Custom Connector OAuth 2.0 'Error trying to load connection provider parameters'

(3) Share

Report

Posted on by TI-09120726-0

Hello,

I am experiencing an issue when accessing the Security tab of any Custom Connector I create across several environments.

Error Message:

Error trying to load connection provider parameters. Try refreshing the page or check your network settings.

Environment Details

User role: System Administrator
User role: Environment Maker
Issue occurs in Power Apps and Power Automate
Issue occurs across several environments I have access to
Issue occurs for all custom connectors (existing and newly created)
Multiple browsers tested
Incognito/InPrivate mode tested
Cache cleared
Different environments tested
Different custom connectors tested
No DLP available

Additional Findings

Browser Developer Tools (F12) show two requests returning HTTP 403 (Forbidden) when opening the Security tab and switching to oauth 2.0 authentication.

Screenshot of the issue

How it should look like

Custom connector Security tab with OAuth 2.0 client credentials configuration

Did anyone encounter such an issue and how did you solve it? Is there a workaround for this issue? Is there a tenant level security setting that might cause this?

Thanks in advance for your assistance.

Best regards,

Tamer

Categories:

Connector development

I have the same question (0)

All responses (8)

Answers (0)

Sort by

CU09061008-0 2 on at

Like (1)

Report
Copy link

Link copied!

Same error here. I've reported some minutes ago but not published yet

Was this reply helpful? Yes No
Suggested answer

11manish 3,038 on at

Like (1)

Report
Copy link

Link copied!
Based on the symptoms, this does not appear to be a configuration issue within an individual custom connector. The most likely causes are:

A tenant-level Power Platform or Entra ID restriction.

A backend permission issue affecting OAuth provider parameter retrieval.

A Microsoft platform regression affecting Custom Connector OAuth configuration.

The next critical step is to inspect the 403 response payload in the browser network trace.

That response usually contains the information needed to determine whether the failure is caused by tenant policy, missing permissions, or a service-side issue.

If the response does not clearly identify the cause, a Microsoft support case is likely required because the failure is occurring before the OAuth configuration can

even be loaded.

Was this reply helpful? Yes No
Suggested answer

Valantis 6,526 on at

Like (2)

Report
Copy link

Link copied!

Hi @TI-09120726-0,

This is not a connector configuration issue.

The 403 error appearing when the Security tab loads before you've entered any OAuth settings means the Power Platform backend is being blocked from fetching the OAuth provider parameters from an external endpoint. This is a tenant-level restriction.

Most likely cause: your organization has Conditional Access policies or Entra ID app restrictions that block the Power Platform service from making the necessary calls to load OAuth provider metadata. This is common in highly locked-down tenants.

check this pelase:

1. Look at the 403 response body in browser DevTools (F12 > Network tab > click the failing request > Response). The body usually contains the specific policy or permission that's blocking it.

2. Check Entra ID > Sign-in logs for the Power Platform service principal. Look for blocked sign-ins around the time you open the Security tab.

3. Check if your tenant has "Restrict non-admin users from creating tenants" or app registration restrictions that could affect Power Platform's ability to access OAuth metadata endpoints.

4. Raise a Microsoft support ticket with the 403 response payload from DevTools attached. This is a tenant-level platform issue that only Microsoft support can diagnose from their side.

The fact that it affects all environments and all users confirms this is tenant-wide, not environment-specific.

Best regards,

Valantis

✅ If this helped solve your issue, please Accept as Solution so others can find it quickly.

❤️ If it didn’t fully solve it but was still useful, please click “Yes” on “Was this reply helpful?” or leave a Like :).

🏷️ For follow-ups @Valantis.

📝 https://valantisond365.com/

💼 LinkedIn

▶️ YouTube

Was this reply helpful? Yes No
SF-09061337-0 2 on at

Like (1)

Report
Copy link

Link copied!
In my case is a problem of CORS not a 403 error (or 500).

From browser developer tools:

"Access to XMLHttpRequest at: https://tip1-shared.consent.azure-apim.net/api/providers/{0}/parameters from origin: https://make.powerautomate.com has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource."

Additionally:

Requests to /parameters (and /providers/.../parameters) endpoints also fail with same issue

The {0} placeholder is not replaced in the request URL

Backend response lacks required CORS headers

Browser blocks request → UI fails

Then:

Cannot configure OAuth 2.0 authentication for new custom connectors

Cannot update existing connectors (e.g., change Client ID / Secret)

Blocks implementation of secure backend APIs using Azure AD

Affects development and ALM processes

Other details

I could reproduce the same issue in:

Multiple environments

Multiple tenants

Different browsers

Occurs consistently when selecting OAuth 2.0

Happens for both:

New connectors

Existing connectors being edited

Was this reply helpful? Yes No
TI-09120726-0 71 on at

Like (0)

Report
Copy link

Link copied!

Hello @SF-09061337-0,

I got the same problem of CORS which resulted in a 403 error.

I also faced the same issue on different tenants as well not just environments.

Was this reply helpful? Yes No
Suggested answer

Valantis 6,526 on at

Like (2)

Report
Copy link

Link copied!

Hi @TI-09120726-0,

Thanks for the CORS details this changes the diagnosis completely.

The {0} placeholder not being replaced in the request URL (https://tip1-shared.consent.azure-apim.net/api/providers/{0}/parameters) is the smoking gun. This is a bug in the Power Platform frontend the URL template isn't being populated before the request is made, so the CORS check fails on a malformed endpoint.

The fact that SF-09061337-0 reproduced it across multiple tenants confirms this is a platform-level regression, not a tenant policy issue. My original diagnosis was wrong for this case.

What to do now:

1. Check Microsoft Service Health at admin.microsoft.com > Health > Service health for any active Power Platform or Power Automate incidents related to custom connectors or OAuth configuration.

2. Raise a Microsoft support ticket and reference the {0} placeholder bug in the URL specifically this is a frontend rendering issue that needs engineering to fix.

3. Check the Power Platform Message Center for any announcements about connector service updates in the past 24-48 hours.

This is blocking connector development for multiple users. The more support tickets raised with this specific CORS error and the malformed URL, the faster it gets prioritized.

Best regards,

Valantis

✅ If this helped solve your issue, please Accept as Solution so others can find it quickly.

❤️ If it didn’t fully solve it but was still useful, please click “Yes” on “Was this reply helpful?” or leave a Like :).

🏷️ For follow-ups @Valantis.

📝 https://valantisond365.com/

💼 LinkedIn

▶️ YouTube

Was this reply helpful? Yes No
stampcoin 5,166 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

For me, the problem is gone, but the issue is still Active.

https://admin.powerplatform.microsoft.com/support/knownissues/6479501

Was this reply helpful? Yes No
Valantis 6,526 on at

Like (1)

Report
Copy link

Link copied!

Hi @TI-09120726-0,

Just wanted to check in and see if everything is working now. If you still need any help, feel free to let me know.

Also, if the issue is resolved, it would be great if you could mark the answer as solved so others with the same question can find it easily.

Thanks and have a great day!

Was this reply helpful? Yes No