1. Home
  2. Training Library
  3. Microsoft Azure
  4. Courses
  5. Introduction to Azure Resource Manager

Introduction to Azure Resource Manager

The course is part of these learning paths

AZ-103 Exam Preparation: Microsoft Azure Administrator
course-steps 15 certification 6 lab-steps 8
AZ-203 Exam Preparation: Developing Solutions for Microsoft Azure
course-steps 20 certification 1 lab-steps 7
Architecting Microsoft Azure Solutions
course-steps 10 certification 6 lab-steps 5
Developing, Implementing and Managing Azure Infrastructure
course-steps 10 certification 7 lab-steps 2
more_horiz See 3 more
Introduction to Azure Resource Manager
Duration1h 30m
star star star star star-half


This course will introduce the Microsoft Azure Resource Manager (ARM) REST API, and how to interact with it using the Azure Cross-Platform (xPlat) CLI Tool and the ARM PowerShell module. The ARM interface is a web service that provides two primary mechanisms for managing cloud resources:

Microsoft's ARM interface offers several different methods of accessing it:

Key Takeaways

After participating in this course, you'll be enabled with the following information:

  • The architecture of the Microsoft Azure Resource Manager (ARM) interface
  • installing and getting started with the ARM PowerShell module
  • Installing and getting started with the Azure Cross-Platform (xPlat) CLI Tool
  • How to build and understand Azure Resource Manager JSON Templates
  • Common software tools you'll encounter, surrounding Azure Resource Manager
  • Declarative provisioning and imperative provisioning of cloud resources in Azure

If you have thoughts or suggestions for this course, please contact Cloud Academy at support@cloudacademy.com.

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.

Hi, my name is Trevor Sullivan, a Microsoft MVP for Windows PowerShell.

Welcome to Microsoft Azure Resource Manager, provisioning. In this lecture, we're going to talk about provisioning in the past, declarative provisioning and the new provisioning workflow with the Azure Resource Manager API. So let's start off by taking a look at the traditional method of provisioning. The traditional method of provisioning looked like opening the Azure portal, clicking the "New" button, selecting a type of resource such as a storage account or a virtual machine or virtual network. Filing out the details for that item such as a name or type and then finally clicking the "Confirm" button so that the Azure platform would go out and provision that resource. We can also use the Azure PowerShell module to automate these tasks from a PowerShell script. Let's take a look at provisioning the new way. If you're a software developer or IT professional, you can declare your infrastructure inside of a code file, which is made up of JSON objects or a JavaScript object notation. The desire is to deploy this declarative infrastructure out to your Azure subscription. However, you can first put that file into source control. Once that file is inside of your source control, you can perform a deployment to your Azure subscription inside of what's called a resource group. A couple of different source control options you have are Visual Studio team services, formally known as Visual Studio Online, as well as the popular GitHub service which Microsoft and many other vendors have adopted. So now, let's take a look at the new provisioning process using the Azure Resource Manager API.

First, you'll author your JSON file that contains a declarative infrastructure for your cloud subscription. You'll commit that file to source control every time that you make a change. You'll deploy that JSON file to your Azure dev environment.

Then once you've confirmed the functionality in dev, you can deploy to the QA environment. Once QA and test has signed off on that infrastructure configuration the operations team can then deploy that same infrastructure to the production environment.