Forum Discussion
Azure AD Connect and "Exchange hybrid deployment" write-back
- 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.
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.
- David MachulaDec 04, 2018Copper Contributor
Why the need not to writeback?
When the Office 365 product was evaluated, the assumption was made that nothing from the "Cloud" would make changes to our local environment (so we would be "safe" ). Features like password writeback to local AD were thought to be strictly optional. This is what security and management understood at the time. I was asked to confirm that Exchange writeback is necessary for a hybrid environment (Yes, we do intend to run the HCW and setup a hybrid environment). Details on mailbox moves being written back to on-premises seems to be a compelling reason to enable this feature.
- DubC85Jun 20, 2019Copper Contributor
David Machula ChrisWebbTech Andy David
Wanted to add that if you're in an AD greenfield with Exchange Online only, AzureAD Connect will not writeback the mail attribute to the user account. The mail attribute would be quite necessary for many OnPrem applications/services.
- Dec 03, 2018Those 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 DavidDec 03, 2018MVP
Yep, I was responding to his comment "Is selecting this optional feature... mandatory... for Exchange hybrid environments?"
- Dec 03, 2018Ahhh, 10/4 :)