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 Apps / Custom Connector OAuth...
Power Apps
Unanswered

Custom Connector OAuth issue: How to identify client dynamically during /authorize call?

(0) ShareShare
ReportReport
Posted on by
Hi,
 
I am working on a Power Apps Custom Connector (planning to publish it as a certified connector) using Generic OAuth 2.0 authentication.
 
My backend is based on IdentityServer (OAuth2) and supports a multi-tenant architecture (database per tenant).
 
All clients will use the same connector.
 
Architecture

Each client has a unique identifier (e.g., tenantId / clientId), which is required before authentication to:
  • Resolve the correct tenant
  • Select the appropriate database
  • Route to the correct identity provider (SAML / federated login)
Requirement
I would like to allow users to input a Tenant ID during connection creation, and pass it into the OAuth authorization request.

For example:

/connect/authorize?tenantId={tenantId}

Problem
It appears that:
  • The Authorization URL is treated as static
  • Connection parameters are not injected into the OAuth authorization request
  • Only standard OAuth parameters are sent:
    • client_id
    • scope
    • redirect_uri
    • state
Question
Is there any supported way in Power Platform connectors to:
  • Pass dynamic user-provided values (connection parameters) into the OAuth /authorize request? (Or)
  • influence parameter values dynamically?
Categories:
I have the same question (0)
  • Kushal_M Profile Picture
    251 Super User 2026 Season 1 on at
    Hello 
     
    No, not with the standard Generic OAuth 2.0 authentication model in Power Platform custom connectors.
    The OAuth configuration for a custom connector treats the authorization endpoint as essentially static. During the OAuth authorization code flow, Power Platform generates the /authorize request and only includes the supported OAuth parameters (such as client_id, redirect_uri, scope, response_type, state, etc.). User-defined connection parameters are not injected into the authorization request.

    You would like something like:
     
    https://identity.example.com/connect/authorize
        ?tenantId=<user-entered-value>
        &client_id=...
        &scope=...
    However, Power Platform does not provide a supported mechanism to:
    • Take a connection parameter entered by the user
    • Dynamically append it to the OAuth Authorization URL
    • Modify OAuth request parameters at runtime per connection
    This limitation applies to both custom connectors and certified connectors.
     

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 Apps

#1
Valantis Profile Picture

Valantis 481

#2
WarrenBelz Profile Picture

WarrenBelz 379 Most Valuable Professional

#3
11manish Profile Picture

11manish 291

Last 30 days Overall leaderboard