Forum Discussion
MS Teams Connector pop-up not loading and more
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)
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_dev98Oct 10, 2024Copper ContributorI 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 ConnectToO365InlineI 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 foundCould 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.
- sukhadevjadhavOct 25, 2024Copper Contributor
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?
- Prasad_Das-MSFTOct 28, 2024
Microsoft
sukhadevjadhav , we have shared the details with engineering team. Once we have any further update, we will respond in this thread. Thanks!