To enable the return of groups in a claim, there are two ways…<\/p>\n
The steps on enabling groups claim is outlined in the following article… Once enabled, groups will now be returned in the “groups” claim within a access token or ID token using OpenID Connect.<\/p>\n Important Note:<\/strong><\/p>\n Id tokens<\/strong> will only contain the groups claim if the openid<\/strong> value is included in the scope<\/strong> parameter.<\/p>\n When using, the Azure Active Directory Authentication library (ADAL<\/strong>) for dotnet, by default you may not get the groups claim. You may need to add the scope<\/strong> claim with the openid<\/strong> value as an ExtraQueryParameter<\/strong>.<\/p>\n Moving forward…<\/strong><\/p>\n The following groups claim description comes from https:\/\/docs.microsoft.com\/en-us\/azure\/active-directory\/develop\/access-tokens<\/a><\/p>\n 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 <\/em>application manifest<\/em><\/a>. 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 Office 365 Distribution Lists.<\/em><\/p>\n Examples\u2026<\/span><\/strong><\/p>\n For example, if you are using OAuth2 and getting a access token for Microsoft Graph, the groups claim will not be returned. This is because the application registration of Microsoft Graph does not have the groupMembershipClaims enabled.<\/p>\n Keep in mind, only the audience of the access token should be consuming the access token. In this case, the audience is Microsoft Graph. Microsoft Graph currently has no need to know what groups a user is a member of.<\/p>\n In another example, if the audience is Azure Storage Explorer, this first-party application registration does in fact return groups because it does have groupMembershipClaims enabled. This is because Azure Storage Explorer allows you to assign groups to access its resources so it needs to know what groups a principal is a member of.<\/p>\n So, if you want to get the groups claim from an access token, ensure the audience is for your application registration. Then you can have your application request a access token for another resource like Microsoft Graph. Otherwise, you can use the ID token issued by Azure AD when using OpenID Connect.<\/p>\n An Access Token and ID Token will look something like this with the “groups” claim…<\/p>\n { <\/span> By default, GUID’s are returned in the “groups” claim. If your group is synchronized to Azure AD using Azure AD Connect, you can then display the group name.<\/p>\n For more information about configuring the groups claim… Otherwise, if they are not synchronized, you will only get the GUID. You will need to make a separate call to Microsoft Graph to retrieve another value like its Display Name.<\/p>\n The Microsoft Graph call will look something like this\u2026<\/p>\n https:\/\/graph.microsoft.com\/beta\/users\/{user-id}\/memberOf<\/a><\/p>\n If using Azure AD Graph API (not recommended)\u2026. Instead of getting a “groups” claim, you will get a “hasgroups” claim.<\/p>\n The following description is from https:\/\/docs.microsoft.com\/en-us\/azure\/active-directory\/develop\/access-tokens<\/a><\/p>\n \u201chasgroups\u201d claim: If present, always true, denoting the user is in at least one group. Used in place of the groupsclaim for JWTs in implicit grant flows if the full groups claim would extend the URI fragment beyond the URL length limits (currently 6 or more groups). Indicates that the client should use the Graph to determine the user’s groups (<\/em>https:\/\/graph.windows.net\/{tenantID}\/users\/{userID}\/getMemberObjects<\/em><\/a>).<\/em><\/p>\n In this scenario, An Access Token and ID Token will look something like this with the “groups” claim…<\/p>\n { <\/span> For other flows, 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 to the claim sources pointing at the Graph endpoint containing the list of groups for the user. So, just like above, you will need to make a additional call to the Graph API endpoint to get the groups the user is a member of.<\/p>\n In this scenario, An Access Token and ID Token will look something like this with the “groups” claim…<\/p>\n { <\/span> “_claim_names”: { “groups”: “src1” },<\/p>\n “_claim_sources”: {<\/p>\n “src1”: { “endpoint”: “https:\/\/graph.windows.net\/{tenantID}\/users\/{userID}\/getMemberObjects” }<\/p>\n }, As for Azure AD B2C, when using user flow policies<\/strong>, the “groups” claim is not available. You will have to use the Graph API to get the list of groups the user is a member of.<\/p>\n Even though today, the endpoints provided by the claims above when the user is a member of too many groups is using the Azure AD Graph endpoint, we actually recommend using Microsoft Graph as the Azure AD Graph is being deprecated.<\/p>\n You can use Microsoft Graph to get a list of groups the user is a member of by following the guidance provided in the following article…<\/p>\n
\nhttps:\/\/docs.microsoft.com\/en-us\/azure\/active-directory\/hybrid\/how-to-connect-fed-group-claims<\/a><\/p>\n
\n
\n
\n\n
\nhttps:\/\/docs.microsoft.com\/en-us\/azure\/active-directory\/develop\/access-tokens<\/a><\/li>\n
\nhttps:\/\/docs.microsoft.com\/en-us\/azure\/active-directory\/develop\/id-tokens<\/a><\/li>\n
\nhttps:\/\/docs.microsoft.com\/en-us\/azure\/active-directory\/develop\/reference-saml-tokens<\/a><\/li>\n<\/ul>\n
\n
\n“typ”: <\/span>“JWT”,
\n“alg”: “RS256”,
\n“x5t”: “{x5t-value}”,
\n“kid”: “{kid-value}”
\n}<\/span>.{
\n“aud”: “{audience}”,
\n“iss”: “https:\/\/sts.windows.net\/{tenant-id}\/”,
\n…
\n“groups”: [ “group-id-1”, “group-id-2”,
\n…}.{signature}<\/span><\/p>\n
\nThere are some limitations\u2026<\/h3>\n
GUID’s returned only.<\/strong><\/h4>\n
\nhttps:\/\/docs.microsoft.com\/en-us\/azure\/active-directory\/hybrid\/how-to-connect-fed-group-claims<\/p>\n
\nhttps:\/\/graph.windows.net\/{tenant-ID}\/users\/{user-ID}\/getMemberObjects<\/a>”<\/p>\n
\nWhen using the OAuth2 implicit flow and the principal is a member of more than 5 groups\u2026<\/strong><\/h4>\n
\n“typ”: <\/span>“JWT”,
\n“alg”: “RS256”,
\n“x5t”: “{x5t-value}”,
\n“kid”: “{kid-value}”
\n}<\/span>.{
\n“aud”: “{audience}”,
\n“iss”: “https:\/\/sts.windows.net\/{tenant-id}\/”,
\n…
\n“hasgroups”: “true”,
\n…}.{signature}<\/span><\/p>\n
\nFor all other authentication flows\u2026<\/strong><\/h4>\n
\n“typ”: <\/span>“JWT”,
\n“alg”: “RS256”,
\n“x5t”: “{x5t-value}”,
\n“kid”: “{kid-value}”
\n}<\/span>.{
\n“aud”: “{audience}”,
\n“iss”: “https:\/\/sts.windows.net\/{tenant-id}\/”,
\n…
\n<\/span><\/p>\n
\n…}.{signature}<\/span><\/p>\n
\nAzure AD B2C<\/strong><\/h4>\n
\nUsing Microsoft Graph to get a list of groups a user is a member of.<\/h3>\n