Why ARM template parameters and variables in Azure? - Purpose & Use Cases

The Big Idea

What if you could change your entire cloud setup by updating just one place?

The Scenario

Imagine you need to create many cloud resources by writing the same settings over and over in a big file. Every time you want to change a value, you must find and update it everywhere manually.

The Problem

This manual way is slow and risky. You might miss some places or make typos. It's hard to keep track of what values you used, and updating the setup becomes a headache.

The Solution

Using ARM template parameters and variables lets you write values once and reuse them everywhere. Parameters let you customize your setup when you deploy, and variables store values inside the template to avoid repetition.

Before vs After

✗ Before

{ "resources": [{ "name": "myVM", "location": "eastus", "size": "Standard_DS1_v2" }, { "name": "myDB", "location": "eastus", "sku": "Basic" }] }

✓ After

{ "parameters": { "location": { "type": "string" } }, "variables": { "vmSize": "Standard_DS1_v2" }, "resources": [{ "name": "myVM", "location": "[parameters('location')]", "size": "[variables('vmSize')]" }, { "name": "myDB", "location": "[parameters('location')]", "sku": "Basic" }] }

What It Enables

You can easily customize and manage your cloud setup with fewer mistakes and faster updates.

Real Life Example

A company deploys the same app in different regions. Using parameters, they just change the region value at deployment without rewriting the whole template.

Key Takeaways

Manual repetition causes errors and slow updates.

Parameters let you input values when deploying.

Variables store reusable values inside the template.

Practice

1.

What is the main purpose of parameters in an ARM template?

easy

A. To define the resources to deploy

B. To allow input values when deploying the template

C. To store fixed values inside the template

D. To specify deployment location only

Solution

1. Step 1: Understand parameters role

   Parameters let users provide input values at deployment time, making templates flexible.

2. Step 2: Differentiate from variables

   Variables store fixed or computed values inside the template, not input values.

3. Final Answer:

   To allow input values when deploying the template -> Option B

4. Quick Check:

   Parameters = input values [OK]

Hint: Parameters accept inputs during deployment, variables do not [OK]

Common Mistakes:

• Confusing parameters with variables
• Thinking parameters define resources
• Assuming parameters are fixed values

2.

Which of the following is the correct syntax to declare a variable named storageAccountName in an ARM template?

{
  "variables": {
    "storageAccountName": "myStorage"
  }
}

easy

A. "resources": { "storageAccountName": "myStorage" }

B. "parameters": { "storageAccountName": "myStorage" }

C. "variables": { "storageAccountName": "myStorage" }

D. "outputs": { "storageAccountName": "myStorage" }

Solution

1. Step 1: Identify variable declaration section

   Variables are declared inside the "variables" section as key-value pairs.

2. Step 2: Match syntax with example

   The example shows "variables": { "storageAccountName": "myStorage" }, which matches "variables": { "storageAccountName": "myStorage" }.

3. Final Answer:

   "variables": { "storageAccountName": "myStorage" } -> Option C

4. Quick Check:

   Variables declared under "variables" [OK]

Hint: Variables go inside "variables" block, not parameters or resources [OK]

Common Mistakes:

• Putting variables inside parameters
• Confusing variables with outputs
• Using wrong JSON section names

3.

Given this ARM template snippet, what will be the value of variables('fullName')?

{
  "parameters": {
    "firstName": { "type": "string", "defaultValue": "John" },
    "lastName": { "type": "string", "defaultValue": "Doe" }
  },
  "variables": {
    "fullName": "[concat(parameters('firstName'), ' ', parameters('lastName'))]"
  }
}

medium

A. parameters('firstName') parameters('lastName')

B. JohnDoe

C. [concat(parameters('firstName'), ' ', parameters('lastName'))]

D. John Doe

Solution

1. Step 1: Understand concat function in variables

   The variable "fullName" uses concat to join firstName, a space, and lastName.

2. Step 2: Substitute default parameter values

   firstName = "John", lastName = "Doe", so concat("John", " ", "Doe") = "John Doe".

3. Final Answer:

   John Doe -> Option D

4. Quick Check:

   concat with space joins names [OK]

Hint: concat joins strings; default parameters fill in values [OK]

Common Mistakes:

• Taking concat as literal string
• Ignoring space between names
• Confusing parameters with variables

4.

Identify the error in this ARM template snippet:

{
  "parameters": {
    "location": { "type": "string" }
  },
  "variables": {
    "region": "parameters('location')"
  }
}

medium

A. Missing square brackets around the parameter reference in variable

B. Variable names cannot be 'region'

C. Parameter type must be 'securestring' to use in variables

D. Variables cannot reference parameters

Solution

1. Step 1: Check variable referencing syntax

   Variables referencing parameters must use expression syntax with square brackets: "[parameters('location')]".

2. Step 2: Identify missing brackets

   The variable "region" is assigned "parameters('location')" as a string, not an expression.

3. Final Answer:

   Missing square brackets around the parameter reference in variable -> Option A

4. Quick Check:

   Parameter references need [ ] in variables [OK]

Hint: Use [parameters('name')] inside variables, not plain strings [OK]

Common Mistakes:

• Omitting square brackets for expressions
• Thinking variables can't use parameters
• Wrong parameter types for variables

5.

You want to create an ARM template that deploys a storage account with a name based on a parameter prefix and a variable uniqueString. Which is the best way to combine them in the template?

{
  "parameters": {
    "prefix": { "type": "string" }
  },
  "variables": {
    "uniqueString": "[uniqueString(resourceGroup().id)]"
  },
  "resources": [
    {
      "type": "Microsoft.Storage/storageAccounts",
      "name": "???",
      "apiVersion": "2022-09-01",
      "location": "[resourceGroup().location]"
    }
  ]
}

Choose the correct expression to use for the storage account name property.

hard

A. "[concat(parameters('prefix'), variables('uniqueString'))]"

B. "parameters('prefix') + variables('uniqueString')"

C. "[parameters('prefix') variables('uniqueString')]"

D. "concat(parameters.prefix, variables.uniqueString)"

Solution

1. Step 1: Understand ARM template expression syntax

   Expressions must be inside square brackets and use functions like concat() to join strings.

2. Step 2: Check correct usage of parameters and variables

   Use parameters('name') and variables('name') inside concat() within brackets.

3. Step 3: Evaluate options

   "[concat(parameters('prefix'), variables('uniqueString'))]" uses correct syntax: "[concat(parameters('prefix'), variables('uniqueString'))]".

4. Final Answer:

   "[concat(parameters('prefix'), variables('uniqueString'))]" -> Option A

5. Quick Check:

   Use [concat(parameters('x'), variables('y'))] for combined names [OK]

Hint: Use [concat(parameters('x'), variables('y'))] for combined strings [OK]

Common Mistakes:

• Using + instead of concat inside brackets
• Omitting square brackets for expressions
• Wrong syntax for parameters or variables