Have a quick question regarding a first time sync of Azure AD Connect.
We're preparing a move to Exchange online, and part of that will be the synchronization of our on-premise AD accounts to Azure AD & 365.
Currently a number of staff in the company already have office 365 accounts (using it for SPOL, SFB and Onedrive), and their current UPNs for logging into these office 365 accounts are actually the same as there NT logins for the on-premises AD directory (e.g. email@example.com).
So when we try and do our initial sync with Azure AD Connect, I'm assuming we'll get numerous sync errors from Azure AD saying that a account already exists with the UPN or alias firstname.lastname@example.org
My question is, when we do this initial Azure AD Connect sync, is there a way of us instructing Azure AD/365 to merge this new on-premise account with the previously created 365 account of the same name/UPN? Or maybe the initial sync will do this automatically anyway?
Any helpful info on this would be greatly appreciated!!
I think it will work (no sync errors) as long as local UPN matches primary email address in Exchange Online.
But: You have to be aware that your local AD will now be the new master data source for all changes to users and groups and other objects. Anyway, it should be more or less safe to play with on test accounts, if you use Group based scoping (default in Express mode) instead of OU based filtering.