Microsoft Entra Agent ID
Authentication

Agent Token Claims

In brief

The documentation now states that resource servers must validate token signatures, issuers, audiences, and lifetimes before using claims. It also clarifies that agent identity claims do not replace delegated scopes or application roles, and that `xms_par_app_azp` identifies the agent identity blueprint associated with the acting agent.

What Entra admins need to know

Administrators should review resource-server validation and claim-handling guidance, including interpretation of `xms_par_app_azp`.

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.

#customer-intent: As a developer or security engineer, I want to understand the token claims structure for Agent Identity tokens, so that I can properly validate and authorize agent applications in my resource servers and implement secure authentication flows.

Clients using agent identities are expected to treat the access tokens issued to them to use at resource servers as opaque, and not try to parse them. However, resource servers that receive access tokens issued to agents need to parse the tokens to validate them and extract claims for authorization purposes.

Resource servers must validate the signature, issuer, audience, and lifetime before using any claims. Agent identity claims describe the caller and its relationships; they don't replace the delegated scope or application role required by an operation. For implementation guidance, see Validate Agent ID tokens in a downstream API.

Core token claim types

Tokens issued for identities used for resource access include claims that you'd normally expect to see in access tokens that Microsoft Entra issues. For more information, see access token claim reference. The following example shows a sample access token issued to an agent acting autonomously. | 11 | AgentIdentity | | 13 | AgentIDUser |

You should ignore anyIgnore values that aren't relevant to your scenario or validation logic. Ignore the values that aren't relevant to your application. Don't assume any order of the values in these claims.

xms_par_app_azp

The xms_par_app_azp claim is used to identifyidentifies the parent application of the authorized party (azp or appid). It's a GUID, when included. You can useWhen included, its GUID identifies the claim to determineagent identity blueprint associated with the parentacting agent identity.

Log the parent application ID for auditing purposes. Microsoft Entra ID sign-in logs always includes the parent ID if available, so resource server should do the same. It isn't recommended to use the parent application ID for authorization decisions, as it would result in widespread access by many agents.

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…