Azure Resource Manager

In the last step of our previous activity, we discussed Microsoft Container Service. In this activity, we will be covering an introduction to Azure Resource Manager (ARM) and the templates available to it, as well as Desired State Configurations (DSC).

Microsoft Azure Resource Manager lets you deploy, update or delete resources for your cloud solution in a single, coordinated operation. Resources can include virtual machines, storage accounts, virtual networks, services or any component that you are managing. 

Why use Azure Resource Manager?

• You can deploy, manage, and monitor all of the resources for your solution as a group, known as a resource group, rather than handle these resources individually.
• You can repeatedly deploy your solution throughout the development lifecycle and have confidence that your resources are deployed in a consistent state.
• You can use declarative templates to define your deployment.
• You can define the dependencies between resources so that they are deployed in the correct order.
• You can apply access control to all services in your resource group because Role-Based Access Control (RBAC) is integrated natively into the management platform.
• You can apply tags to resources to logically organise all of the resources in your subscription.
• You can clarify billing for your organisation by viewing the rolled-up costs for the entire group or for a group of resources sharing the same tag.

Note: The Azure Resource Manager deployment model contains important differences from the classic deployment model, and the two models are not completely compatible with each other. To simplify the deployment and management of resources, Microsoft recommends that you use the Resource Manager for new resources