How to migrate Azure VM from one subscription to another subscription in same region with in same tenant and between two different tenant.

Thirutham Ram 0

Whether Azure migrate supports migrating Azure VM between two subscriptions in same region( in same tenant and between different tenants). With Backup you can restore the VM to another subscription in same region in same tenant.

Vidya Viraktamath 550 Reputation points Microsoft Employee

2025-02-20T14:26:00.28+00:00
Thanks for reaching out Microsoft Q&A.

Migrating Azure VMs

Azure offers a built-in move system for many resources, including virtual machines. However, there are some important considerations:

Dependencies: When moving a VM, you must migrate all dependent resources at the same time. This includes things like:

Managed disks

Network interfaces

Public IP addresses

Virtual networks

Network security groups

Limitations: Not all VMs can be moved. There are limitations based on:

VM size

Operating system

Storage configuration

Attached extensions

Availability sets

1. Same Tenant, Different Subscriptions

Supported: Yes, Azure Migrate supports migrating VMs between subscriptions within the same Azure Active Directory tenant.

Process:

Prepare the VM: Ensure the VM meets the requirements for migration (no unsupported features, dependencies identified).

Use Azure Resource Mover: This service simplifies the process. It helps you select the VM and its dependencies and guides you through the move.

Alternative Method (Manual):

Copy the snapshots to the new subscription.

Create new disks from the snapshots in the new subscription.

Create a new VM in the new subscription, attaching the copied disks.

Reconfigure any settings (network, etc.) as needed.

2. Different Tenants

Supported: Yes, but it requires a slightly different approach.

Process:

Prepare the VM: As before, ensure the VM is compatible with migration.

Export Disks: Export the VM's OS and data disks to VHD files. You'll need to download these files.

Upload Disks: Upload the VHD files to a storage account in the destination tenant.

Create VM: Create a new VM in the destination tenant, using the uploaded VHD files as the disks.

Reconfigure: Adjust network settings, security, and any other configurations to match the new environment.

Important Notes

Backup: Always back up your VM before any migration, just in case something goes wrong.

Downtime: There will likely be some downtime during the migration process. Plan accordingly.

Testing: After the migration, thoroughly test the VM in the new subscription to ensure everything works as expected.

Permissions: You'll need appropriate permissions in both the source and destination subscriptions to perform the migration.

Azure Migrate

While Azure Migrate is a powerful tool for migrations, it's primarily designed for migrating VMs to Azure from on-premises environments or other clouds. For subscription-to-subscription moves, Azure Resource Mover is generally the recommended approach.

Key Resources

Move Azure resources to a new resource group or subscription: https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/move-resource-group-and-subscription

Move Azure VMs across tenants: https://learn.microsoft.com/en-us/azure/resource-mover/tutorial-move-region-virtual-machines

https://learn.microsoft.com/en-us/azure/virtual-machines/windows/disks-upload-vhd-to-managed-disk-powershell

Thanks for reaching out Microsoft Q&A.

Migrating Azure VMs

Azure offers a built-in move system for many resources, including virtual machines. However, there are some important considerations:

Dependencies: When moving a VM, you must migrate all dependent resources at the same time. This includes things like:

Managed disks

Network interfaces

Public IP addresses

Virtual networks

Network security groups

Limitations: Not all VMs can be moved. There are limitations based on:

VM size

Operating system

Storage configuration

Attached extensions

Availability sets

1. Same Tenant, Different Subscriptions

Supported: Yes, Azure Migrate supports migrating VMs between subscriptions within the same Azure Active Directory tenant.

Process:

Prepare the VM: Ensure the VM meets the requirements for migration (no unsupported features, dependencies identified).

Use Azure Resource Mover: This service simplifies the process. It helps you select the VM and its dependencies and guides you through the move.

Alternative Method (Manual):

Copy the snapshots to the new subscription.

Create new disks from the snapshots in the new subscription.

Create a new VM in the new subscription, attaching the copied disks.

Reconfigure any settings (network, etc.) as needed.

2. Different Tenants

Supported: Yes, but it requires a slightly different approach.

Process:

Prepare the VM: As before, ensure the VM is compatible with migration.

Export Disks: Export the VM's OS and data disks to VHD files. You'll need to download these files.

Upload Disks: Upload the VHD files to a storage account in the destination tenant.

Create VM: Create a new VM in the destination tenant, using the uploaded VHD files as the disks.

Reconfigure: Adjust network settings, security, and any other configurations to match the new environment.

Important Notes

Backup: Always back up your VM before any migration, just in case something goes wrong.

Downtime: There will likely be some downtime during the migration process. Plan accordingly.

Testing: After the migration, thoroughly test the VM in the new subscription to ensure everything works as expected.

