New Teams missing functionality and broken connectors

Courtney Henderson 60

Hello,

We currently have a custom teams application which has been working for several years however we have noticed some issues when switching to the new Teams.

Issue 1: Failure to save configurable connector

When configuring our sideloaded connector for our custom app, the configuration does not save when using the new Teams. No errors are thrown (apart from a vague Possibly unhandled rejection: {} undefined, which I think is unrelated?) and it simply shows the connector list again following saveEvent.notifySuccess(); the behaviour seems to be the same whether using the V1 or V2 Javascript SDK.

Has anyone else had similar issues with saving a configurable connector?

Issue 2: Inability to add connectors to Private channel

Adding a connector to a private channel is now no longer an option in the new Teams. Can anyone point me to relevant documentation which describes this change in functionality. Is there a way around this? Or might this be a tenant specific configuration?

Issue 3: Missing values from Context

When getting context from microsoftTeams.app.getContext(), a lot of values now seem to display ‘undefined’ in the new Teams where they show relevant values in Teams Classic. Notably for us the channelName value

Again, can anyone point me to relevant documentation for this change?

All the above seem to be the same regardless of using V1 or V2 of the javascript SDK.

Unfortunately these currently make our application unusable in the new Teams, and we are hesitant to ask our clients to revert back to Teams Classic. Any help would be greatly appreciated.

Many thanks

JimmyYang-MSFT 53,851 Reputation points Microsoft Vendor

2023-11-24T06:26:41.2166667+00:00

@Courtney Henderson

Teams tag is mainly focused on the general issue of Microsoft Teams troubleshooting. According to your description, your question is more related to Teams development. So I will remove teams tag from your thread. Thanks for your understanding!
Meghana-MSFT 3,891 Reputation points Microsoft Vendor

2023-11-24T12:05:49.3466667+00:00

We will check this and get back to you.
Meghana-MSFT 3,891 Reputation points Microsoft Vendor

2023-11-28T15:31:12.5733333+00:00
We checked by creating a connector in Connectors Developer Dashboard and were able to save it https://outlook.office.com/connectors/publish. Could you please let us know if you are doing it differently?

We are checking this internally

We were able to get the context.channel.displayname correctly in new Teams T2.1 -
Meghana-MSFT 3,891 Reputation points Microsoft Vendor

2023-11-28T15:31:55.1633333+00:00
We checked by creating a connector in Connectors Developer Dashboard and were able to save it https://outlook.office.com/connectors/publish. Could you please let us know if you are doing it differently?

We are checking this internally

We were able to get the context.channel.displayname correctly in new Teams T2.1 -
Courtney Henderson 60 Reputation points

2023-11-29T12:40:21.6933333+00:00

Thank you for the reply @Meghana-MSFT

When getting the context via the JS SDK we get the following:

This is within a configuration page when using the registerOnSaveHandler. In Teams classic, we get the channel name, however in new Teams it is 'undefined'.

We then set the config and save the webhook URL so we can post notifications to the channel. This works, and we receive the webhookURL successfully, however on triggering the saveEvent.notifySuccess() the configuration page closes without any error messages or indication that the connector config has not worked, however no configured connectors are displayed in the list, nor does the connector work.

This works perfectly without any issues in Teams classic.

Many thanks
Courtney Henderson 60 Reputation points

2023-12-04T12:27:46.2533333+00:00

Hello @Meghana-MSFT

Just a message to follow up on my previous one. I wonder if you have been able to replicate these issues or are able to advise any further.

Initially I thought this might have been an issue on our tenant only, however our clients are experiencing the same.

Has anyone else experienced these issues? Is this a known issue? Can I provide any further information to help diagnose the issue?

I notice you mentioned you are looking internally into the issue with an inability to add connectors to a private channel. Is there any update on this?

Many thanks,
Mike W 25 Reputation points

2023-12-04T15:09:23.5833333+00:00

I have experienced the same issue as point 2 in the initial post. Cannot add an Incoming Web Hook to a private teams channel.

Also, the lack of a 'connectors' option means I cannot view currently configured Web Hooks.

This is in the non-development side and so should include the Teams troubleshooting tag. Appears to be a change in functionality in 'New' version.
Meghana-MSFT 3,891 Reputation points Microsoft Vendor

2024-02-19T11:20:50.1633333+00:00

You can add connectors to private channels from manage channel settings. Please refer the below screenshot -
Peter Philips 106 Reputation points

2024-03-16T18:43:52.9933333+00:00

We are also seeing numerous bugs in the New Teams related to connectors. Connectors continue to work properly in the "Old" Teams. I also see, as @Courtney Henderson said, that the new Teams context as retrieved from the teamsClient.getContext does not contain channel information

Here is context from old teams

Here is context from same channel on new teams

You can also see channelRelativeUrl and channelType are also missing. We count on these fields to provide helpful functionality.

While this is broken, we are also advising our customers to not use the new Teams, which isn't stellar for anyone. Thanks in advance if this can be fixed with priority. Cheers.

1 answer

Courtney Henderson 60 Reputation points

2024-01-04T11:32:32.8133333+00:00

Just a follow up on this.

I have contacted a Microsoft support analyst directly via my admin colleague and they have confirmed the new Teams app does not support these features and that the advised resolution is to revert to Teams Classic until fixed at their end (which they are actively monitoring).

We will be advising all our clients to revert to Teams Classic in order to use the required features of our app until resolved by Microsoft.

I will endeavour to update this post once the issue is resolved.

I hope this is of help to others experiencing the same issues.
Please sign in to rate this answer.

6 people found this answer helpful.
Ray Allen (US) 0 Reputation points

2024-01-12T15:36:33.2833333+00:00

Thank you! I was about to reach out to our admins to contact MS but since they are aware and hope to have resolution soon, I'll wait.

Mike W 25 Reputation points

2024-01-31T20:56:11.79+00:00

OK, sounds good, that's what I was doing. Thanks!

Courtney Henderson 60 Reputation points

2024-07-18T09:44:05.98+00:00

Update: The connector issues have now been resolved for the most part. Unfortunately this has come just in time for Microsoft to retire connectors:

https://devblogs.microsoft.com/microsoft365dev/retirement-of-office-365-connectors-within-microsoft-teams/

Looks like the alternative suggested is to use workflows. This doesn't meet our requirements, but have found that using a Bot with proactive messaging can achieve fairly similar functionality.

I found these blog posts particularly useful:

https://ashiqf.com/tag/adaptive-card-message-in-teams-channel-using-bot-framework/

https://ashiqf.com/2022/03/
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

New Teams missing functionality and broken connectors

1 answer

Your answer