Cross Tenant Cross Region Resource Migration.

Question

We have around 20 VMs, 2 SQL server with Always on set up and couple of machines which has dynamic GP hosted on a subscription in Europe region. We initially wanted to move it to a different subscription and realised both belong to different directories. We then planned to move the subscription across directories and then move resources across subscriptions. However we realised the current set up is in Europe region and we want the infra to be moved to US region.

Can i get some suggestions and easiest way not to mess up with the infra and migrate them all?

we feel there are few limitations here. ASR cannot be used as it doesnt support cross tenant migration. Resource mover cannot be used as it doesnt support cross region. We are unable to do the Billing transfer as the existing azure subscription is in UK and the transfer request is for a different tenant in US region. We are planning to use Azure Migrate to achieve this. However post migration we also have a challenge to change the domain of the Migrated resources.

I would need your help to understand if we have to change the domain first and then migrate or Complete the Migration and then step into Domain change.

Any reference document to achieve this would be helpful.

Answer 1

Hi @Jahnavi ,

Welcome to Microsoft Q&A Forum, thank you for posting your query here!

Eather way you can do it the migration using Azure migrate.

Prepare the Target Environment Changing domain first later migration:

• In the target Azure tenant, create an additional domain controller within the desired virtual network.
• Ensure this domain controller is configured with appropriate settings, including DNS and network configurations, to support domain services.
• Promote the domain controller in the target tenant to act as a member of the existing domain, ensuring it is part of the domain you intend to migrate.
• Once the target tenant's domain controller is operational, update the domain configuration in the source tenant to enable migration.
• Update DNS records to reflect the new domain controller in the target tenant.

Do not want to change the domain first Else: -

if you don't want to change the domain in the source, create an additional domain controller in the target subscription, configure the target VNet's DNS server with the new domain controller's IP, log in using the local username and password, change the workgroup name to match the target domain, and then join the new domain.

Feel free to reach out if you have any further questions or need additional information—I’m happy to assist!

Please provide your valuable comments

Please do not forget to "Accept the answer” and “upvote it” wherever the information provided helps you, this can be beneficial to other community members.it would be greatly appreciated and helpful to others.