Permissions: You'll need appropriate permissions in both the source and destination subscriptions to perform the migration.

Azure Migrate

While Azure Migrate is a powerful tool for migrations, it's primarily designed for migrating VMs to Azure from on-premises environments or other clouds. For subscription-to-subscription moves, Azure Resource Mover is generally the recommended approach.

Key Resources

Move Azure resources to a new resource group or subscription: https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/move-resource-group-and-subscription

Move Azure VMs across tenants: https://learn.microsoft.com/en-us/azure/resource-mover/tutorial-move-region-virtual-machines

https://learn.microsoft.com/en-us/azure/virtual-machines/windows/disks-upload-vhd-to-managed-disk-powershell
Thirutham Ram 0 Reputation points

2025-02-20T14:45:09.5633333+00:00

I want to keep my source VM intact for failback.

1 answer

Ashok Gandhi Kotnana 3,540 Reputation points Microsoft Vendor

2025-02-20T15:08:01.41+00:00
Hi @Thirutham Ram ,

Please find the below solution for your scenario

Same Tenant: In a DR scenario, the VM replicates; during failover, a new VM is created in the target subscription, where you can see the "Reprotect" option for failback here vm is intact no issues using ASR

Different Tenant: Azure Migrate doesn’t support failback; you need a Configuration Server to keep the source VM intact and use ASR modernization for failover and failback.

Azure Migrate Cutover: Once cutover is done, failback is not possible.

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.
Please sign in to rate this answer.
Thirutham Ram 0 Reputation points

2025-02-20T15:37:17.8766667+00:00

I am looking for same tenant and same region.

Case 2: Azure Migrate should be deployed as Physical server migration. I tried with Azure migrate with in same region. Mobility agent got installed but not reporting in Azure migrate console. CS installed as physical server

Ashok Gandhi Kotnana 3,540 Reputation points Microsoft Vendor

2025-02-20T15:55:19.5966667+00:00

Hi @Thirutham Ram ,

Please refer to my step1 above

Same Tenant and Same region Azure Migrate is not required; simply enable Disaster Recovery from the VM blade, perform failover, reprotect, and failback within the same tenant.

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

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.

Thirutham Ram 0 Reputation points

2025-02-20T16:30:55.5133333+00:00

Same Tenant and Same region Azure Migrate is not required; simply enable Disaster Recovery from the VM blade, perform failover, reprotect, and failback within the same tenant.

VM Source region will not show in Disaster Recovery.

Ashok Gandhi Kotnana 3,540 Reputation points Microsoft Vendor

2025-02-20T17:00:06.41+00:00

Hi @Thirutham Ram ,

Thanks for the response back.

Since we are initiating the failover from the VM Blade, it won't show source VM. This is expected because we are already within the source VM. Additionally, performing a disaster recovery does not require explicitly selecting a source VM

Refer: https://learn.microsoft.com/en-us/azure/site-recovery/vmware-azure-reprotect

Note: if you are doing the disaster recovery from recovery service vault you can see the source and target

Refer: https://learn.microsoft.com/en-us/azure/site-recovery/azure-to-azure-tutorial-enable-replication

Thankyou

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.

Thirutham Ram 0 Reputation points

2025-02-20T17:30:11.6633333+00:00

I can't see my required region in Target. In the screen shot my VM source region is south India.

Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Ashok Gandhi Kotnana 3,540 Reputation points Microsoft Vendor

2025-02-21T03:04:17.53+00:00

Hello Thirutham Ram,

Disaster Recovery (DR) cannot be performed within the same region. Additionally, two separate questions are being addressed here.

Migration

DR (Source intact)

DR means different region, same regions you cannot do dr, when a disaster happen in the same region both will go down, disaster will not allow you to replicate on the same region

For south India you can replicate nearby region central india

Refer: https://learn.microsoft.com/en-us/azure/reliability/regions-paired#list-of-region-pairs

If you want same region, just do this thing this will solve your issue. Take snapshot in the source vm and select target subscription which taking the snapshot

Crate a disk from snapshot and create a vm from the disk

It will create in the same region in target subscription

Important Note: While taking the snapshot select target subscription region below screenshot for your reference.

DR is a separate issue that you have so I would suggest to log separate question for it and mark this as answered if this conversation helped you, I hope I have answered your questions.

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.

Ashok Gandhi Kotnana 3,540 Reputation points Microsoft Vendor

2025-02-24T05:26:58.2866667+00:00

Hello Thirutham Ram,

Just want to check if the above answer worked for you or else please let us know if any help, we are always here to help whenever you need us.

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.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

How to migrate Azure VM from one subscription to another subscription in same region with in same tenant and between two different tenant.

1 answer

Your answer