I cannot add an incoming webhook to ms teams channel

Dennis B_ 90

Hello,

yesterday when I tried to add an incoming webhook I got the generic error message that "something went wrong".

Now when I hit "add" on the incoming webhook, I just get a blank page.

Following the network traffic, I found out that the request on

/connectors/IncomingWebhook/Manage/New?MailboxAddress=e880cc50-6518-49f2-9abd-549668ec3b86%401b94b413-6d28-42b0-bf1a-7bb10aa22440&client=SkypeSpaces&SSThread=19%3ApJFBJXqrH3tfd-wLD5uuJOE6xrwauZN_0znaj0OeEAg1%40thread.tacv2&HostName=teams.microsoft.com&culture=de-de&ssApiHost=de.ng.msg.teams.microsoft.com&iframe=true&SSTheme=default&isDesktopClient=false&enableConnectorApps=true&providerId=203a1e2c-26cc-47ca-83ae-be98f960b6b2

returns a server error 500.

We need this desperately. Thankful for any help!

SINANI Ersan 5 Reputation points

2024-07-25T11:10:47.35+00:00

Hello. We are getting the same issue
Stephan Grunder 20 Reputation points

2024-07-26T08:04:12.0233333+00:00

It is not working.
tested on:
24180.205.2980.1757 icw client 49/24062724814
and with webclient**
1415/24061318413**

