Azure's new Resource Manager provides a new way to deploy and manage your solutions. If you used the earlier Service Management model and want to learn about the changes, see Understanding Resource Manager deployment and classic deployment.
If you'd like to learn more about the benefits of the new Resource Manager, read the Azure Resource Manager overview.
Resource Handlers are available for both management systems within CloudBolt. They can co-exist, however virtual machines and networks managed under one model will not be visible or available under the other.
Many resource types will transition easily between the two management systems. The resource providers that differentiate between the two models are:
- Compute - For more details, read the MSDN article on Azure VM Resizing and SKU Change in ASM and ARM.
For these resource types, you must be aware of which version you are using because the supported operations will differ. If you are ready to migrate your resources to Resource Manager deployment, see Platform supported migration of IaaS resources from Classic to Azure Resource Manager.
Migrations can be performed a number of ways:
- Via the instructions provided by Microsoft via Migrate IaaS resources from classic to Azure Resource Manager by using Azure PowerShell
- Via the ASM2ARM PowerShell script module. More details are available here: https://phidiax.com/blog/post/azure-vm-migration-from-asm-to-arm-using-the-asm2arm-tool-multiple-vms-and-virtual-network
- Via AzCopy, which can be run from Powershell or CMD shell. More details are available here: https://www.phidiax.com/blog/post/azure-vm-migration-from-asm-to-arm-using-azcopy-and-powershell
We will update the documentation as support evolves for both management systems.