Forum Discussion

ian_dev98's avatar
ian_dev98
Copper Contributor
Sep 02, 2024

MS Teams Connector pop-up not loading and more

Hi there,

 

I have several issues with the MS Teams Connectors at the moment:

 

1. Connectors configuration tab not loading in the web app. I get the message that teams seems to be offline, which is not the case. I tested it in the mac desktop app and there it works fine:

 

2. The outlook connector configuration page is not working (already reported in https://techcommunity.microsoft.com/t5/teams-developer/issues-with-ms-teams-connectors/m-p/4195335)

-> https://outlook.office.com/connectors/publish redirects to https://outlook.office.com/connectors/connectors/Home/Error

 

3. A few days ago, once I configure my connector (I am using our company "awork" connector) and you click on the Save button, the 

microsoftTeams.settings.registerOnSaveHandler gets executed as expected, however the connector is not saved. Now it doesn't even let me open the configuration page anymore. No changes were done by me in the meantime. The request id is 
00-cd956e28829c4e89f03f9b76677ea30b-b8e156a867f6a66b-00
 
The integration is important to us as this affects several of our enterprise customers. Is there any other info I can provide? As the connectors are not deprecated yet, I would expect this whole setup to still work...
Kind regards
Ian
  • ian_dev98 , O365 Connectors Substrate team is aware of this issue and there is an ICM raised to fix this.

    According to latest update from engineering team, it was fixed in teams web, and you can create Incoming Webhook & RSS connectors. However, the fix for Teams Desktop client is under investigation.

     

    We checked at our end using Teams web and are able to create/configure incoming webhook connectors. 

    • ian_dev98's avatar
      ian_dev98
      Copper Contributor

      Prasad_Das-MSFT Hi, thanks for the quick reply! Which of the 3 issues are you referring to when you say that the "O365 Connectors Substrate team is aware of this issue and there is an ICM raised to fix this"?

       

      My 3rd issue with configuring my connector is unrelated to the incoming webhook connectors. For this I am trying to configure the "awork" connector which we published at the MS Teams Connector Store:

       

      Once I hit the configure button, I get the error message that something went wrong with the request id:

      I get the following errors in my console, maybe this helps:

       

      2 weeks ago this still worked, back then "only" saving the connector config failed.

       

      Is there any more info I can provide from my side to solve this issue?

      • Prasad_Das-MSFT's avatar
        Prasad_Das-MSFT
        Icon for Microsoft rankMicrosoft

        ian_dev98,  the ICM was raised for the issue that involves Teams Management not functioning correctly when creating Connectors. Users are experiencing errors such as 500 and 403 when attempting to create incoming webhooks and RSS connectors etc. The problem persists across both Teams desktop and web clients, with some users encountering a white screen upon completion of the creation flow. Users are unable to create or configure Connectors in Teams, encountering errors and white screens.

        According to latest update

        1. 1P Category - In addition to Incoming Webhook and RSSJira Cloud, Jenkins, GitHub Enterprise, Bitbucket Server, New Relic, StatusPageIO, Pingdom would work with the latest fix. No other connector in this category works.
          Note: There is known issue when creating an Incoming Webhook, which results in a white/empty screen, happens when clicking "Done" button at the end of the creation flow, to mitigate this issue, pressing Home at the top of the page to go back, would help, technically webhook would get created, and one can use it.
        2. 3P Category - All connectors in this category works.

         

        If your connector doesn't fall under fixed category, please share connector details along with tenant id, so that we can inform engineering team about update.

  • Hi ian_dev98 , Engineering team is not able to repro this. Can you please send a test message to the above webhook URL to generate fresh backend logs and investigate the issue?

Resources