ARM template parameters and variables in Azure - Step-by-Step Execution

Process Flow - ARM template parameters and variables

Start ARM Template

↓

Define Parameters

↓

Define Variables

↓

Use Parameters & Variables in Resources

↓

Deploy Template with Parameter Values

↓

Resources Created Using Values

↓

End Deployment

The ARM template starts by defining parameters and variables, then uses them to configure resources during deployment.

Execution Sample

Azure

{
  "parameters": {
    "storageAccountName": { "type": "string" }
  },
  "variables": {
    "location": "eastus"
  }
}

Defines a parameter for storage account name and a variable for location.

Process Table

Step	Action	Parameters State	Variables State	Resource Property Value
1	Start template processing	storageAccountName: undefined	location: undefined	N/A
2	Define parameter 'storageAccountName'	storageAccountName: string (no value yet)	location: undefined	N/A
3	Define variable 'location'	storageAccountName: string (no value yet)	location: 'eastus'	N/A
4	Receive deployment parameter value	storageAccountName: 'mystorage123'	location: 'eastus'	N/A
5	Use parameter and variable in resource	storageAccountName: 'mystorage123'	location: 'eastus'	storageAccountName: 'mystorage123', location: 'eastus'
6	Deploy resource with these values	storageAccountName: 'mystorage123'	location: 'eastus'	Resource created with name 'mystorage123' in 'eastus'
7	End deployment	storageAccountName: 'mystorage123'	location: 'eastus'	Deployment complete

💡 Deployment ends after resources are created using parameter and variable values.

Status Tracker

Variable	Start	After Step 3	After Step 4	Final
storageAccountName	undefined	string (no value yet)	'mystorage123'	'mystorage123'
location	undefined	'eastus'	'eastus'	'eastus'

Key Moments - 3 Insights

Why is the parameter 'storageAccountName' undefined at first?

Parameters are placeholders until deployment time when actual values are provided, as shown in step 4 of the execution_table.

Can variables use parameter values in their definitions?

Yes, variables can reference parameters to compute values before deployment, but in this example, 'location' is a fixed string (step 3).

Why do resources use both parameters and variables?

Parameters allow input customization at deployment, variables simplify reuse and calculations, both combine to configure resources (step 5).

Visual Quiz - 3 Questions

Look at the execution_table, what is the value of 'storageAccountName' at step 2?

A undefined

B string (no value yet)

C 'mystorage123'

D 'eastus'

💡 Hint

Check the 'Parameters State' column at step 2 in the execution_table.

At which step does the deployment receive the actual parameter value?

A Step 4

B Step 3

C Step 5

D Step 6

💡 Hint

Look for when 'storageAccountName' changes from no value to 'mystorage123' in the execution_table.

If the variable 'location' was changed to 'westus', what would change in the execution_table?

A The resource name would change to 'westus'

B The parameter value would change to 'westus'

C The 'Variables State' column would show 'westus' instead of 'eastus' from step 3 onward

D No change would occur

💡 Hint

Variables track their values in the 'Variables State' column in the execution_table.

Concept Snapshot

ARM templates use parameters to accept input values at deployment time.
Variables hold fixed or computed values inside the template.
Parameters are undefined until deployment; variables are defined in the template.
Resources use both to configure properties dynamically.
Parameters enable reuse; variables simplify complex expressions.

Full Transcript

This visual execution shows how ARM templates define parameters and variables. Initially, parameters like 'storageAccountName' are placeholders without values. Variables like 'location' are set inside the template. When deploying, the parameter receives a real value, here 'mystorage123'. Resources then use these values to create cloud resources, such as a storage account named 'mystorage123' in the 'eastus' location. Variables remain constant unless changed in the template. This flow helps customize deployments while keeping templates reusable and clear.