Incoming Webhooks
8 Topics
Teams: Error when attempting to add new Incoming Web Hooks Connector
We are getting an error when attempting to add an Incoming Webhook connector to our Teams. It appears that it is happening across all our Teams no matter what channel it is. When we go to add a new Incoming Webhook connector we get an error that says, "Something went wrong. Failed to create webhook b2 URL for tenant..." followed by our tenant. Nothing else is given for the reason why. It looks like the existing Incoming Webhooks are working however there is an alert that says "Attention required" on them. We first noticed this happening yesterday. Moving this question over from here as recommended by community expert: https://docs.microsoft.com/en-us/answers/questions/190611/teams-error-when-attempting-to-add-new-incoming-we.htmlSolved2.7KViews1like1CommentAzure DevOps Service Hooks & Teams Incoming Webhooks
Hi everyone, I'm trying to determine how to utilize the Service Hooks in Azure DevOps so that we can tie into Teams via an incoming webhook to automatically post to a channel in Teams whenever a Pull Request is created. When I run a test on the Azure side posting to the Incoming Webhook url from the Teams channel - I just get a 400/Bad Request I assume the issue has to do with the format of the payload being sent from Azure and the format that the O365 connector is requiring - but I can't seem to find anything on this topic. Has anyone configured something like this or does anyone have some suggestions I can look into? Thanks for your time!Solved8.9KViews1like6Comments
