Limitations of Azure AD for nested groups
Support for identity providers
You cannot connect more than one Azure Active Directory identity provider that flattens your nested groups. You can switch from Atlassian’s current SCIM solution to Atlassian’s custom integration for nested groups. Learn more about switching from SCIM to Azure AD for nested groups
Available attributes for mapping
The custom integration for Azure AD uses fixed attribute mapping between Azure Active Directory and your Atlassian cloud organization. This works with default mapping in Azure AD, but if you configure some custom mapping, you cannot use the custom integration for Azure AD.
Azure Active Directory Attribute | AtlassianCloud Attribute |
|---|---|
objectId | externalId |
mail OR userPrincipalName | userName |
givenName | name.givenName |
surname | name.familyName |
displayName | displayName |
mail OR userPrincipalName | emails[type eq "work"].value |
accountEnabled | active |
jobTitle | title |
preferredLanguage | preferredLanguage |
mobile | phoneNumbers[type eq "mobile"].value |
telephoneNumber | phoneNumbers[type eq "work"].value |
department | urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:department |
Was this helpful?