Due to the short notice of withdrawing the webhook functionality and also the vacation period we really want to use this functionality untill the end. Furthermore workflow is (i think) not supported on shared teams channels (at least I don't see it).
Is there anopther way to add a webhook to a shared channel. I really want to add a webhook to my new channel and as i understand this should be possible to do so until 15th of august. But currently it is not working and time is running out.

regards

Steve
Iran Udayanga 15 Reputation points

2024-07-26T11:43:37.2066667+00:00

we have same issues we can not add a new one
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Aymen E 15 Reputation points

2024-07-29T08:59:37.92+00:00

Still having the same issue, with no error though, just the blank page.

I am pretty sure this is just a move from Microsoft to block us from using O365 Connectors, even though it is no deprecated yet.

So to me, the reality is that its creation is deprecated since sometime now, they just don't officially state the case. Thank you MS !
Prasad-MSFT 6,671 Reputation points Microsoft Vendor

2024-07-30T04:48:33.3866667+00:00

@Dennis B_ , SINANI Ersan, Stephan Grunder, Iran Udayanga, Aymen E could you please share your respective tenant Ids where you are facing this issue, so that we can share those details with engineering team to fix?
Rene Platt 10 Reputation points

2024-08-02T14:48:14.5066667+00:00

Its still not working.
Prasad-MSFT 6,671 Reputation points Microsoft Vendor

2024-08-07T12:12:33.31+00:00

According to latest update from engineering team, you can start using teams web to create Incoming Webhook & RSS connectors. However, the fix for Teams Desktop client is under investigation.
Mads AA 0 Reputation points

2024-08-21T06:28:24.7466667+00:00

At this point it is not something to base any new projects on, as it is being phased out.

Source: https://devblogs.microsoft.com/microsoft365dev/retirement-of-office-365-connectors-within-microsoft-teams/

Accepted answer

Prasad-MSFT 6,671 Reputation points Microsoft Vendor

2024-07-16T05:52:29.55+00:00

We checked this from our side by creating a new incoming webhook and are able to create successfully.

Tested in Microsoft Teams version 24187.501.2981.3768. The client version is 49/24053101421.

FYI, O365 connectors within Teams will be deprecated and notifications from this service will stop. Learn more about the timing and how the Workflows app provides a more flexible and secure experience. If you want to continue receiving these types of messages, you can use a workflow to post messages from a webhook request. Set up workflow
Please sign in to rate this answer.

1 person found this answer helpful.
Claudio_B 15 Reputation points

2024-07-18T14:49:15.89+00:00

I have the same problem and can reproduce it on different machines with different clients (web vs native) and two different tenants/organizations.

Do you have any suggestions?

Firdouse Begum MEHATHAR 0 Reputation points

2024-07-22T06:26:20.34+00:00

We are still facing the issue, even after trying multiple solutions.
Cache and reinstalling nothing helped. The blank screen or loading for a long time persists with Incoming webhooks. And not even able to copy the configured URL.

Laurent Bouriez 5 Reputation points

2024-07-22T15:06:47.6133333+00:00

Facing the same issue, how can this be an official answer from Microsoft ???

Josef Rainer 0 Reputation points

2024-07-22T15:56:50.8566667+00:00

I also have this problem for last few days

Mads AA 0 Reputation points

2024-07-23T09:22:28.6233333+00:00

I've been having the same issue for a week now.

Teams version: 24165.1414.2987.41
Client version: 49/24061318413.

Mads AA 0 Reputation points

2024-07-23T09:23:55.0466667+00:00

.....

Dieter Loskarn 0 Reputation points

2024-07-25T11:47:28.3333333+00:00

Same issue here, different client versions as well as the web-client.

Kelvin Shee 30 Reputation points

2024-07-29T00:25:40.3033333+00:00

no solution from microsoft ?

Aymen E 15 Reputation points

2024-07-29T09:34:21.4+00:00

Why is this the accepted answer ? @Dennis B_

This does not provide any solution, only "it works for us, so it should work for you".

Prasad-MSFT 6,671 Reputation points Microsoft Vendor

2024-07-30T04:51:11.5433333+00:00

Claudio_B, Firdouse Begum MEHATHAR, Laurent Bouriez, Josef Rainer Mads AA, Dieter Loskarn Kelvin Shee could you please share your respective tenant Ids where you are facing this issue, so that we can share those details with engineering team to fix?

Prasad-MSFT 6,671 Reputation points Microsoft Vendor

2024-07-30T04:56:48.73+00:00

Update:
O365 Connectors Substrate team is aware of this issue and there is an ICM raised to fix this. Once this is fixed, we will notify you in this thread. Thanks!

Please do share your respective Tenant Ids

Hercule BOINA HADJI 0 Reputation points

2024-08-01T08:12:34.7166667+00:00

Same issue, cant create a connector

Tin Tupek 0 Reputation points

2024-08-02T13:45:51.4+00:00

Any update on this fix.

Ryohei SUZUKI 0 Reputation points

2024-08-04T12:17:52.33+00:00

same issue

Prasad-MSFT 6,671 Reputation points Microsoft Vendor

2024-08-07T12:12:52.3133333+00:00

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

Johanne Ulrica Øveraasen 0 Reputation points

2024-08-22T12:23:12.73+00:00

I still have the same issue

Teams version: 24215.1005.3072.3011.

Client version: 49/24080212008.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

17 additional answers

André Schild 10 Reputation points

2024-07-19T17:17:59.49+00:00

Hello,

we see this behaviour too.

Looking at the console in the webbrowser we see this error message:
nhandled error/rejection {"isTrusted":true}

error @ v2/:6

v2/:6 {}

error @ v2/:6

v2/:6 Unhandled error/rejection {"isTrusted":true}

error @ v2/:6

chromewebdata/:1 Refused to display 'https://login.microsoftonline.com/' in a frame because it set 'X-Frame-Options' to 'deny'.

This indicates that MS is making a mess with security settings.

And yes, we would like to user workflows, but so far I have not found a way to add Workflows to shared channels...?
Please sign in to rate this answer.

2 people found this answer helpful.
Prasad-MSFT 6,671 Reputation points Microsoft Vendor

2024-07-30T04:52:49.7466667+00:00

could you please share your tenant Id where you are facing this issue, so that we can share those details with engineering team to fix?
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Brandon Jank 10 Reputation points

2024-07-24T20:47:07.13+00:00

Same issue, been like this for a week now.
Please sign in to rate this answer.

2 people found this answer helpful.
Prasad-MSFT 6,671 Reputation points Microsoft Vendor

2024-07-30T04:54:17.8966667+00:00

could you please share your tenant Id where you are facing this issue, so that we can share those details with engineering team to fix?
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Barrow Kwan 10 Reputation points

2024-07-26T06:07:38.2166667+00:00

I had the same issue and been more than a week
Please sign in to rate this answer.

2 people found this answer helpful.
Prasad-MSFT 6,671 Reputation points Microsoft Vendor

2024-07-30T04:54:25.05+00:00

could you please share your tenant Id where you are facing this issue, so that we can share those details with engineering team to fix?
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Iran Udayanga 15 Reputation points

2024-07-26T11:44:52.6333333+00:00

we have same issue, we can not create a new one
Please sign in to rate this answer.

2 people found this answer helpful.
Prasad-MSFT 6,671 Reputation points Microsoft Vendor

2024-07-30T04:54:32.8933333+00:00

could you please share your tenant Id where you are facing this issue, so that we can share those details with engineering team to fix?
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

I cannot add an incoming webhook to ms teams channel

17 additional answers

Your answer