-
Title
Removal of Domain in Source environment breaks ODM Discovery -
Description
If I have David.Smith@domainx.com
I move Domainx to target environment.
Microsoft now displays users UPN as <GUID>@domainx.onmicrosoft.com in source Environment.
If you run an ODM discovery the object shows up as unlicensed. -
Resolution
UPDATE - It has been confirmed that if you wait a while (~Approximately 4+ hrs to over night) M365 updates the <Guid> in the UPN back to the proper UPN, so no further action is required. As once the UPN is properly displayed then the objects show as licensed and equipped with mailboxes and OneDrive's as licensed.
Cloud Only
If this is a cloud only object OR if MSDirSync (Microsoft Directory Synchronization) doesn't update it, you have to manually update the user's UPN in the Source Tenant.
Once these users are updated, then you can run ODM Discovery and the object will show as licensed.Hybrid
If this is a Hybrid environment you can run a MSDirSync and that will update the users in the tenant and then you can run the Discovery to update ODM and the object will show as licensed.
-
Additional Information
Note: It appears that the UPN can be updated to anything so it might just be the object touch in the source tenant that somehow fixes whatever happened to make objects appear as not discoverable as licensed. In one Example, we tried removing a couple chars from the GUID Microsoft assigns it and now ODM can discover it successfully as licensed.