Adaptive Cards Error: “The remote endpoint returned an error HTTP 401."

%3CLINGO-SUB%20id%3D%22lingo-sub-2292256%22%20slang%3D%22en-US%22%3EAdaptive%20Cards%20Error%3A%20%E2%80%9CThe%20remote%20endpoint%20returned%20an%20error%20HTTP%20401.%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2292256%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20All%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhen%20trying%20to%20send%20an%20adaptive%20card%20with%20Action.Http%20through%20Power%20Automate%2C%20the%20first%20flow%20works%20perfectly%2C%20sends%20the%20email%2C%20I%20type%20in%20the%20information%20I%20need%20to%20send%20back%2C%20but%20when%20I%20go%20to%20hit%20submit%2C%20it%20returns%20the%20error%3A%26nbsp%3B%E2%80%9CThe%20remote%20endpoint%20returned%20an%20error%20HTTP%20401.%22.%20However%2C%20I%20checked%20the%202nd%20flow%20which%20receives%20the%20Http%20request%20on%20Postman%20and%20everything%20is%20working%20on%20that%20end%20as%20well.%20I%20registered%20my%20team%20alias%20to%20send%20emails%20and%20that%20was%20approved%20so%20I%20am%20not%20sure%20why%20this%20is%20happening.%20Any%20help%20would%20be%20much%20appreciated.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2486478%22%20slang%3D%22en-US%22%3ERe%3A%20Adaptive%20Cards%20Error%3A%20%E2%80%9CThe%20remote%20endpoint%20returned%20an%20error%20HTTP%20401.%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2486478%22%20slang%3D%22en-US%22%3EYes%20same%20issue%20here.%20I%20registered%20everything%20properly%20with%20the%20originator%20and%20everything.%20I'll%20see%20if%20I%20can%20reach%20out%20to%20microsoft.%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E
Occasional Visitor

Hi All,

 

When trying to send an adaptive card with Action.Http through Power Automate, the first flow works perfectly, sends the email, I type in the information I need to send back, but when I go to hit submit, it returns the error: “The remote endpoint returned an error HTTP 401.". However, I checked the 2nd flow which receives the Http request on Postman and everything is working on that end as well. I registered my team alias to send emails and that was approved so I am not sure why this is happening. Any help would be much appreciated.

 

Thanks!

3 Replies
Yes same issue here. I registered everything properly with the originator and everything. I'll see if I can reach out to microsoft.

@danielledavid 

 

I too faced this problem.  It was resolved after adding an empty Authorization header.

 

The When a HTTP request is received trigger does not expect any credentials, but Outlook automatically sends out a bearer token when you submit an Actionable Message by default. This will lead to a HTTP Unauthorized error message

 

TechieMani_0-1626083670767.png

 

To avoid this, you must provide a Header with an empty Authorization token inside:

1
2
3
4
"headers": [ {
  "name": "Authorization",
  "value": ""
} ]
I faced the same issue. Thanks for the help and saving of time !