Forum Discussion
AD Connect with an existing O365 Tenant
we're about to enable AD Connect for an active Office 365 tenant and need some clarifications. The Tenant is hosting O365 users with exchange online for the organization mail domain company.org but ...
Yes, UPN, Primary SMTP Address or "mail" are the fields used for "soft match", any should work. And yes on the management front, every scenario that involves directory synchronization requires you to have at least one Exchange box on premises, for management purposes. This is the only *supported* by Microsoft solution, although other configurations will still work. At the very least though, make sure you have the on premises AD schema extended with the Exchange attributes.
- Hello
what about possible impacts on exchange mailboxes when activating the sync ?
DO we have to manually modify the "exchange" properties of each AD users to reflect the Exchange Online users. before activating the sync ?- No, you don't. And you cannot, as you don't have the Exchange AD schema extensions available. The more important caveat here is that you will need to manage everything from on-premises once you "match" the objects, which includes the Exchange properties. This is the reason why Microsoft only "supports" configurations in which there is at least one Exchange server on premises, as the Exchange management tools are the only one supported for the task of managing Exchange objects and attributes.
- Hello Vasil,
I have installed an exchange 2016 server on-prem to be used as management for mailboxes.
I've also activated the ADConnect between the Domain and the tenant.
At the moment I've only enabled synchronization for a TEST OU where I moved an user.
The user has been replicated and now I see it int the tenant as "directory synced".
I expected to start seeing it also on the on-prem exchange server among the recipients but I don't.
