HTTP GET request fails since August without any modification

(2) Share

Report

Posted on by NR-20080858-1

Hi all,
I have a flow that is getting the information from a question in a form, a basic GET HTTP request to a microsoft form.

I use these parameters:

That I got from the Network tab:

It used to return header and body, but from August, I have a "bad request" error message. I tried to re-run the successful flows, but they now all fail with "Bad request" and I haven't changed anything...
I guess something has changed on Microsoft side but I can't figure out what.
Thank you so much for your help!

Categories:

Power Automate Desktop

All responses (3)

Answers (0)

Sort by

Michael E. Gernaey 53,970 Super User 2026 Season 2 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi,

It might be easier for others, but for me I cannot read your image, it has to be a lot bigger.

Please feel free to attach a large version, versus pasting it in.
Suggested answer

Michael E. Gernaey 53,970 Super User 2026 Season 2 on at

Like
a
(0)

Report
Copy link

Link copied!

So I kept trying lol to see whats there.

I can tell you have an Authorization Issue.

Can you share the full headers etc for the HTTP Get?

Also, can you verify who the action is run as?

Is this happening when you run it, or someone else?

I can totally get that since you didnt change anything ugg whats up. There have been some security enhancements and TPC / Network protocol changes. I am wondering if you are getting hit because you aren't doing any type of Challenge/Response to get a Token etc, where before you didn't need it, but now it seems you do.

I cannot read it perfectly, but when getting the Authorized Error, if I could see the whole error i might be able to see whats missing.
NR-20080858-1 13 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi FLMike,

I appreciate the time you took to reply to this thread.

The error on the right side was not really relevant as I was using Chrome and not the Flow. But I investigated authorisation rights and refreshed all my connections to Sharepoint. After reconnecting my account to sharepoint within the flows it worked.

This is bizarre as I got the problem from August and not from the last password change.

Anyway, it's working now, thanks for the insights on authorization.

Nicolas