You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hi
according to this bug report this issue should have been solved
But I still get groups and users synchronized but without group membership.
Hello Torbjörn,
Thanks for reaching out about your Crowd and Azure AD sync issues. I want to understand a bit more on how you’re syncing Crowd with Azure AD. When you’re running the sync, is incremental sync enabled? If so, could you possibly disable this and attempt a full sync to see if the groups and/or nested groups are then synced to Crowd?
Further information on this may be found at Configuring a Remote Crowd Directory
If this is the case, this could be due to the way Active Directory tracks changes to groups and nested groups in the sense that it doesn’t change the metadata for “updated” when a nested group is changed. Further information on this may be found at Nested Groups in Crowd.
We look forward to hearing back.
Regards,
Stephen Sifers
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.