SOLVED

Incoming Webhook - MS Teams returned HTTP error 403

%3CLINGO-SUB%20id%3D%22lingo-sub-108801%22%20slang%3D%22en-US%22%3EIncoming%20Webhook%20-%20MS%20Teams%20returned%20HTTP%20error%20403%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-108801%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%20sending%20log%20information%20from%20my%20application%20directly%20to%20MS%20Teams%20channel.%20The%20problem%20is%20that%20it%20stopped%20working%20around%20one%20month%20ago.%20When%20I%20try%20to%20send%20POST%20by%20using%20Postman%2C%20I%20get%20error%26nbsp%3B%3C%2FP%3E%3CPRE%3EWebhook%20message%20delivery%20failed%20with%20error%3A%20Microsoft%20Teams%20endpoint%20returned%20HTTP%0Aerror%20403%20with%20ContextId%20tcid%3D8329146558657309443%2Cserver%3DEAP010230157048..%3C%2FPRE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20was%20trying%20to%20search%20something%20about%20it%2C%20but%20I%20didn't%20find%20anything.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20ideas%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%3C%2FP%3E%3CP%3ELukas%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-108801%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%20Incoming%20Webhook%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-132311%22%20slang%3D%22en-US%22%3ERe%3A%20Incoming%20Webhook%20-%20MS%20Teams%20returned%20HTTP%20error%20403%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-132311%22%20slang%3D%22en-US%22%3E%3CP%3EFinally%20it%20started%20to%20work%20when%20I%20had%20enabled%20Incoming%20Webhook%20connector.%20No%20more%20403%20errors%20%3A)%3C%2Fimg%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-131619%22%20slang%3D%22en-US%22%3ERe%3A%20Incoming%20Webhook%20-%20MS%20Teams%20returned%20HTTP%20error%20403%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-131619%22%20slang%3D%22en-US%22%3E%3CP%3EIn%20order%20to%20see%20the%20connectors%20that%20disappeared%2C%20you%20have%20to%20(as%20an%20admin)%20go%20into%20your%20tenant%20settings%20and%20under%20Apps%20turn%20on%20%22Enable%20new%20external%20apps%20by%20default.%22%20An%20update%20in%20August%20added%20Connectors%20to%20Apps%20and%20turned%20off%20external%20apps%20by%20default.%20We%20turned%20this%20setting%20on%20and%20restarted%20Teams%20and%20the%20connectors%20showed%20up.%20See%20the%20blog%20post%20about%20it%20here%3A%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FMicrosoft-Teams-Blog%2FNew-admin-controls-for-apps-in-Teams%2Fba-p%2F78975%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FMicrosoft-Teams-Blog%2FNew-admin-controls-for-apps-in-Teams%2Fba-p%2F78975%3C%2FA%3E.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-126628%22%20slang%3D%22en-US%22%3ERe%3A%20Incoming%20Webhook%20-%20MS%20Teams%20returned%20HTTP%20error%20403%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-126628%22%20slang%3D%22en-US%22%3E%3CP%3EI've%20tried%20both%20accounts%20(admin%20and%20standard)%20and%20there%20is%20no%20difference.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-126569%22%20slang%3D%22en-US%22%3ERe%3A%20Incoming%20Webhook%20-%20MS%20Teams%20returned%20HTTP%20error%20403%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-126569%22%20slang%3D%22en-US%22%3E%3CP%3Eit%20seems%20you%20have%20some%20issues.%20I%20get%20some%20errors%20on%20JS%20that%20is%20referring%20to%20calling%20which%20is%20not%20there%20yet.%3C%2FP%3E%3CP%3EI%20also%20see%20some%20401's%20at%20your%20screen%20are%20you%20the%20admin%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-126534%22%20slang%3D%22en-US%22%3ERe%3A%20Incoming%20Webhook%20-%20MS%20Teams%20returned%20HTTP%20error%20403%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-126534%22%20slang%3D%22en-US%22%3E%3CP%3EHmm%20I%20don't%20know%20what's%20wrong%2C%20but%20I%20still%20see%20the%20same%20connectors%20as%20I've%20posted%20before.%20I've%20also%20tried%20to%20run%20MS%20Teams%20in%20a%20web%20browser%2C%20but%20no%20difference.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBtw.%20I've%20checked%20Console%20window%20of%20Developer%20Tools%20and%20there%20are%20a%20lots%20of%20JS%20errors%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F23930iEB53311D71279E35%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22image.png%22%20title%3D%22image.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-126516%22%20slang%3D%22en-US%22%3ERe%3A%20Incoming%20Webhook%20-%20MS%20Teams%20returned%20HTTP%20error%20403%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-126516%22%20slang%3D%22en-US%22%3E%3CP%3EJust%20checked%20in%203%20different%20tenants%20but%20the%20option%20is%20still%20there%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-126011%22%20slang%3D%22en-US%22%3ERe%3A%20Incoming%20Webhook%20-%20MS%20Teams%20returned%20HTTP%20error%20403%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-126011%22%20slang%3D%22en-US%22%3E%3CP%3EIt%20looks%20like%20that%3CSTRONG%3E%20Incoming%20Webhook%3C%2FSTRONG%3E%20connector%20is%20not%20supported%20anymore.%3C%2FP%3E%3CP%3EAt%20this%20moment%20there%20are%20just%20a%20few%20connectors%20available%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20598px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F23852i5B32CE48044D3D62%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22image.png%22%20title%3D%22image.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-125621%22%20slang%3D%22en-US%22%3ERe%3A%20Incoming%20Webhook%20-%20MS%20Teams%20returned%20HTTP%20error%20403%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-125621%22%20slang%3D%22en-US%22%3E%3CP%3EIs%20this%20a%20webhook%20that%20is%20older%3F%20or%20a%20new%20one%20and%20where%20do%20you%20use%20it%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-125598%22%20slang%3D%22en-US%22%3ERe%3A%20Incoming%20Webhook%20-%20MS%20Teams%20returned%20HTTP%20error%20403%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-125598%22%20slang%3D%22en-US%22%3E%3CP%3ENot%20sure%20if%20related%20in%20any-way%2C%20but%20for%20about%20the%20month%20I've%20been%20working%20on%20it%20SPO%20has%20been%20delivering%20malformed%20JSON%20from%20it's%20web-hook%20to%20my%20server.%20Maybe%20something%20has%20broken%20on%20the%20web-hook%20side%20of%20things%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

