Skip to content

Latest commit

 

History

History
14 lines (7 loc) · 1.42 KB

virtual-machines-common-convert-disks-considerations.md

File metadata and controls

14 lines (7 loc) · 1.42 KB

  • The conversion requires a restart of the VM, so schedule the migration of your VMs during a pre-existing maintenance window.

  • The conversion is not reversible.

  • Be aware that any users with the Virtual Machine Contributor role will not be able to change the VM size (as they could pre-conversion). This is because VMs with managed disks require the user to have the Microsoft.Compute/disks/write permission on the OS disks.

  • Be sure to test the conversion. Migrate a test virtual machine before you perform the migration in production.

  • During the conversion, you deallocate the VM. The VM receives a new IP address when it is started after the conversion. If needed, you can assign a static IP address to the VM.

  • The original VHDs and the storage account used by the VM before conversion are not deleted. They continue to incur charges. To avoid being billed for these artifacts, delete the original VHD blobs after you verify that the conversion is complete.

  • Review the minimum version of the Azure VM agent required to support the conversion process. For information on how to check and update your agent version, see Minimum version support for VM agents in Azure