HTTP GET suddenly returning 403 Forbidden (worked a few weeks ago)

(0) Share

Report

Posted on by MM-26060905-0

Hi everyone,

I’m running into an issue with an HTTP GET request in Power Automate. This flow used to work fine a few weeks ago, but now the same request consistently returns a 403 Forbidden error.

I already tried:

Adding a custom User-Agent header to avoid being detected as a bot
Testing different standard headers
Recreating the HTTP action

None of these attempts made any difference and I still get a 403 response.

Because the request used to work and nothing changed on my side, I suspect the target website may have recently added stricter bot detection, firewall rules, or IP blocking for cloud traffic.

Has anyone experienced something similar?

Do I need to add additional headers (cookies, referer, origin), or is it more likely that the site has started blocking Azure/Power Automate IP ranges?

Any suggestions on how to troubleshoot this or confirm the cause would be greatly appreciated.

Thanks!

Categories:

Licensing

I have the same question (0)

All responses (1)

Answers (0)

Suggested answer

Tomac 3,914 Moderator on at

Like (0)

Report

HTTP GET suddenly returning 403 Forbidden (worked a few weeks ago)

Hi @MM-26060905-0

As you suspected, a 403 Forbidden error is returned by the remote server, so your GET request is being blocked by the source, not failing at Power Automate. You'll need to reach out to the owner of the server you're getting the content from and ask them about the error.

Was this reply helpful? Yes No