SAML token claims reference

The Microsoft identity platform emits several types of security tokens in the processing of each authentication flow. This document describes the format, security characteristics, and contents of SAML 2.0 tokens.

Claims in SAML tokens

Name Equivalent JWT Claim Description Example
Audience aud The intended recipient of the token. The application that receives the token must verify that the audience value is correct and reject any tokens intended for a different audience. <AudienceRestriction>
Authentication Instant Records the date and time when authentication occurred. <AuthnStatement AuthnInstant="2011-12-29T05:35:22.000Z">
Authentication Method amr Identifies how the subject of the token was authenticated. <AuthnContextClassRef>
First Name given_name Provides the first or "given" name of the user, as set on the Microsoft Entra user object. <Attribute Name="">
Groups groups Provides object IDs that represent the subject's group memberships. These values are unique (see Object ID) and can be safely used for managing access, such as enforcing authorization to access a resource. The groups included in the groups claim are configured on a per-application basis, through the "groupMembershipClaims" property of the application manifest. A value of null will exclude all groups, a value of "SecurityGroup" will include only Active Directory Security Group memberships, and a value of "All" will include both Security Groups and Microsoft 365 Distribution Lists.

If the number of groups the user is in goes over a limit (150 for SAML, 200 for JWT) then an overage claim will be added the claim sources pointing at the Graph endpoint containing the list of groups for the user.
<Attribute Name="">
Groups Overage Indicator groups:src1 For token requests that are not length-limited but still too large for the token, a link to the full groups list for the user will be included. For SAML this is added as a new claim in place of the groups claim.

The Azure AD Graph API is being replaced by the Microsoft Graph API. To learn more about the equivalent endpoint, see user: getMemberObjects.
<Attribute Name="">
Identity Provider idp Records the identity provider that authenticated the subject of the token. This value is identical to the value of the Issuer claim unless the user account is in a different tenant than the issuer. <Attribute Name="">
IssuedAt iat Stores the time at which the token was issued. It is often used to measure token freshness. <Assertion ID="_d5ec7a9b-8d8f-4b44-8c94-9812612142be" IssueInstant="2014-01-06T20:20:23.085Z" Version="2.0" xmlns="urn:oasis:names:tc:SAML:2.0:assertion">
Issuer iss Identifies the security token service (STS) that constructs and returns the token. In the tokens that Microsoft Entra ID returns, the issuer is The GUID in the Issuer claim value is the tenant ID of the Microsoft Entra directory. The tenant ID is an immutable and reliable identifier of the directory. <Issuer></Issuer>
Last Name family_name Provides the last name, surname, or family name of the user as defined in the Microsoft Entra user object. <Attribute Name="">
Name unique_name Provides a human readable value that identifies the subject of the token. This value is not guaranteed to be unique within a tenant and is designed to be used only for display purposes. <Attribute Name="">
Object ID oid Contains a unique identifier of an object in Microsoft Entra ID. This value is immutable and cannot be reassigned or reused. Use the object ID to identify an object in queries to Microsoft Entra ID. <Attribute Name="">
Roles roles Represents all application roles that the subject has been granted both directly and indirectly through group membership and can be used to enforce role-based access control. Application roles are defined on a per-application basis, through the appRoles property of the application manifest. The value property of each application role is the value that appears in the roles claim. <Attribute Name="">
Subject sub Identifies the principal about which the token asserts information, such as the user of an application. This value is immutable and cannot be reassigned or reused, so it can be used to perform authorization checks safely. Because the subject is always present in the tokens the Microsoft Entra ID issues, we recommended using this value in a general purpose authorization system.
SubjectConfirmation is not a claim. It describes how the subject of the token is verified. Bearer indicates that the subject is confirmed by their possession of the token.
<SubjectConfirmation Method="urn:oasis:names:tc:SAML:2.0:cm:bearer" />
Tenant ID tid An immutable, non-reusable identifier that identifies the directory tenant that issued the token. You can use this value to access tenant-specific directory resources in a multi-tenant application. For example, you can use this value to identify the tenant in a call to the Graph API. <Attribute Name="">
Token Lifetime nbf, exp Defines the time interval within which a token is valid. The service that validates the token should verify that the current date is within the token lifetime, else it should reject the token. The service might allow for up to five minutes beyond the token lifetime range to account for any differences in clock time ("time skew") between Microsoft Entra ID and the service. <Conditions

Sample SAML Token

This is a sample of a typical SAML token.

<?xml version="1.0" encoding="UTF-8"?>
<t:RequestSecurityTokenResponse xmlns:t="">
        <wsu:Created xmlns:wsu="">2014-12-24T05:15:47.060Z</wsu:Created>
        <wsu:Expires xmlns:wsu="">2014-12-24T06:15:47.060Z</wsu:Expires>
    <wsp:AppliesTo xmlns:wsp="">
        <EndpointReference xmlns="">
        <Assertion xmlns="urn:oasis:names:tc:SAML:2.0:assertion" ID="_3ef08993-846b-41de-99df-b7f3ff77671b" IssueInstant="2014-12-24T05:20:47.060Z" Version="2.0">
            <ds:Signature xmlns:ds="">
                    <ds:CanonicalizationMethod Algorithm="" />
                    <ds:SignatureMethod Algorithm="" />
                    <ds:Reference URI="#_3ef08993-846b-41de-99df-b7f3ff77671b">
                            <ds:Transform Algorithm="" />
                            <ds:Transform Algorithm="" />
                        <ds:DigestMethod Algorithm="" />
                <ds:SignatureValue>j+zPf6mti8Rq4Kyw2NU2nnu0pb{lots of characters}ut93UTyTAIGOs5fvP9ZfK2vNeMVJW7Xg==</ds:SignatureValue>
                <KeyInfo xmlns="">
                        <X509Certificate>MIIDPjCCAabcAwIBAgIQsRiM0jheFZhKk49YD0SK1TAJBgUrDg{lots of characters}OBcXWLAIarZ</X509Certificate>
                <NameID Format="urn:oasis:names:tc:SAML:2.0:nameid-format:persistent">m_H3naDei2LNxUmEcWd0BZlNi_jVET1pMLR6iQSuYmo</NameID>
                <SubjectConfirmation Method="urn:oasis:names:tc:SAML:2.0:cm:bearer" />
            <Conditions NotBefore="2014-12-24T05:15:47.060Z" NotOnOrAfter="2014-12-24T06:15:47.060Z">
                <Attribute Name="">
                <Attribute Name="">
                <Attribute Name="">
                <Attribute Name="">
                <Attribute Name="">
                <Attribute Name="">
                <Attribute Name="">
            <AuthnStatement AuthnInstant="2014-12-23T18:51:11.000Z">
        <SecurityTokenReference xmlns="" xmlns:d3p1="" d3p1:TokenType="">
            <KeyIdentifier ValueType="">_3ef08993-846b-41de-99df-b7f3ff77671b</KeyIdentifier>
        <SecurityTokenReference xmlns="" xmlns:d3p1="" d3p1:TokenType="">
            <KeyIdentifier ValueType="">_3ef08993-846b-41de-99df-b7f3ff77671b</KeyIdentifier>

Next steps