This document discusses Azure Service Management (ASM) and Azure Resource Manager (ARM), two models for deploying infrastructure in Microsoft Azure. ASM was the original model but ARM is now preferred. ASM operates at the cloud service level using XML, while ARM uses JSON and groups resources into resource groups. While ASM is supported for existing resources, ARM supports new resource types and allows deployments to work in parallel. The document demonstrates deploying infrastructure with each model and discusses pros and cons of each approach. It recommends using ARM for new deployments while ASM can still be used for existing resources.

1. © Copyright SELA Software & Education Labs Ltd. | 14-18 Baruch Hirsch St Bnei Brak, 51202 Israel | www.selagroup.com
SELA DEVELOPER PRACTICE
JUNE 19-23, 2016
Ido Katz, Microsoft Azure MVP
Cloud Infrastructure Technical Lead
Sela Group
Azure Service Management Vs. Azure Resource Manager
Mail: idok@sela.co.il
Blog: blogs.microsoft.co.il/idokatz
Twitter: @send2katz

2. Agenda
What is Cloud?
Azure Service Management
Demo – ASM – IaaS Deployment Process
Azure Resource Manager
Demo – ARM – IaaS Deployment Process
Pros – ASM & ARM
Cons – ASM & ARM
Why should I use them both?
Questions

3. What is Cloud?

4. Azure Service Management
Azure Service Management (A.K.A ASM/V1/Classic) was there
from the beginning of Azure but he started as an API for PaaS
Services as Azure started as PaaS Services
ASM operations are based on the Cloud Service
ASM is based on XML Scheme
You can use ASM for the old portal and the new portal as well

5. Demo
ASM – IaaS Deployment Process

6. Azure Resource Manager
Azure Resource Manager was announced 2 Years ago
The objective of the ARM is to remove dependencies of the
cloud service operations.
Each component will be located under Resource Group.
ARM is based on JSON Scheme.
Resource Group can be exported and than you can the JSON file
and deployment file.

7. Demo
ARM – IaaS Deployment Process

8. Why should I use them both?
ASM-
supported by most existing Azure resources
customer already invested in the ASM deployment
New resources added to Azure will not support this model (Azure Active Directory, Media
Services and a lot of Marketplace Solutions such as Kemp, Couch Base, etc.)
ARM-
Most of the resources already supported
New Customer should use ARM as the default deployment
There are some resources that available only on this model (Scale Sets, Cool Storage, RBAC, etc.)

9. Pros – ASM & ARM
ARMASM
Work in ParallelVisualization
JSON BasedEasy to navigate
New Features!!!Well Known Structure

10. Cons – ASM & ARM
ARMASM
Hard to navigateDependencies
There are components that aren’t
supported yet
XML Based
Can’t Communicate with ASMComponents unavailable
A whole different structureCannot communicate with ARM

11. Things you should know
ASM Resources cannot communicate with ARM Resources
ASM was based on cloud service operations and because cloud service cannot do two
operations in a time you couldn’t work in parallel.(For example you couldn’t deploy two
VM’s under the same cloud service)
ASM & ARM got two different API’s so if you're using PS there are commands for ASM
(for example: Get-AzureVM) and for ARM (for example: Get-AzureRMvm)
If you starting using Azure today start working with the ARM right away.
There is no migration tool for moving from ASM to ARM – you can use PowerShell script
to automate it.
There is a community GitHub repository by Microsoft which got a lot of JSON deployment
file that you can use and customize it to your own environment.

12. Questions