Forum Discussion

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...

Microsoft

Sep 02, 2024

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

1P Category - In addition to Incoming Webhook and RSS, Jira 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.
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.

ian_dev98

Copper Contributor

Sep 03, 2024

Prasad_Das-MSFT Ty for the update!

We are a 3rd party app and seems like the issue is not fixed for our connector. The details are:

app id: 428a95dd-b9be-41c6-847a-0aeea6d706d6

app name: awork

connector id: 01ea66d6-db2b-4ef5-8579-d537c7920d84

connector config url: https://app.awork.com/api/v1/accounts/msteams/connector/config.html

I tested it in our normal tenant with id: 03df4317-6ae9-47cf-87d8-5b5a1469763e

as well as in a E5 developer tenant with id: 16a89b03-16aa-4dab-b547-81b9f183771e

(the E5 tenant can easily be used for testing)

Prasad_Das-MSFT
Microsoft
Sep 03, 2024
ian_dev98 , thanks, we have shared this information with engineering team. Once we get any further update, we will inform you in this thread.
- ian_dev98
  Copper Contributor
  Oct 10, 2024
  Prasad_Das-MSFT
  I now managed to get the connector setup working by upgrading to the latest javascript teams-sdk as I was using a 1.x version instead of the current 2.28.0. With that the connector finally is able to saved on Teams desktop app for MacOS.
  Now I am running into another problem. I am getting the webhook url for the connector from the config.
  However, when I try to POST a message to the channel, I get the following response from Microsoft (see curl attached files):
  
  Unknown Connector provider ConnectToO365Inline
  
  I checked the console and there is a request to Update the ConnectToO365Inline connector (see curl attached files). When I run the curl to send the message again with the providerId instead of theConnectToO365Inline in the webhook url, I get the response:
  
  Connector configuration not found
  
  Could you help me here as well? Is there any info I can provide to solve this? I added the 2 curls as a zip to this reply. Hope this helps.
  curls.zip9 KB
  - sukhadevjadhav
    Copper Contributor
    Oct 25, 2024
    Hi, I am also facing same issue after configuring connector for Zabbix in MS teams.
    
    Sending failed: Unknown Connector provider ConnectToO365Inline.
    
    Can you confim if Zabbix connector is working with MSteams?