1.
Physical hardware

2.
Consistent
Management
Layer
AZURE RESOURCE MANAGER API

3.
Azure Templates can:
• Repeated deployment and consistent
state.
• Simplify Orchestration
• Simplify Roll-back
• Provide unified management and
Update Support.
Azure Templates are:
• Source file, checked-in
• Able to specify resources and
dependencies (VMs, WebSites, DBs) and
connections (config, LB sets)
• Based on parametrized input/output
SQL - A Website
Virtual
Machines
SQL-A
Website
[SQL CONFIG] VM (2x)
DEPENDS ON SQLDEPENDS ON SQL
SQL CONFIG

4.
Simplest structure and elements:

5.
Note: Parameters are optional. However, without parameters, your template would
always deploy the same resources with the same names, locations, and properties.

6.
Size

7.
Example A value returned in the Outputs section.

8.
docs.microsoft.com/en-us/azure/templates/

9.
Qlikdeploy.json
Storage account
Landscape deploy
Common settings:
- Username
- PW
- ADJOINpw
- Location
- vnetID
- Subnetref
- Storage account
- Template URLs
- Images
- DNSname
Unique Parameters:
- - environment
(dev/test/prod)
(COPYINDEX)
- Qlikinfo (per env)
- Machine sizes
- PIP/LB/Avset name
- Start ID
landscapedeploy.jso
n
Load balancer
private
VM deploy
Common settings:
- Username
- PW
- ADJOINpw
- Location
- vnetID
- Subnetref
- Storage account
- Template URLs
- Images
- DNSname
Unique Parameters:
- Qlikinfo (per env)
(COPYINDEX)
- Vmname
- Lbid
- Lbbackend
- Avsetid
- Imageid
- storageaccountkey
VMdeploy.json
NIC
VM
AVSET
Load balancer
Common Settings
Unique settings
- Lbname
- Pipid
- Frontendipid
- Lbpoolid
- Lbprobeid
- subnetref
Load balancer
public
PIP (if PROD) Test/dev  private
Prod  public
Nprinting 
vmnoavsetlb
Central/proxy 
vmavsetlb

10.
1.
2.
3.
1.
2.
3.
4.
5.
6.

11.
Consistent
Management
Layer
AZURE RESOURCE MANAGER API