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:

Using connectors

I have the same question (0)

All responses (2)

Answers (0)

Suggested answer

Tomac 4,046 Moderator on at

Like (0)

Report
Copy link

Link copied!

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
Suggested answer

MM-26060905-0 15 on at

Like (0)

Report
Copy link

Link copied!

Hi all,

Just to add, if people are still experiencing these kinds of 403 issues but still need to retrieve or scrape content from a website, I’ve implemented a workaround that bypasses this limitation reliably.

Instead of relying on a basic HTTP GET from Power Automate, I use a lightweight Node.js setup (Playwright-based) hosted in Azure. It mimics a real browser session, which avoids most bot detection/cloud IP filtering issues.

It does require a small Azure deployment, but the implementation itself is straightforward and you don’t need to be a developer to use it once it’s set up.

If anyone needs this approach or wants a simple explanation of how to implement it, feel free to send me a message.

Was this reply helpful? Yes No