We are currently facing an issue with our Azure AD integration. We have integrated Azure AD with our on-premises AD for user provisioning and SSO, following the official manual.
However, we encountered a problem: in our on-premises AD, there are about 300-400 groups that share the same logical name, but their system names are different. Group provisioning in Azure AD is based on the group name, and during synchronization with Atlassian, we are receiving errors indicating that there are duplicate groups. The error suggests renaming the groups in Azure AD, but this is not feasible, as these groups are tied to other systems.
Given this situation, we would like to know if it is possible to configure the synchronization process to use the system group names rather than the logical ones. Or, is the only solution to rename the groups in AD?
We appreciate any guidance or suggestions you can offer on how to proceed.
Thank you in advance for your assistance.
Choose the right Microsoft Azure AD option for you | Atlassian Support (our choice was option 2 cause we have nested groups)