Hello,

 

I'm sending log information from my application directly to MS Teams channel. The problem is that it stopped working around one month ago. When I try to send POST by using Postman, I get error 

Webhook message delivery failed with error: Microsoft Teams endpoint returned HTTP
error 403 with ContextId tcid=8329146558657309443,server=EAP010230157048..

 

I was trying to search something about it, but I didn't find anything.

 

Any ideas?

 

Thanks

Lukas

10 Replies

Not sure if related in any-way, but for about the month I've been working on it SPO has been delivering malformed JSON from it's web-hook to my server. Maybe something has broken on the web-hook side of things?

Is this a webhook that is older? or a new one and where do you use it?

It looks like that Incoming Webhook connector is not supported anymore.

At this moment there are just a few connectors available

image.png

Just checked in 3 different tenants but the option is still there

Hmm I don't know what's wrong, but I still see the same connectors as I've posted before. I've also tried to run MS Teams in a web browser, but no difference.

 

Btw. I've checked Console window of Developer Tools and there are a lots of JS errors

image.png

it seems you have some issues. I get some errors on JS that is referring to calling which is not there yet.

I also see some 401's at your screen are you the admin?

I've tried both accounts (admin and standard) and there is no difference.

Best Response confirmed by Lukáš Kubis (Occasional Contributor)
Solution

In order to see the connectors that disappeared, you have to (as an admin) go into your tenant settings and under Apps turn on "Enable new external apps by default." An update in August added Connectors to Apps and turned off external apps by default. We turned this setting on and restarted Teams and the connectors showed up. See the blog post about it here: https://techcommunity.microsoft.com/t5/Microsoft-Teams-Blog/New-admin-controls-for-apps-in-Teams/ba-....

 

Finally it started to work when I had enabled Incoming Webhook connector. No more 403 errors :)

How have you enabled it?  I am getting this below error while trying 

 

webhook message delivery failed with error: Microsoft Teams endpoint returned HTTP error 403 with ContextId