All additional steps can be done via Power Shell. Step Zero again: use the Azure Portal to create a new blob container within a Storage Account in the destination region (used in $DestStorageAccountName and $DestStorageContainerName). Copy the Snapshots to a Destination Region-based Storage Account Make sure you select „Account type: Premium (SSD)“ if you use Managed Disks / Premium Storage. The VM may remain online during this process, but some applications might require the VM to be turned off. …everyīyte counts when copying between zones! So if you plan to copy to a different zone (visit for details) this might cost some coins per GB.Īfter the cleanup, creating snapshots is a simple trick: from the Azure Portal select the source VM, select „Disks“, select one of the disks and click „+ Create Snapshot“, and do this for every disk – name them „Snapshot-“, for example: „Snapshot-myVM1-OS“ for the System Disk and „Snapshot-myVM1-Data1“ for the first Data Disk. Step Zero: perform a cleanup and remove temporary files and folders, old backups etc.

Bonus: Copy a Network Security Group to the Destination Region.Convert the Disks to „Managed Disks“ (if required).Attach the Snapshots as Disks to the New VM.Create a New VM within the New Resource Group.Add a New Virtual Network in the Destination Region.Copy the Snapshots to a Destination Region-based Storage Account Container.The whole process consists of only a few steps (use this as a checklist): One might think this is a big thing (which might become even bigger if the source VM uses „Managed Disks“), but in fact it is just a „Copypaste“ – if you know how to do it. For various reasons, it might be useful to move or copy an Azure VM to a different region within Microsoft Azure.

Azure take snapshot of vm