Microsoft Entra Agent ID
Standards

Agent OAuth flows: On behalf of flow

In brief

The article now describes hosted confidential-client agents, clarifies blueprint impersonation for multi-instance Agent IDs, and explains direct OBO for single-instance agents. It also updates supported grant types and consent guidance.

What Entra admins need to know

Administrators can use the guidance to select the correct OBO flow, permissions, and consent approach. No required action is stated.

This editorial summary was generated by AI from the documentation changes. Verify important details in the full Microsoft Learn article.

Documentation change

The comparison below shows only the changed extract. Use the full-page view for complete context.

Agent OAuth flows: On behalf of flow

Agents (agent identity blueprints)This article describes hosted, confidential-client agents operating on behalf of regular, signed-in users use the standard OAuth 2.0users. The protocol with all its capabilities. User delegation enables agent identitiesbelow applies to operate on behalf of signed-in users using standard OAuth 2.0 On-Behalf-Of flows with agent-specificmulti-instance Agent IDs and uses blueprint impersonation. The agent identity is assigned the necessaryneeds delegated permissions needed for OBO access. It requiresand user or administrator consent from users to access their data.the downstream API.

Agents haveA single-instance Agent ID performs OBO directly with the capabilities of Microsoft Entrashared client ID resource (API) applications and supporta credential configured on the API attributes required forblueprint. It doesn't use a blueprint impersonation token or inherit permissions from a blueprint principal. For its requests and the (OAuth2Permissions, AppURI)preview consent workaround, see Call a downstream API on behalf of a user with a single-instance Agent ID. Agent

In this confidential-client pattern, the agent identity blueprints canblueprint doesn't initiate an interactive authorization (/authorize) flows directly. They must receiveflow. It receives a user token from a client application and then performperforms an OBO token exchange. A web redirect URI can be configured on a blueprint for consent flows only (response_type=none), but it has limited functionality compared to a redirect URI onFor an app registration.agent that runs locally and signs in the user directly, see Authenticate a local agent with Microsoft Entra ID.

[!INCLUDE Use Microsoft SDKs]

Protocol steps

Agents arenThis OBO flow doesn't supported foruse an interactive (/authorize) flows.request. Supported grant types are client_credentialclient_credentials, jwt-bearer, and refresh_token. The flow involves the agent identity blueprint, agent identity, and a client credential. The client credential can be a client secret, a client certificate, or a Federated Identity Credentialfederated identity credential (FIC). When possible, use a managed identity to obtain the FIC.

:::image type="content" source="media/agent-on-behalf-of-oauth-flow/on-behalf-of-flow.png" alt-text="Diagram showing the illustration of on-behalf-of token acquisition flow for agents.":::

client_id=AgentBlueprint
&scope=api://AzureADTokenExchange/.default
&fmi_path=AgentIdentity
&client_assertion_type=urn:ietf:params:oauth:client-assertion-type:jwt-bearer
&client_assertion=TUAMI
&grant_type=client_credentials
```
Daily Entra.News

Get daily email updates

Get a concise summary of the latest Microsoft Entra updates delivered straight to your inbox.

Loading the secure signup form…