<img height="1" width="1" style="display:none" src="https://www.facebook.com/tr?id=578826073428599&amp;ev=PageView&amp;noscript=1">
Remotely Blog

How to migrate an Azure virtual machine from one tenant to another

System administrators are often tasked with migrating existing virtual machines from one of their tenants to another. At first glance, this task can appear to be daunting. Luckily, Microsoft offers a free tool called Azure Storage Explorer which offers the ability to log into multiple Azure tenants to monitor and manage resources within your environment(s). This article will walk through how to migrate an Azure virtual machine from one tenant to another.

1. Selecting your Azure resource

After installing and opening Azure Resource Explorer you will be asked which Azure resource you are connecting to. For virtual machine (VM) migrations from one tenant to another, you should select Subscription. This will allow you to view and manage your virtual disks that make up the VM. Sign into the Azure tenant you will be moving the VM out of; the source.


2. Sign into the Azure tenant

Next, sign into the Azure tenant you will be moving the VM into; the target. To sign into another subscription:

  1. Select the User icon in the left toolbar
  2. Select Add an account

To add additional tenants, repeat the actions listed above. The screenshot below shows 3 separate Azure accounts being added to the Azure Storage Explorer client.


3. Shut down the VM being migrated

It is important that the VM you are migrating is completely shut down before proceeding with the migration process. Once the VM is shut down from the Azure portal, locate the disk that is associated with the VM being moved out of the tenant. This disk will be listed under the Disks dropdown. You will then need to locate which Resource Group the disk is located in. In the example below you will see a VM called REMAZLAMP-001 located inside the Remotely_Dev Resource Group within the RemotelyRMMDev tenant. We will be migrating this VM out of the current tenant and into another tenant that we are signed into the Storage Explorer with.

4. Copy and pasting the VM disk

Once the context is on the source VM disk, you will be prompted with the following options:

  • Upload
  • Download
  • Copy
  • Paste
  • Create a snapshot

For migrating this VM disk, ensure that the source disk is highlighted, the select and choose the Copy button. In this exercise, the VM has two disks - an OS disk and a data disk. We will need to perform the following steps twice - once for each disk.


When the source disk is copied, navigate to the target Resource Group located inside the target tenant. You will then click the Paste button to paste the disk into the new target Resource Group.


Once pasted, you will be prompted to provide settings information for the pasted VM disk. Fill out the:

  • Disk name
  • Region
  • Availability zone
  • Account type

The Activities panel at the bottom can be used to track the events within the Storage Explorer. When the copy and paste is complete, the new disk will appear in the target location.


5. Create the new VM

The final step is to create the new VM out of the VM disk(s) that you copied to your new tenant. To do so, log into your Azure portal wit the account that is associated with your target tenant.

Next, Search for Disks and select the disk you copied over. In this example, because the VM had an OS disk and a data disk, we are first selecting the 30GB OS disk, then clicking Create VM to ensure that the new VM uses that disk for the OS.


In the screenshot below, we have the option to attach the data disk of 256GB to the new VM when configuring the settings for the VM.


Once all VM settings have been entered you can select Review and Create to complete the creation of the new VM. Congratulations, you have now successfully migrated an Azure VM from one tenant to another.

Note: You will not get the option to create an admin account when creating the new VM if one has already been created before the migration. The existing admin account is stored in the disk and will be detected when the new VM is created after the migration.

Built on Azure. Built for Azure.

Book some time with a Remotely team member to chat about the only Azure native RMM.

No Comments Yet

Let us know what you think