I went with the platform supported method. Long-term, it means I have more work to do to do some renaming, etc, but I\u2019ve never had \u201cmy own\u201d stuff to move using this method, so I wanted to do it and document it with a real example.<\/p>\n
Note that the platform support method<\/a> has a few approaches. My virtual machine was in a virtual network, so I opted to move the entire virtual network and associated contents. This is cool because, all VMs (I have one only) are moved, and endpoints are converted into NAT rules in a load balancer. Any reserved cloud service IPs are converted into static public IPs.<\/p>\n Note, you\u2019ll need to download the latest Azure PowerShell modules<\/a> (and reboot if it\u2019s your first install) to do either method.<\/em><\/p>\n FYI, the below includes copy\/pastes of the actual cmdlets that I used. The only thing I have modified, for obvious reasons, is the subscription ID.<\/p>\n You\u2019ll need to register the provider that allows you to do ASM-ARM migrations. This is done on a per subscription basis. You\u2019ll log into your subscription using ARM:<\/p>\n If your tenant has more than one subscription, like mine does, then you need to query the subscriptions:<\/p>\n This allows you to get the ID of the subscription that you will sign into, so you can select it as the current subscription to work on:<\/p>\n Next you register the migration proivder:<\/p>\n This migration can take up to five minutes. You can query the status of the migration:<\/p>\n You can continue once you get a registered status:<\/p>\n ProviderNamespace : Microsoft.ClassicInfrastructureMigrate<\/p>\n RegistrationState : Registered<\/p>\n ResourceTypes : {classicInfrastructureResources}<\/p>\n Locations : {East Asia, Southeast Asia, East US, East US 2…}<\/p><\/blockquote>\n The migration has three phases. The first allows you to validate that you can migrate your machines cleanly. Common issues include unsupported extensions, extension versions, classic backup vault registrations, endpoint ACLs, etc.<\/p>\n To do the validation, you need to sign in using ASM:<\/p>\n Once again you need to make sure you\u2019re working with the right subscription:<\/p>\n And then make that subscription current:<\/p>\n I migrated my virtual network, so I queried for the Azure name of the virtual network.<\/p>\n My virtual network was called aidanfinn02 so I saved that as a variable \u2013 it\u2019ll be used a few times.<\/p>\n Then I ran the validation against the virtual network, saving the results in a variable called $validate:<\/p>\n I could then see the results:<\/p>\n There were two issues:<\/p>\n ResourceType : VirtualNetwork<\/p>\n ResourceName : aidanfinn02<\/p>\n Category : Error<\/p>\n Message : Virtual Network aidanfinn02 has encountered validation failures, and hence it is not supported for migration.<\/p>\n VirtualMachineName :<\/p>\n ResourceType : Deployment<\/p>\n ResourceName : aidanfinn02<\/p>\n Category : Error<\/p>\n Message : Deployment aidanfinn02 in Cloud Service aidanfinn02 has encountered validation failures, and hence it is not supported for migration.<\/p>\n VirtualMachineName :<\/p>\n ResourceType : Deployment<\/p>\n ResourceName : aidanfinn02<\/p>\n Category : Error<\/p>\n Message : VM aidanfinn02 in HostedService aidanfinn02 contains Extension MicrosoftMonitoringAgent reporting Status : Error. Hence, the VM cannot be migrated. Please ensure that<\/p>\n the Extension status being reported is Success or uninstall it from the VM and retry migration.,Additional Details: Message=This machine is already connected to another<\/p>\n Log Analytics workspace, please set stopOnMultipleConnections to false in public settings or remove this property, so this machine can connect to new workspaces, also<\/p>\n it means this machine will get billed multiple times for each workspace it report to. (MMAEXTENSION_ERROR_MULTIPLECONNECTIONS) Code=400<\/p>\n VirtualMachineName : aidanfinn02<\/p>\n ResourceType : Deployment<\/p>\n ResourceName : aidanfinn02<\/p>\n Category : Error<\/p>\n Message : VM aidanfinn02 in HostedService aidanfinn02 contains Extension MicrosoftMonitoringAgent reporting Handler Status : Unresponsive. Hence, the VM cannot be migrated.<\/p>\n Please ensure that the Extension handler status being reported is Ready or uninstall it from the VM and retry migration.,Additional Details: Message=Handler<\/p>\n Microsoft.EnterpriseCloud.Monitoring.MicrosoftMonitoringAgent of version 1.0.11049.5 is unresponsive Code=0<\/p>\n VirtualMachineName : aidanfinn02<\/p>\n ResourceType : Deployment<\/p>\n ResourceName : aidanfinn02<\/p>\n Category : Error<\/p>\n Message : VM aidanfinn02 in HostedService aidanfinn02 is currently configured with the Azure Backup service and therefore currently not supported for Migration. To migrate this<\/p>\n VM, please follow the procedure described athttps:\/\/aka.ms\/vmbackupmigration.<\/p>\n VirtualMachineName : aidanfinn02<\/p><\/blockquote>\n The solutions to these problems were easy:<\/p>\n I re-ran the validation:<\/p>\n And the result was that the virtual network (and thus the VM) was ready for an ARM migration.<\/p>\n ResourceType : VirtualNetwork<\/p>\n ResourceName : aidanfinn02<\/p>\n Category : Information<\/p>\n Message : Virtual Network aidanfinn02 is eligible for migration.<\/p>\n VirtualMachineName :<\/p>\n ResourceType : Deployment<\/p>\n ResourceName : aidanfinn02<\/p>\n Category : Information<\/p>\n Message : Deployment aidanfinn02 in Cloud Service aidanfinn02 is eligible for migration.<\/p>\n VirtualMachineName :<\/p>\n ResourceType : Deployment<\/p>\n ResourceName : aidanfinn02<\/p>\n Category : Information<\/p>\n Message : VM aidanfinn02 in Deployment aidanfinn02 within Cloud Service aidanfinn02 is eligible for migration.<\/p>\n VirtualMachineName : aidanfinn02<\/p><\/blockquote>\n The preparation phase is next. This is an interim or trial period where you introduce the ARM API to your resources. For a time, the resources are visible to both ARM and ASM. There is no downtime, but you cannot make any configuration changes. The reasoning for this is that you can validate that everything is still working.<\/p>\n You run the command, as I did against the virtual network.<\/p>\n And then you wait \u2026 try not to grind your teeth or chew your gums:<\/p>\n OperationDescription OperationId OperationStatus<\/p>\n ——————– ———– —————<\/p>\n Move-AzureVirtualNetwork 2bcb56ce-2330-0824-a376-a3dcc4892e3d Succeeded<\/p><\/blockquote>\n Once preparation is done, double-check everything. My website was still responding, and resources appeared in two different resource groups with -Migrated suffixes \u2013 I\u2019ll show you how I tidied that up later in the post. I was ready to commit; this is when you tell Azure that all is good, and to please remove the ASM APIs from the resources.<\/p>\n More time passes when you forget to breath, and then it\u2019s done! You\u2019re in ARM, and your resources are manageable once again. Note that there is an alternative to Commit, which is to abort the process and roll back to ASM-only management.<\/p>\n My ASM deployment was quite basic, and not best practice. I created a network security group for the subnet, allowing in:<\/p>\n As I mentioned, my ASM resources migrated into two resource groups as ARM resources. I wanted to:<\/p>\n You can move resources, but you cannot rename resource groups. So I created a third resource group (aidanfinn):<\/p>\n Then I moved the resources from both of the migrated resource groups into the new aidanfinn resource group:<\/p>\n The official method for migrating storage is to migrate the storage account. That means that you move the storage account with the VHDs within it. Azure offers a new method for handling storage called managed disks:<\/p>\n I decided to take a different route \u2013 I would convert my ARM VM from un-managed disks to managed disks. I needed a few values:<\/p>\n I stopped the VM (my first piece of downtime in this entire process):<\/p>\n Then I did the conversion:<\/p>\n And then I restarted the VM, after just a few minutes of downtime:<\/p>\n I like the management features of Azure, so I re-introduced:<\/p>\n Lots of stuff can get left behind, especially if you\u2019ve been trying things out. That all needs to be removed. One thing I kept around for a while was the classic backup vault, just in case. I only unregistered the old ASM VM \u2013 I did not delete the data. That means I have a way back if all goes wrong in ARM or I screw up in some way. I\u2019ll give it a month, and then I\u2019ll remove the old vault.<\/p>\n By the way, you can upgrade a backup vault to ARM<\/a> (recovery services vault) if you want to keep your retention.<\/p>\n I ended up with everything in ARM and in one resource group:<\/p>\n I don\u2019t like the naming, so I will be cleaning things up. My next mini-project will be to:<\/p>\n I know \u2013\u00a0I could have done all that more quickly and easily using MigAz, but I wanted to do the platform supported migration on\u00a0my<\/em> stuff, and it was a chance to document it too! Hopefully this will be useful for you.<\/p>\n","protected":false},"excerpt":{"rendered":" In this post, I will explain how I upgraded the Azure virtual machine, that this site is hosted on, from ASM (Azure Service Management, Classic or Azure v1) to ARM (Azure Resource Manager, Resource Manager or Azure v2). FYI, although I had no plans for changing subscriptions, this migration is also the first step for … Continue reading “How I Upgraded This VM To Azure Resource Manager”<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":20394,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"_uf_show_specific_survey":0,"_uf_disable_surveys":false,"footnotes":""},"categories":[5],"tags":[161,162,170,148,164,163,87,165,153],"class_list":["post-20392","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-azure","tag-arm","tag-asm","tag-azure","tag-azure-backup","tag-managed-disks","tag-migration","tag-powershell","tag-storage-account","tag-virtual-machines"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\tRegister the Migration Provider<\/h2>\n
Login-AzureRmAccount<\/pre>\n
Get-AzureRmSubscription<\/pre>\n
Select-AzureRmSubscription -SubscriptionId 1234567f-a1b2-1234-1a2b-1234ab123456<\/pre>\n
Register-AzureRmResourceProvider -ProviderNamespace Microsoft.ClassicInfrastructureMigrate<\/pre>\n
Get-AzureRmResourceProvider -ProviderNamespace Microsoft.ClassicInfrastructureMigrate<\/pre>\n
Validation<\/h2>\n
Add-AzureAccount<\/pre>\n
Get-AzureSubscription<\/pre>\n
Select-AzureSubscription -SubscriptionId 1234567a-a1b2-1234-1a2b-1234ab123456<\/pre>\n
Get-AzureVnetSite | Select -Property Name<\/pre>\n
$vnetName = \u201caidanfinn02\u201d<\/pre>\n
$validate = Move-AzureVirtualNetwork -Validate -VirtualNetworkName $vnetName<\/pre>\n
$validate.ValidationMessages<\/pre>\n
\n
\n
$validate = Move-AzureVirtualNetwork -Validate -VirtualNetworkName $vnetName$validate.ValidationMessages<\/pre>\n
$validate.ValidationMessages<\/pre>\n
Preparation<\/h2>\n
Move-AzureVirtualNetwork -Prepare -VirtualNetworkName $vnetName<\/pre>\n
Commit<\/h2>\n
Move-AzureVirtualNetwork -Commit -VirtualNetworkName $vnetName<\/pre>\n
Network Security Group<\/h2>\n
\n
Resource Group Clean-up<\/h2>\n
\n
![\"image\"](\"https:\/\/aidanfinn.com\/wp-content\/uploads\/2017\/08\/image_thumb.png\" "\\"image\\"")
<\/a><\/p>\n![\"image\"](\"https:\/\/aidanfinn.com\/wp-content\/uploads\/2017\/08\/image_thumb1.png\" "\\"image\\"")
<\/a><\/p>\nMigrate Storage to ARM<\/h2>\n
\n
$rgName = \"aidanfinn\"\r\n$vmName = \"aidanfinn02\"<\/pre>\n
Stop-AzureRmVM -ResourceGroupName $rgName -Name $vmName -Force<\/pre>\n
ConvertTo-AzureRmVMManagedDisk -ResourceGroupName $rgName -VMName $vmName<\/pre>\n
Start-AzureRmVM -ResourceGroupName $rgName -Name $vmName<\/pre>\n
Re-Introduce Management<\/h2>\n
\n
Cleanup ASM<\/h2>\n
The End Result<\/h2>\n
![\"image\"](\"https:\/\/aidanfinn.com\/wp-content\/uploads\/2017\/08\/image_thumb2.png\" "\\"image\\"")
<\/a><\/p>\n\n