Forum Discussion
Incomplete sync of Exchange Message Moderation settings to Office 365 / Exchange Online
Reading here the msExchBypassModerationLink attributed has been supported by AADConnect since version 1.1.524.0
https://docs.microsoft.com/en-us/azure/active-directory/hybrid/reference-connect-sync-attributes-synchronized
So it appears to be a bug where Azure AD isn't anchoring the attribute to only be controlled by on-premises.
1.1.880 isn't particularly old so I don't think it will be that. I'll double check in my lab tomorrow for you.
Brian
I have checked in my lab and this is my experience. If I enabled moderation on a synchronised mail enabled distribution list, the updates are shown in the export in the Synchronisation Service Manager. Please check the attached pictures and make the changes in your environment to see if AADConnect is picking up the change and synchronising it.
You can see I made two changes, one to enable moderation and another to change moderation notifications - both are picked up by AADConnect and synchronised over.
Can you check this and report back your findings for synchronisation flow?
Thanks for testing that. I can confirm everything comes over except for when I put groups in the senders that don't require approval. I just added another group and will capture the synch and share it shortly.
Brian
I am getting the same experience as you for both Exchange 2010 and Exchange 2013 Hybrid labs. I haven't had the chance to test in Exchange 2016.
msExchBypassModerationLink is successfully synchronised from on-premises through AADConnect and reflected in Exchange Online EAC, however I can simply add and remove users at my desire for moderator bypass, where making other changes are blocked because the object is synchronised from on-premises via AADConnect.
Reading here the msExchBypassModerationLink attributed has been supported by AADConnect since version 1.1.524.0
https://docs.microsoft.com/en-us/azure/active-directory/hybrid/reference-connect-sync-attributes-synchronized
So it appears to be a bug where Azure AD isn't anchoring the attribute to only be controlled by on-premises.
