Error 403 when trying to fetch a token using HTTP with Microsoft Entra ID (preauthorized)

(0) Share

Report

Posted on by BK-02091156-0

Hello everyone,

I am currently working with an API to update information in a maintenance plan. I am trying to retrieve the token using the HTTP connector in Power Automate, but I keep receiving a 403 error. When I test the same request in Bruno, it works without any issues, but it fails within the Power Automate flow.

Has anyone encountered this problem before or has experience working with APIs and Power Automate? I would greatly appreciate any suggestions or solutions.

Thank you in advance for your help!

Categories:

Power Automate Mobile App

Building flows

Using connectors

Using flows

Power Automate Desktop

Connector development

General topics

I have the same question (0)

All responses (3)

Answers (0)

Sort by

Expiscornovus 33,891 Most Valuable Professional on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @BK-02091156-0,

In the Outputs > Body I see an innerError: Have you double checked that error?

Is there any clue/additional information in that innerError?

Btw, I see the BASF API documentation is behind a login, that makes it a bit more difficult to troubleshoot as well.

https://developer.basf.com/apis

Happy to help out 😁

I share more #PowerAutomate and #SharePointOnline content on my Blog, LinkedIn, Bluesky profile or Youtube Channel

Was this reply helpful? Yes No
Suggested answer

stampcoin 5,171 Super User 2026 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

@BK-02091156-0 Hi,

As I understand you should use http connector rather than HTTP with Microsoft Entra ID (preauthorized).

You can start with App-Only Context ,like what you used in your screenshot, or contact them to get certification to use OAuth.

Reference link: https://developer.basf.com/authentication-and-authorization

Good luck.

Enjoy Power Platform and have a great day 🚀 | My LinkedIn

If the answer helps, please consider 👍, Thanks.

Was this reply helpful? Yes No
Suggested answer

nhkrizic 4 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi, just a quick question to help narrow this down:

Are you using the “Invoke an HTTP request” action with a pre‑authorized connection, or are you calling the API through the standard HTTP connector?

The reason I ask is that a 403 (Forbidden) usually means the account running the flow doesn’t have the required permissions for that API endpoint.

Bruno works because it uses your credentials, but Power Automate uses the connection owner’s identity — which may not have the same roles or API permissions.

If you’re calling a Graph or custom API, make sure the service account (or the user who owns the connection) has the correct role/permissions assigned.

Once the right permissions are granted, the 403 should disappear.

Let me know which connector you’re using and I can help you check the right setup.

Was this reply helpful? Yes No