Users from Azure Ad get synced to crowd without group memberships

[Benjamin Brummer]

Crowd is syncing users from Azure Ad without group member-ships.

Audit log says "user xy created" and "group xz created" but user is not added.

The problem is that crowd startet to forget existing memberships.

Already tried:

• Deletet Azure Ad Directory and added it again.
• Enabled/Disabled Directory in Crowd
• Incremental and Full sync

[AnnWorley · Accepted solution]

Just wanted to call everyone's attention to the patch releases and other recent comments on the bug report: Azure AD synchronisation remove membership:

Hello,

The fix is available in Crowd 3.0.3, Crowd 3.1.4 and Crowd 3.2.2. It may however occur that Crowd continues to incrementally synchronize with Azure AD, not picking up the existing memberships. In such case please:

• Uncheck the "Enable incremental sync" checkbox
• Click the "Update" button
• Check the "Enable incremental sync" checkbox
• Click the "Update" button again

Best regards,
Patryk Petrowski

[Patryk]

That's correct, these versions contain the fix for membership synchronization issues with Azure Active Directory. Unfortunately I didn't get an answer wether the change in AAD was an intended one or a bug yet.

[Benjamin Brummer]

I think the answer can be found in the third comment https://jira.atlassian.com/browse/CWD-5192

[AnnWorley · Accepted solution]

Hi Benjamin,

Thank you for reporting this issue. There is a public-facing bug report for it now: Azure AD synchronisation remove membership 

For status updates, please watch that ticket. If you comment or vote on it you will automatically be added to notifications.

I would like to share this knowledge base article with a workaround: Export Azure Active Directory Users & Groups and Import into Crowd

Thanks,

Ann

[Benjamin Brummer]

Hope it will be fixed soon.

[Bruno Vincent]

Hello @Benjamin Brummer

Same behaviour here on two test instances (Crowd v3.1.2 & v3.2.1), Crowd's native Azure AD connector has lost all memberships, though synchronisation status is successful. I guess there must have been some changes on Azure AD side.

As a workaround you might want to take a look at and/or install the ODCC plugin which does not seem to be impacted according to my tests.

Important disclaimer: I work for the vendor of the ODCC plugin.

We also provide an emergency script that allows you to import your Azure AD users and groups in an internal Crowd directory if something goes wrong with Azure AD connectivity. This can help you to regain access to your applications if you're stuck right now. Please note that you don't need a license for this script.

[Benjamin Brummer]

Thanks for the script it safes a lot of time :-)

[Bruno Vincent]

Sure, no problem. I'm glad it helped! 🙂