Microsoft Entra Agent ID
DeveloperMicrosoft Entra Sdk For Agent Identities
In brief
The documentation replaces “Entra ID Auth SDK” with “Microsoft Entra ID Auth SDK” in two descriptions. The endpoint formats and behavior are unchanged.
What Entra admins need to know
No administrator action is indicated; this is a terminology and branding clarification.
This editorial summary was generated by AI from the documentation changes. Verify important details in the full Microsoft Learn article.
Documentation change
View on Microsoft LearnThe comparison below shows only the changed extract. Use the full-page view for complete context.
Specify the downstream API by including its name in the request URL based on your Microsoft Entra ID Auth SDK (sidecar) configuration. The authorization header endpoint takes the format `/AuthorizationHeader/{serviceName}` where `serviceName` is the name of the downstream API configured in the SDK settings.
To acquire an app only token for an autonomous agent, you provide the agent identity client ID in the request.
For interactive agents, use the on-behalf of flow. The agent first validates the user token granted to it before acquiring the resource token to call the downstream API.
Agent web API receives user token from the calling application and validates the token via the Microsoft Entra ID Auth SDK (sidecar)
/Validateendpoint Acquire token for downstream APIs by calling/AuthorizationHeaderwith only theAgentIdentityand the incoming authorization header
@@ -49,7 +49,7 @@ These are the steps to acquire tokens using the Microsoft Entra ID Auth SDK (sid - Autonomous agent's user account: Agents operating on their own behalf using user principals created specifically for agents (for instance agents having their own mailbox). - Interactive agents: Agents operating on behalf of human users. - Specify the downstream API by including its name in the request URL based on your Entra ID Auth SDK (sidecar) configuration. The authorization header endpoint takes the format `/AuthorizationHeader/{serviceName}` where `serviceName` is the name of the downstream API configured in the SDK settings.+ Specify the downstream API by including its name in the request URL based on your Microsoft Entra ID Auth SDK (sidecar) configuration. The authorization header endpoint takes the format `/AuthorizationHeader/{serviceName}` where `serviceName` is the name of the downstream API configured in the SDK settings. 1. To acquire an app only token for an autonomous agent, you provide the agent identity client ID in the request. @@ -72,7 +72,7 @@ These are the steps to acquire tokens using the Microsoft Entra ID Auth SDK (sid 1. For interactive agents, use the on-behalf of flow. The agent first validates the user token granted to it before acquiring the resource token to call the downstream API. - Agent web API receives user token from the calling application and validates the token via the Entra ID Auth SDK (sidecar) `/Validate` endpoint+ Agent web API receives user token from the calling application and validates the token via the Microsoft Entra ID Auth SDK (sidecar) `/Validate` endpoint Acquire token for downstream APIs by calling `/AuthorizationHeader` with only the `AgentIdentity` and the incoming authorization header ```bash