Hey guys,
we are just in the preparation of an On-Premise AD migration. So it's On-Prem to On-Prem with hybrid connected Azure AD resources.
The AAD Connect is able to to watch into both forests. We have defined by sync rule that a migrated user object should only be synced from the new forest,
when extensionAttribute13 is filled with the string "Migrated". We utilize the correct source anchor, so this is really smooth without disable/enable
O365 licensing.
But for clients in the resource processing it is not that straight forward. Clients are synchronized to Azure and managed by Intune. By migrating the client from A to B
we receive a further object in Azure for the same client. No merging. The new one is quite empty while the former one is filled with information.
What have we done wrong and what is the best practise in such a common scenario?
Best regards,
Christian