Teams: Error when attempting to add new Incoming Web Hooks Connector

Question

Teams: Error when attempting to add new Incoming Web Hooks Connector

Emily 31

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.

OlympusatJeremy 6 Reputation points

2020-12-08T19:28:17.097+00:00

I ran into this issue today as well. I confirmed permissions are good. This is what I see:

:-(
Something went wrong.
Failed to create webhook b2 URL for tenant COMPANY_NAME
RequestId: 2c64c06c-1dbb-4e20-81f5-18e80e165f15
Server: BN6PR13MB1379
Date: 12/8/2020 7:17:10 PM
Rama-MSFT 181 Reputation points

2020-12-09T12:21:09.133+00:00

Hi @Emily ,

Thanks for reaching us!

We are investigating on this, will respond to you soon.
Emily 31 Reputation points

2020-12-09T13:16:53.657+00:00

I am glad that we are not alone. Our permissions are good as well. I reached out originally on Twitter and they mentioned that a release was recently done that might have broken this. No word on if or when it will be fixed.
Rama-MSFT 181 Reputation points

2020-12-10T07:17:55.207+00:00

Hi @Emily ,

Could you please share your Connector Id and json schema that you are using. So, we can test and provide you better service.
Emily 31 Reputation points

2020-12-10T13:01:01.47+00:00

@Rama-MSFT We can't even create a new connector to get an id or send the json. We fail with the generic error that "Something went wrong. Failed to create webhook b2 URL for tenant...."
OlympusatJeremy 6 Reputation points

2020-12-10T14:24:09.583+00:00

If this helps, this error occurs when we try to setup the incoming webhook. Once we get to choose a name for the hook and the image, when you click next then you see the error.
OlympusatJeremy 6 Reputation points

2020-12-10T19:31:28.66+00:00

@Emily I tried this again today and it now seems to be working. See if it is working for you too
Emily 31 Reputation points

2020-12-10T19:48:32.89+00:00

Thanks, @OlympusatJeremy . It is good to know that a fix might have rolled out. I just tired a little bit ago and we are still seeing errors but I will keep trying.
Emily 31 Reputation points

2020-12-10T20:29:26.453+00:00

I just checked again and it is working for us as well! Cheers!!
Jagadeesh-MSFT 331 Reputation points

2020-12-18T10:14:49.197+00:00

Hi @Emily , are you still facing the issue ?.

2 answers

Your answer

OlympusatJeremy 6 Reputation points

2020-12-08T19:28:17.097+00:00

I ran into this issue today as well. I confirmed permissions are good. This is what I see:

:-(
Something went wrong.
Failed to create webhook b2 URL for tenant COMPANY_NAME
RequestId: 2c64c06c-1dbb-4e20-81f5-18e80e165f15
Server: BN6PR13MB1379
Date: 12/8/2020 7:17:10 PM
Rama-MSFT 181 Reputation points

2020-12-09T12:21:09.133+00:00

Hi @Emily ,

Thanks for reaching us!

We are investigating on this, will respond to you soon.
Emily 31 Reputation points

2020-12-09T13:16:53.657+00:00

I am glad that we are not alone. Our permissions are good as well. I reached out originally on Twitter and they mentioned that a release was recently done that might have broken this. No word on if or when it will be fixed.
Rama-MSFT 181 Reputation points

2020-12-10T07:17:55.207+00:00

Hi @Emily ,

Could you please share your Connector Id and json schema that you are using. So, we can test and provide you better service.
Emily 31 Reputation points

2020-12-10T13:01:01.47+00:00

@Rama-MSFT We can't even create a new connector to get an id or send the json. We fail with the generic error that "Something went wrong. Failed to create webhook b2 URL for tenant...."
OlympusatJeremy 6 Reputation points

2020-12-10T14:24:09.583+00:00

If this helps, this error occurs when we try to setup the incoming webhook. Once we get to choose a name for the hook and the image, when you click next then you see the error.
OlympusatJeremy 6 Reputation points

2020-12-10T19:31:28.66+00:00

@Emily I tried this again today and it now seems to be working. See if it is working for you too
Emily 31 Reputation points

2020-12-10T19:48:32.89+00:00

Thanks, @OlympusatJeremy . It is good to know that a fix might have rolled out. I just tired a little bit ago and we are still seeing errors but I will keep trying.
Emily 31 Reputation points

2020-12-10T20:29:26.453+00:00

I just checked again and it is working for us as well! Cheers!!
Jagadeesh-MSFT 331 Reputation points

2020-12-18T10:14:49.197+00:00

Hi @Emily , are you still facing the issue ?.

Answer 1

@Emily ,

As we are mainly responsible for general issue of Microsoft Teams, your question which is involved in development is not supported by us. It recommends you ask in Teams developer forum. You will get the most qualified pool of respondents, and other partners who read the forums regularly can either share their knowledge or learn from your interaction.

Moreover, some suggestions may be helpful to your scenario.

Check if there is some error message in the health status of Microsoft Teams in Office 365 admin center > Health > Service health.
Confirm with your IT admin if he creates a conditional access in Azure AD.

If the response is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

Patrick 1

Just ran into this earlier this afternoon. No fix yet from what I can see.

0 comments