web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate / Error creating Custom ...
Power Automate
Suggested Answer

Error creating Custom Connector OAuth 2.0 authentication type

(0) ShareShare
ReportReport
Posted on by Microsoft Employee
When you try to enable OAuth 2.0 authentication type in Security Tab, you receive the following error and you are not able to continue with the creation/updating Custom Connector. This occurs both creting a new connector and updating an existing one. Dropdown for selecting Identity Provider do not show any value due to this error. I've tryied in 2 different tenants and different environments and the error always appears. 

Screenshot 2026-06-09 115242.png
I have the same question (0)
  • Suggested answer
    Sunil Kumar Pashikanti Profile Picture
    2,111 Moderator on at

    I’ve seen this exact issue recently, and your screenshot matches it perfectly. The empty Identity Provider dropdown with the “Error trying to load connection provider parameters” message is usually not a configuration issue.

    Since it’s happening across multiple tenants and environments, it’s very likely a platform or policy-related issue. In many cases, the maker portal is unable to load OAuth provider metadata due to things like tenant restrictions or backend service issues.

    What worked for me was:
    Use the Swagger editor and define OAuth 2.0 manually instead of relying on the dropdown
    Retry later or in a different browser session, as the issue can be intermittent
     
    Example (simplified):
    "securityDefinitions": {
      "oauth2_auth": {
        "type": "oauth2",
        "flow": "accessCode",
        "authorizationUrl": "https://login.microsoftonline.com/{tenant-id}/oauth2/authorize",
        "tokenUrl": "https://login.microsoftonline.com/{tenant-id}/oauth2/token",
        "scopes": {
          "api.read": "Read access"
        }
      }
    }
     
    If you want to confirm the root cause, open Dev Tools (F12), go to Network, and check for a failed request when opening the Security tab. That usually points to what’s being blocked.

    If it keeps happening, raising a support ticket might be necessary.

    ✅ If this answer helped resolve your issue, please mark it as Accepted so it can help others with the same problem.
    👍 Feel free to Like the post if you found it useful.
  • Suggested answer
    11manish Profile Picture
    2,837 on at
    There is possibility to policy related issue (As above mentioned).
     
    I would first check the browser's Network tab (F12) for failed requests and then consider opening a Microsoft Support ticket if the issue persists across multiple
     
    tenants and environments.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Season of Sharing Community Challenge Launch!

Jump in, show your community spirit, and win prizes!

Kudos to our 2025 Community Spotlight Honorees

Expanding mentorship, skilling, and AI innovation

Congratulations to the May Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Automate

#1
Valantis Profile Picture

Valantis 410

#2
Vish WR Profile Picture

Vish WR 289

#3
David_MA Profile Picture

David_MA 282 Super User 2026 Season 1

Last 30 days Overall leaderboard