You’re offline. This is a read only version of the page.
Announcements
Our company has a webhook feature that posts a simple payload of data to any HTTPS endpoint when certain things happen. This has worked with Microsoft Flow workflows for probably a couple of years now. About 10 days ago, about January 24th, all posts that are sent to any Microsoft Flow that listens with an HTTP Request are now getting 401 Unauthorized errors. To explain slightly more - when we send these POSTS from an interactive user in the browser, they work fine. When we send the same POST from a Windows app it works fine. However, when it the POST is sent from our Azure cloud service app, which is where they all come from, then it fails every single time. We are talking same exact JSON payload in every case, same exact code block sending the POST in every case. The only variable is that as of Jan. 24th Flow is now blocking these POSTs with a 401 error when it originates from an Azure cloud service app.
I just need to know what changed / why (our code for sending has not been altered in over 3 years). Also, is this a known issue / design change, and is there any way to work around it?
Thanks,
Steve
Hi @SteveMon ,
I'm afraid we don't currently have the right environment to test Azure cloud related issues.
Please consider contacting Microsoft Support directly to assist you with this issue:
Best Regards,
Share
Report
All responses (
Answers (
503
