Agent Token Claims
In brief
The `tid` and `idtyp` claim names were corrected to remove extra spaces in the agent token claims table.
What Entra admins need to know
Administrators have clearer claim names when consulting the documentation; no action is required.
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.
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.
{
In v2 tokens, you see `azp` instead of `appid`. They both refer to the application ID of the agent identity.
You'd notice that the token includes a few claims that aren't previously seen in access tokens issued to applications. The following optional claims are also supported to identify that the tokens are for agent identities. They also provide more context in which the agent identity is acting.
- `xms_tnt_fct`
- `xms_sub_fct`
| Claim Name | Description |
| ----------- | ------------------------------------------------------- |
| `tid ``tid` | Tenant ID of the customer tenant |
| `idtyp ``idtyp` | `user` (indicating the subject is a user) |
| `xms_idrel` | `1` (indicating a member user; others possible too) |
| `azp` / `appid` | Application ID of the agent identity |
| `scp` | Delegated permissions granted to the agent identity |
@@ -20,7 +20,7 @@ Resource servers must validate the signature, issuer, audience, and lifetime bef ## 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](/entra/identity-platform/access-token-claims-reference). The following example shows a sample access token issued to an agent acting autonomously. +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](/entra/identity-platform/access-token-claims-reference). The following example shows a sample access token issued to an agent acting autonomously. ```json {@@ -51,7 +51,7 @@ Tokens issued for identities used for resource access include claims that you'd In v2 tokens, you see `azp` instead of `appid`. They both refer to the application ID of the agent identity. -You'd notice that the token includes a few claims that aren't previously seen in access tokens issued to applications. The following optional claims are also supported to identify that the tokens are for agent identities. They also provide more context in which the agent identity is acting. +You'd notice that the token includes a few claims that aren't previously seen in access tokens issued to applications. The following optional claims are also supported to identify that the tokens are for agent identities. They also provide more context in which the agent identity is acting. - `xms_tnt_fct` - `xms_sub_fct`@@ -141,8 +141,8 @@ In this scenario, the agent identity is acting on behalf of a human user. The ac | Claim Name | Description | | ----------- | ------------------------------------------------------- |-| `tid ` | Tenant ID of the customer tenant |-| `idtyp ` | `user` (indicating the subject is a user) |+| `tid` | Tenant ID of the customer tenant |+| `idtyp` | `user` (indicating the subject is a user) | | `xms_idrel` | `1` (indicating a member user; others possible too) | | `azp` / `appid` | Application ID of the agent identity | | `scp` | Delegated permissions granted to the agent identity | 