Use managed identity in Power Platform custom connectors
Diesen Beitrag auf Deutsch lesen
Configure preview managed identity authentication in a custom connector to call Microsoft Entra ID protected APIs without client secrets.
Original article from March 10, 2026: Access APIs in Power Platform Without Secrets Using Managed Identity in Custom Connectors, by Mohamed Ashiq Faleel, on Mohamed Ashiq Faleel. Read the original
Source may be outdated. The original article is more than 60 days old. Dates and availability refer to the state of the source.
This is our own summary, not a republication or full translation.
TL;DR
Power Platform custom connectors can use preview managed identity authentication to access Microsoft Entra ID protected APIs without client secrets or certificates. Configure OAuth 2.0 with Managed Identity, register the connector redirect URL and federated credential in an Entra ID app, then create and use the connection in Power Apps or Power Automate.
Why it matters
- Makers: Configure OAuth 2.0 with Managed Identity in a custom connector, then define API actions and create a connection without entering a client secret.
- Admins/IT: Register a single-tenant Entra ID application, add the required API permissions, and establish federated credentials using connector-generated values.
- Makers: Treat this capability as preview and validate it before relying on it for production integrations.
Frequently asked questions
How do I enable managed identity for a Power Platform custom connector?
Select OAuth 2.0 and Azure Active Directory in the connector Security tab, then choose Managed Identity under Secret Options. Supply the application ID, tenant ID, resource URL, and scope.
What Entra ID configuration does a managed identity custom connector need?
The application registration needs the connector redirect URL and a federated credential. Use the connector-generated issuer and explicit subject identifier to establish trust.
Can a managed identity custom connector call Microsoft Graph from Power Automate?
Yes, the connector can be used from Power Automate after its connection is created. The example defines a GET action for the Microsoft Graph current user profile endpoint.