Introduction to Azure Resource Manager
Template Deployment & Advanced Concepts
The course is part of these learning pathsSee 3 more
This lecture introduces the Microsoft Azure Resource Manager (ARM) architecture. We will discuss key concepts including your Azure Subscription (account), ARM Resource Groups, Resources, Resource Providers, and briefly touch on a couple of features that enable you to manage access to your cloud resources: tags and Role-Based Access Control (RBAC).
Hello and welcome to Microsoft Azure Resource Manager, Resource Manager Architecture. In this lecture, we're going to cover the Resource Manager Architecture, moving Azure resources, and linking Azure resources.
Inside of Microsoft Azure, the top-level object you're going to generally deal with is called your Azure subscription or account. Inside of your Azure subscription, you can provision one or more resource groups. Cloud resources are provisioned inside of these resource groups and can be managed at the resource group level.
The Azure Resource Manager API contains what are called resource providers. The resource providers are what are responsible for provisioning resource instances into your resource groups. There's many different resource providers available and several of them are listed here, such as Compute, Network, Storage, SQL DB, Cache and many others. Resource groups and individual resources have a couple of features that are generic.
First of all, you can apply role-based access control (RBAC) rules to both the resource group level, as well as the resources themselves. Role-based access control enables administrators to restrict what operations a user or group can perform at the resource group or individual resource layer. Resource groups and individual resources also support what are called tags. Tags are simple key-value pairs, like a dictionary, that enable the user to specify custom metadata that define the purpose of that resource. Once those tags have been defined, an administrator can go into their subscription and filter the resources for a list of resources that match a particular tag.
Inside of your Azure subscription, you may have more than one resource group. One resource group may contain resources that you would like to administratively move to a different resource group. So using the Azure Resource Manager API, we can take certain types of resources and move them from one resource group to another.
In some cases, you'll be managing multiple Azure subscriptions. Certain types of resources allow you to move then from one resource group in a subscription to a different resource group in a different subscription. The ability to do this moving process really depends on the type of Azure resource as only certain resources support the operations of moving between resource groups in the same subscription and resource groups that cross the subscription boundary.
You can also link Azure resources together. So inside of an Azure subscription, again you might have one or more resource groups. One resource group may contain several resources that make up a single application. So what you can do is create links between those resources.
You can also create resource links between resource groups. So if you have an application that spans more than one resource group, you can link all of those resources together. Each resource in Microsoft Azure Resource Manager can be linked to up to 50 other resources.
About the Author
Trevor Sullivan is a Microsoft MVP for Windows PowerShell, and enjoys working with cloud and automation technologies. As a strong, vocal veteran of the Microsoft-centric IT field since 2004, Trevor has developed open source projects, provided significant amounts of product feedback, authored a large variety of training resources, and presented at IT functions including worldwide user groups and conferences.