Considerations for Converting Virtual Machines to Azure

Review the following considerations before you restore an Hyper-V virtual machine to an Azure virtual machine in the Azure management portal:

SnapProtect Considerations

  • Conversion of virtual machines to Azure is not supported from SnapProtect snap copies, but is supported from SnapProtect backup copies.

  • Converting VHDX formatted 4K sectored disks to Azure is not supported.

  • If the AUTO option is selected and the disk operating system type cannot be determined from the configuration file, the job will fail. You can resubmit the job by selecting the proper operating system in the Restore Options for All Selected Items dialog box.

  • The Create and Power ON Virtual Machine option is selected by default. If this option is not selected when the VM is restored, only the operating system disk is registered, and any remaining disks are uploaded to the Azure storage account. In this case, you must recreate the VHDs manually through the Azure management portal by using the Create VHD option on the Disk tab:

    1. For each disk, browse to the storage location and open the disk from which the VHD is to be created. Opening the disk registers it as a VHD so that it can be attached to a new or existing VM.
    2. Select the VM to which the VHD is to be attached, and attach one or more registered VHDs from the storage location.

Azure VM Considerations

  • Hyper-V generation 2 virtual machines cannot be converted to Azure.
  • The VM name can contain only alphanumeric characters or the hyphen ('-' ) character; the name cannot contain any Unicode Transformation Format (UTF) characters.
  • The RAM and disk specification for the source VM must match the format of the Azure destination VM. For example, if the source VM RAM is less than 1.75 GB and AUTO is selected as the VM size for the conversion, only two disks will be uploaded, because of Azure restrictions.
  • Virtual machines with a VM size of A8 or A9 can  be created only in new Azure cloud services without any instances. You cannot create A8 or A9 VMs in existing cloud services.

After you understand the behaviors and limitations that are associated with the conversion to Azure, you can begin your conversion of Hyper-V VMs. For detailed instructions on converting the VMs to Azure, see Converting Hyper-V Virtual Machines to Azure.