Connector Configuration Page Not Displaying in New Teams

Radim H 5

Hello,

I have a MS Teams connector app that worked fine in the old Teams but is not displaying its configuration page in the new Teams. The configuration page loads and executes in the background (as evidenced by console logs), but it does not render on the screen. I have updated the app to SDK v2, but the issue persists.

Snímek obrazovky 2024-05-24 v 16.24.10

My connector's configuration page is quite simple—it's mainly for displaying a webhook URL for users to copy. I've compared it with other connectors doing similar things, and their configuration page seem identical to mine.

Can anyone provide guidance on what might be causing this issue or if there are specific changes needed for compatibility with the new Teams?

Thank you!

Radim H.

4 answers

ChetanSharmamsft 1,026 Reputation points Microsoft Vendor

2024-05-24T15:01:56.87+00:00

Hello @Radim H - Thanks for raising your issues.
I hope you have followed below documentation to create the connector:
https://learn.microsoft.com/en-us/microsoftteams/platform/webhooks-and-connectors/how-to/connectors-creating

Could you please check if your connect is enabled or not: https://learn.microsoft.com/en-us/microsoftteams/m365-custom-connectors#enable-or-disable-connectors-in-teams

If possible, could you please share the error logs and let us know if it is working in any Teams clients?
Please sign in to rate this answer.
Radim H 5 Reputation points

2024-05-25T06:33:31.11+00:00

Hello,

Thank you for your reply! Yes, I followed the documentation. However, the connector was created and released several years ago and worked fine. I have checked again and it still works in the old Teams but not in the new Teams (both in the browser and in the app).

Please see the attached console log teams.microsoft.com-1716618452808.log.

The most important part is this (though I made sure that frame-src is set in the CSP, so I don't understand the message). I also checked some other connectors and the same message appears for them (and yet their config pages work - so it does not seem to be related):

```308996-8694cefe20e3856d.js:1 An iframe which has both allow-scripts and allow-same-origin for its sandbox attribute can escape its sandboxing.``` There are also these messages that are coming from my config page (so it seems that the page is loaded and executed behind the scenes). ```config/?team={teamId}&channel={channelName}&en-us:50 app intialized``` ```config/?team={teamId}&channel={channelName}&en-us:68 settings retrieved``` Please let me know if I can provide any further details. Thanks, Radim

Prasad-MSFT 6,076 Reputation points Microsoft Vendor

2024-05-27T05:40:44.9366667+00:00

Double-check the code for rendering the configuration page. Make sure that the HTML elements and CSS styles are compatible with the new Teams interface. Also verify that the contentUrl and other relevant configurations in the app manifest are correctly set up to display the configuration page. The app name in the manifest should match the connector name within the app. Ensure that the app has the necessary permissions configured in the Developer Portal. Check if the domains specified in the manifest are allowed to load in the new Teams client.

Radim H 5 Reputation points

2024-05-27T06:46:08.8033333+00:00

Thanks for your reply.

Well, the same html/code (using the latest Teams JS SDK) works in the old teams, it should work in the new teams as well, right?

Can you please advise me where I can check or even update the manifest? When I go to the Connectors Developer Dashboard (where the connector is registered and published), I don't see any details (when I click the View Submission button, the form is empty).

As I said, the Ybug connector is quite old (and I don't seem to have any way of updating it). Do I need to migrate the connector to the developer portal (is it this one https://dev.teams.microsoft.com/home or another?). Thanks for navigating me through this.

Thanks

Radim

Prasad-MSFT 6,076 Reputation points Microsoft Vendor

2024-05-28T12:11:33.91+00:00

Radim H We have raised an ICM for this issue and engineering team is looking into it. We will inform you once we have further update. Thanks!

Radim H 5 Reputation points

2024-06-04T20:35:44.0966667+00:00

Hello Prasad,

Thanks for your reply. Do you please have any news about this? Do you need any additional details I can provide?

Are there any other significant changes between old and new Teams that might prevent my connector from being loaded? I upgraded the Teams JS library to 2.23 as instructed, so the app should even be ready for the cloud.microsoft domain rollout.... but nothing changed, my connector config page still can't load :-/

Thanks,

Radim

Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Sign in to comment
Deleted

This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Comments have been turned off. Learn more
Deleted

This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Comments have been turned off. Learn more
Deleted

This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Comments have been turned off. Learn more

Share via

Connector Configuration Page Not Displaying in New Teams

4 answers