Forum Discussion

Copper Contributor

Dec 03, 2018

Solved

Azure AD Connect and "Exchange hybrid deployment" write-back

At a management level, one of the assumptions (correct or incorrect) when opting for Office 365 was that synchronization would be one-way (from our Active Directory to the Office 365/Azure). Unless o...

admin

Exchange Server

hybrid

Andy David
Dec 03, 2018
Why the need not to writeback?

If you have mailboxes both and in 365, you'll want that writeback enabled.

For example the legacyExchangeDN of a moved mailbox is written back as an X500 address on-prem to the remote mailbox .

If you dont have that, its going to cause issues for your Outlook clients with cached values and public folders.

https://docs.microsoft.com/en-us/azure/active-directory/hybrid/reference-connect-sync-attributes-synchronized

Andy David

MVP

Dec 03, 2018

Why the need not to writeback?

If you have mailboxes both and in 365, you'll want that writeback enabled.

For example the legacyExchangeDN of a moved mailbox is written back as an X500 address on-prem to the remote mailbox .

If you dont have that, its going to cause issues for your Outlook clients with cached values and public folders.

https://docs.microsoft.com/en-us/azure/active-directory/hybrid/reference-connect-sync-attributes-synchronized

ChrisWebbTech

MVP

Dec 03, 2018

Those Attributes write up to AzureAD/365 because all your changes should happen onprem :P. But he's referring to not having any users in 365 yet. In that case I don't see a requirement. But as you start adding any kind of Office 365 groups or anything of that nature you are definatley going to want a hybrid setup.

Andy David
MVP
Dec 03, 2018
Yep, I was responding to his comment "Is selecting this optional feature... mandatory... for Exchange hybrid environments?"
- ChrisWebbTech
  MVP
  Dec 03, 2018
  Ahhh, 10/4 :)