Hey everyone! We're currently working on implementing group writeback in our hybrid setup, but we've hit a significant snag. When we add a user to a cloud group through our on-premises Active Directory, that change doesn't sync back to Entra ID, leading to a mismatched status between our on-prem AD and the cloud. How are you all managing this? Do you typically manage all groups on-prem, or do you have any policies in place to prevent these kinds of issues?
3 Answers
Just a heads-up, writeback is usually meant for one-way syncing from cloud to on-prem. Managing group members locally isn’t really the way it’s supposed to work. You should handle group management directly in Entra going forward.
It looks like you're not pointing to the right group in your local AD. Ensure you're checking the correct group settings because writeback on itself should work fine. If you add a user in the cloud, it should sync back as expected.
FYI, group writeback is actually reaching its end of life. There was a recent announcement about it being discontinued, so it might be a good time to rethink your approach and move everything to the cloud.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures