A frequently asked question about rolling out Azure VNet with different subnets in a infrastructure as code environment is where and how to define the subnets in your Azure ARM template. In the most examples online the number of subnets is configured in the template and the name and addressPrefix is configured in the parameter file. The big disadvantage with this scenario is that when you deploy a VNet with for example two subnets and later you decide to add more subnets you have two choices both of which are uncomfortable for an Infrastructure as code release pipeline. Continue reading “Infrastructure as Code – Deploy Azure VNet with dynamic subnets”
At the moment of writing this blog it’s unfortunately not possible to move an Azure VM with Managed disk to another Resource Group or to another Description. However, Microsoft says on the Azure Portal that this will be possible in the near feature. For the time being, I have chosen to write a small PowerShell script that will do the move fully automated for you. At the moment the only way to move an Azure VM with Managed Disk to another resource group is redeploying the VM. To achieve this you need to perform the following steps (some from the portal and some from PowerShell) manually:
- Shutdown VM
- Collect the required information like Networking, VM size, Storage etc.
- Create a Snapshot
- Create or use an existing Azure Storage Account to copy the Snapshot to
- Remove the VM
- Create a new Azure VM in the new Resource Group with the collected information and Snapshot disk from the Azure Blob
- The Azure VM will start automatically, check if the VM functions as it should and remove the Snapshot and Azure Storage Account.
As you can see there are about 7 steps needed to move an Azure VM with a Managed Disk. The script that I have written will do all the steps automatically with only 3 variables that you need to define while running the script. Continue reading “Move Azure VM with Managed Disk to another Resource Group”