Azure AD for nested groups is now generally available!

[#1]

Hi Atlassian Community!

I’m Taylor, a Product Marketing Manager on the Enterprise Trust team. I’m excited to announce the general availability of Microsoft Azure Active Directory (AD) for nested groups. This custom integration supports flattening nested groups between Azure AD and Atlassian Cloud through Atlassian Access.

This integration addresses the requests we’ve received to add support for nested groups in Atlassian Cloud. Even though we don't support nested groups, we do keep your group memberships when you sync nested groups. This helps you manage permissions and mirror your internal organizational structure. You’ll see in the illustration below that organizations using Azure AD for nested groups can retain their org permissions through a flattened group structure. For example, with the flattened structure, all members of “Design”, “Grads”, and “Engineering” remain part of the larger Atlassian group. We recognize that some of our customers have faced challenges in moving from Server to Atlassian Cloud because of nested groups requirements. We created this integration to support our customers on their cloud migration journey. We recently completed our feature early access program (EAP) and now have many customers that are already using Azure AD for nested groups.

Using this new integration, you can now retain your nested structure in your Azure AD directory and use a flattened structure in Atlassian Cloud! We've published documentation explaining nested groups and how to approach them in the cloud. If you already provision users from Azure AD using SCIM, and would like to switch to using our custom integration, Azure AD for nested groups, read the instructions here.

Interested in getting started? Read our full documentation on Azure AD for nested groups.

[Yatish Madhav]

This new functionality - Yay! Need Enterprise plan - Doh! 

[Adrian Smith]

@Yatish Madhav I may have missed that. Where in the documentation does it show that the Enterprise Plan is required?

[Sayed Bares _ServiceRocket_]

Thanks for sharing! very useful feature specially for the organizations with complicated structure it saves tons of time when migrating to Atlassian access

[Kendall Alton]

The same concept should work for Atlassian Data Center, correct?   For role-based 'external user directory', we would enable both permissions and communication functionality.  This provides easy notification to a specific role, as well as assigning permissions specific to the role.  Users can self-maintain the membership that applies across multiple applications.