This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(64, 75%, 16%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJB%3C/text%3E%3C/svg%3E)
We have a CI/CD pipeline that sends messages to a Teams channel via the "Incoming Webhook" connector. Yesterday at 3:47PM Central was the last time that the webhook worked; today I'm getting a 200 response, but the body of the response shows that something is wrong... the gist of it is "XXX is unauthorized, the public key XXX is not found for ring WW, cannot validate signature."
I tried creating a new connector but am getting the same response. And, when I delete the new connector and submit the form to tell why, I get an HTTP error there too.
Is there an outage? Did something change that I need to address?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(211.20000000000002, 39%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ELD%3C/text%3E%3C/svg%3E)
I'm facing the same issue. Tried to create new connectors, but they keep giving error.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(243.2, 62%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EC%3C/text%3E%3C/svg%3E)
Hello Everyone - Thanks for raising your query.
We will look into it and let you know the updates.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(3.2, 66%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJW%3C/text%3E%3C/svg%3E)
I have the same issue from yesterday and don't know how to get it supported ? any idea ?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(57.599999999999994, 65%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMM%3C/text%3E%3C/svg%3E)
Could you please confirm if you are also facing similar error like the one mentioned here - https://techcommunity.microsoft.com/t5/teams-developer/webhook-messages-aren-t-delivered-from-azure-functions/m-p/3954072#M8597. Our incoming webhook connectors are working fine.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(25.6, 26%, 12%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMR%3C/text%3E%3C/svg%3E)
Our error is not the same as the linked. Incoming webhook connectors are not working fine for us and many others.
See https://answers.microsoft.com/en-us/msteams/forum/all/teams-webhook-error-despite-200-ok/920464d2-dd9c-4fae-847a-99855f6498f2 for others with the same issue.
The error given by the MS side is:
Microsoft.Exchange.Security.TokenIssuer.Common.SubstrateTokenRequestException: Request 427c2e45-22b1-43a3-94dd-e277dfd221e1;1697517710;1.0;48af08dc-f6d2-435f-b2a7-069abd99c086;https://outlook.office.com;;[],bd581b29e7bf4a48b16e7fc6bca2cb66,48af08dc-f6d2-435f-b2a7-069abd99c086,;GlobalActor;{TokenScopeType,CloudInstance},{AccessType,HpaAsApp},{PopKey,{"kty":"RSA","n":"v95EizVpL385wCMW8sD3n_qACwnPKv2IstraFBLo_RU5bq6Ky8BwSDw_U-SB42qdH-W8X7BKBE2IRdfrT4aJkGgfMqQhPFAmH-xr-hIbBr6b4bcfjaocrGLpGxqS5b60MszTKdooHIy6JQasfsnzDJ367mFvtPj9fwAgAynKr-PTfI3y8Pn2-oZcuaz9jX2aF0qEngWOasr4sLVrq654NxUD7MBf3He-Yd_1-bYAMtVNfsG0Iv8Ih6HJ4EJcJUbSfBvgc1SWqrg0IGGJJZYcsodJkQ36DnQeUk28NGT2KdNawyzKZDAaVpxunH6eFOCE2NguwjN_Y-TrNZSHIHEKaQ","e":"AQAB","alg":"RS256","kid":"749f5a89-100e-44fc-9b8c-5c4a014bb709"}};warqvR45thDtXFmf0RCvmtXXdLU=;lejdjFZ-mokS5YZuZ55T4fppdDY to https://localhost:444/sts/token/1 on server DM8PR01MB6856 failed with status code 401(Unauthorized) and reason {"Message":"STI server DM8PR01MB6856 failed to process request. Error: Request "427c2e45-22b1-43a3-94dd-e277dfd221e1;1697517710;1.0;48af08dc-f6d2-435f-b2a7-069abd99c086;https://outlook.office.com;;[],bd581b29e7bf4a48b16e7fc6bca2cb66,48af08dc-f6d2-435f-b2a7-069abd99c086,;GlobalActor;{TokenScopeType,CloudInstance},{AccessType,HpaAsApp},{PopKey,{"kty":"RSA","n":"v95EizVpL385wCMW8sD3n_qACwnPKv2IstraFBLo_RU5bq6Ky8BwSDw_U-SB42qdH-W8X7BKBE2IRdfrT4aJkGgfMqQhPFAmH-xr-hIbBr6b4bcfjaocrGLpGxqS5b60MszTKdooHIy6JQasfsnzDJ367mFvtPj9fwAgAynKr-PTfI3y8Pn2-oZcuaz9jX2aF0qEngWOasr4sLVrq654NxUD7MBf3He-Yd_1-bYAMtVNfsG0Iv8Ih6HJ4EJcJUbSfBvgc1SWqrg0IGGJJZYcsodJkQ36DnQeUk28NGT2KdNawyzKZDAaVpxunH6eFOCE2NguwjN_Y-TrNZSHIHEKaQ","e":"AQAB","alg":"RS256","kid":"749f5a89-100e-44fc-9b8c-5c4a014bb709"}};warqvR45thDtXFmf0RCvmtXXdLU=;lejdjFZ-mokS5YZuZ55T4fppdDY" is unauthorized, the public key warqvR45thDtXFmf0RCvmtXXdLU= is not found for ring WW, cannot validate signature"}. The response headers are: Date:Tue, 17 Oct 2023 04:41:49 GMT;Server:Microsoft-HTTPAPI/2.0.'
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(288, 74%, 37%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETL%3C/text%3E%3C/svg%3E)
Same problem since yesterday.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(35.2, 37%, 13%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDT%3C/text%3E%3C/svg%3E)
We are having a similar issue with Webhooks called by ADF. Slowness noticed yesterday 16/10, but much worse today and causing timeout failures. There seems to be a backlog of requests, we get the response after approx 20 mins
@Meghana-MSFT No, it's not the same. The http response is actually a 200 response, but the body is showing the above error.
My Postman test was successful just now, so it's possible this issue has been resolved. I'll keep my eyes on it today.
(deleted, duplicate comment)
Mine still takes forever to send message. At least yesterday it had like 5% success rate.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(185.6, 51%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAP%3C/text%3E%3C/svg%3E)
I can report the same issue on our side. We set up the weebhooks in teams months ago with no issues. They started to present intermittent behavior on 11-10-2023.
We are using Python 3.11.5 and pymsteams 0.2.1.
Here our script to generate the message:
import pymsteams
ms_teams_webhook_url=<WebbhookUrl>
ms_teams_message=pymsteams.connectorcard(ms_teams_webhook_url)
ms_teams_message.text(message)
ms_teams_message.send()
The first error that we can report is this one:
Webhook message delivery failed with error: Microsoft Teams endpoint returned HTTP error 500 with ContextId tcid=0,server=msgapi-production-weu-08-0,cv=9By0aPSKMEC/06j+RzUy+Q.001=2..
Then, we have received the following error message on 13-10-2023 as reported in this issue:
Microsoft.Exchange.Security.TokenIssuer.Common.SubstrateTokenRequestException: ... is unauthorized, the public key <PUBLIC_KEY> is not found for ring WW, cannot validate signature"}. The response headers are: Date:Fri, 13 Oct 2023 12:30:44 GMT;Server:Microsoft-HTTPAPI/2.0.
The issue has been mitigated, could you please confirm if it is working fine now.
It appears to be working for me. Thank you!
There is an ongoing issue in Exchange Connectors. An incident has been raised related to this error - Web Hooks erroring randomly, unauthorized, the public key XXXXXXXXXXXXXXXXX = is not found for ring WW, cannot validate signature"}.
The issue has been mitigated, could you please confirm if it is working fine now.
Same thing here, retries sometimes work.
It works normally today. Maybe the problem is fixed. Hope it won't come back to haunt us.