Azure have two deployment models for deploying and managing the azure services:
- Resource Manager (ARM – Azure Resource Manager)
- Classic (ASM – Azure Service Manager)
Azure Service Manager:
- The configuration files work based on XML files.
- Azure services are limited and features are limited to certain extent.
- Cannot manage the ARM resources.
- Cannot able to group resources when there are multiple virtual machines are running on the same subscription. [In case, if there are multiple projects/clients]
- Resource management is not possible as the service administrator/co-administrator will have full access to the resources.
- Portal: https://manage.windowsazure.com
Azure Resource Manager:
- The configuration files work based on JSON files.
- Azure Services are endless and lot of featured available for a service.
- Can manage the ASM resources. [The resource type includes (classic) in the name]
- Can able to group resources when there are multiple virtual machines are running on the same subscription. [In case, if there are multiple projects/clients]
- Resource management is easy with RBAC (Role Based Access Control). In this, it is possible to define the different roles to the different services.
- Portal: https://portal.azure.com
- It is not possible to use Azure Resource Manager to deploy a virtual machine into a virtual network that was created using classic deployment.
- It is not possible to create a virtual machine using the Azure Resource Manager from a user image that was created using the Azure Service Management.