Migrate Azure AD Tenant to Tenant

Rahul 236 Reputation points
2020-08-15T23:30:31.167+00:00

Hi Team,

Need some advice in Azure AD tenant to tenant Migration. ( Not sure if this is available within Microsoft)

Aim: Migrate selected users/groups from one AD to new AD. It's a divestiture Migration scenario. Eg. Company ABC corp have one single AD consist of users from AAA and BBB companies but now they are separating. BBB going for his own AD and environment.

Existing Setup: Hybrid Azure AD Environment, Single AD forest.

Following is the approach consideration:

  1. Migrate only selected user from source AD to target AD. (On-Premises AD)
  2. After users got migrated to target AD. Setup AD connect and sync these users from target AD to Azure AD.

Let me know if the above approach is right or not , also any advice on best practices to achieve this scenario.

Also I got few doubt after migrating users from source to target AD. At what stage I need to move Custom domain from Source Azure AD to target Azure AD at very beginning or need to do this in the end ? What I'm thinking if we do batch-wise migration so we need to still keep the custom domain in source tenant till we completely migrate all selected users. But thinking if we didn't do this in the beginning then user sync via AD connect from new target on-prem AD to new Azure AD would fail because user in on-prem AD got custom domain in his UPN and email but when syncing to new Azure AD it's missing.

In case if we don't add custom domain then user would change to *.onmicrosoft.com domain and later we can add it to new Azure AD tenant and we will change primary domain for all users.

  • Regards,
Microsoft Entra ID
Microsoft Entra ID
A Microsoft Entra identity service that provides identity management and access control capabilities. Replaces Azure Active Directory.
19,454 questions

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. LIT-RS 1 Reputation point
    2020-11-07T19:40:46.007+00:00

    Hi Rahul @Rahul did you get this sorted? Interested also to understand how you plan to migrate the on-prem users too?

  2. Simon Burbery 546 Reputation points
    2022-04-08T11:53:44.917+00:00
    1. Quest AD migration is a great tool for the on-premises domain migration at a reasonable cost. Enable SID history so the users can still connect to resources as normal in the source domain while you move things across.
    2. We trust 'ProfWiz.exe' to migrate workstations into the new domain (although you can use Quest as well) - it is low-cost, seamless and allows the user to log in to the same profile in the new domain. i.e. manually mapped drives, print queues, wallpaper etc are retained and work as normal (based on using Quest to copy SID history, users and passwords to the new domain).
    3. You can now migrate the mailboxes cross-tenant using this procedure: https://learn.microsoft.com/en-us/microsoft-365/enterprise/cross-tenant-mailbox-migration?view=o365-worldwide. Another write up on this is here: https://www.howdoiuseacomputer.com/index.php/2022/04/02/microsoft-365-cross-tenant-migration. Forwarding is used to keep the mail flowing while you plan to migrate the custom domain across.
    4. You could also use cloud migration solutions such as BitTitan, SkyKick or Quest On-Demand Email migration to keep it simple but at a cost per mailbox.
    0 comments