Azure Resource Manager (ARM) concept - Mini Project: Build & Apply

Azure Resource Manager (ARM) Concept

📖 Scenario: You are working as a cloud engineer for a small company. Your task is to create a simple Azure Resource Manager (ARM) template to deploy a storage account. This template will help automate the deployment and management of cloud resources in a consistent way.

🎯 Goal: Build a basic ARM template that defines a storage account resource with essential properties. This template will be reusable and can be deployed multiple times to create the storage account in Azure.

📋 What You'll Learn

Create an ARM template with the correct JSON structure

Define the storage account resource with required properties

Use parameters to allow customization of the storage account name

Include the API version and resource type for the storage account

Set the location property to a parameter value

💡 Why This Matters

🌍 Real World

ARM templates are used to automate and standardize cloud resource deployments in Azure, saving time and reducing errors.

💼 Career

Understanding ARM templates is essential for cloud engineers and architects to manage Azure infrastructure efficiently.

1

Create the ARM template skeleton

Create a JSON object called template with the top-level keys: $schema, contentVersion, parameters, and resources. Set $schema to "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#" and contentVersion to "1.0.0.0". Initialize parameters and resources as empty objects or arrays as appropriate.

Azure

{
  "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
  "contentVersion": "1.0.0.0",
  "parameters": {},
  "resources": []
  # Your code here
}

Hint

Start by defining the basic structure of an ARM template with the required keys.

2

Add a parameter for the storage account name

Inside the parameters object, add a parameter called storageAccountName. Set its type to string and add a metadata object with a description that says "Name of the storage account".

Azure

{
  "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
  "contentVersion": "1.0.0.0",
  "parameters": {
    "storageAccountName": {
      "type": "string",
      "metadata": {
        "description": "Name of the storage account"
      }
    }
  },
  "resources": []
  # Your code here
}

Hint

Parameters allow users to customize the template when deploying.

3

Add the storage account resource

Inside the resources array, add an object representing a storage account resource. Set type to "Microsoft.Storage/storageAccounts", apiVersion to "2022-09-01", and name to reference the storageAccountName parameter using the expression "[parameters('storageAccountName')]". Set location to "eastus" and add a sku object with name set to "Standard_LRS". Add a kind property set to "StorageV2".

Azure

{
  "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
  "contentVersion": "1.0.0.0",
  "parameters": {
    "storageAccountName": {
      "type": "string",
      "metadata": {
        "description": "Name of the storage account"
      }
    }
  },
  "resources": [
    {
      "type": "Microsoft.Storage/storageAccounts",
      "apiVersion": "2022-09-01",
      "name": "[parameters('storageAccountName')]",
      "location": "eastus",
      "sku": {
        "name": "Standard_LRS"
      },
      "kind": "StorageV2"
    }
  ]
  # Your code here
}

Hint

Resources define what Azure services you want to deploy.

4

Add the location parameter and update the resource location

Add a new parameter called location inside the parameters object. Set its type to string and defaultValue to "eastus". Then update the location property of the storage account resource to use the expression "[parameters('location')]" instead of the fixed string "eastus".

Azure

{
  "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
  "contentVersion": "1.0.0.0",
  "parameters": {
    "storageAccountName": {
      "type": "string",
      "metadata": {
        "description": "Name of the storage account"
      }
    },
    "location": {
      "type": "string",
      "defaultValue": "eastus"
    }
  },
  "resources": [
    {
      "type": "Microsoft.Storage/storageAccounts",
      "apiVersion": "2022-09-01",
      "name": "[parameters('storageAccountName')]",
      "location": "[parameters('location')]",
      "sku": {
        "name": "Standard_LRS"
      },
      "kind": "StorageV2"
    }
  ]
  # Your code here
}

Hint

Using parameters for location makes the template flexible for different regions.

Practice

1. What is the main purpose of Azure Resource Manager (ARM)?

easy

A. To write code for mobile applications

B. To manage and organize cloud resources as a group

C. To monitor network traffic only

D. To create virtual machines manually

Solution

1. Step 1: Understand ARM's role

   ARM is designed to help manage cloud resources together, not individually.

2. Step 2: Compare options

   Options B, C, and D describe unrelated tasks, while A correctly describes ARM's purpose.

3. Final Answer:

   To manage and organize cloud resources as a group -> Option B

4. Quick Check:

   ARM manages resources as a group = A [OK]

Hint: ARM groups resources for easy management [OK]

Common Mistakes:

• Thinking ARM is only for virtual machines
• Confusing ARM with monitoring tools
• Assuming ARM writes application code

2. Which of the following is the correct way to deploy resources using ARM templates?

easy

A. Using FTP to upload ARM templates

B. Writing scripts in Python only

C. Using Azure Portal or Azure CLI with the ARM template

D. Manually creating resources without templates

Solution

1. Step 1: Identify deployment methods

   ARM templates are deployed via Azure Portal or Azure CLI commands.

2. Step 2: Eliminate incorrect options

   Python scripts and FTP are not standard deployment methods for ARM templates; manual creation ignores automation benefits.

3. Final Answer:

   Using Azure Portal or Azure CLI with the ARM template -> Option C

4. Quick Check:

   Deploy ARM templates via Portal or CLI = D [OK]

Hint: Deploy ARM templates via Portal or CLI commands [OK]

Common Mistakes:

• Thinking ARM templates deploy only with scripts
• Assuming manual creation is deployment
• Confusing FTP with deployment method

3. Given this ARM template snippet:

{
  "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
  "contentVersion": "1.0.0.0",
  "resources": [
    {
      "type": "Microsoft.Storage/storageAccounts",
      "apiVersion": "2021-04-01",
      "name": "mystorageaccount",
      "location": "eastus",
      "sku": { "name": "Standard_LRS" },
      "kind": "StorageV2"
    }
  ]
}

What resource will this template create when deployed?

medium

A. A storage account named mystorageaccount in East US region

B. A virtual machine named mystorageaccount

C. A database named mystorageaccount

D. A network interface named mystorageaccount

Solution

1. Step 1: Analyze resource type in template

   The resource type is "Microsoft.Storage/storageAccounts", which means a storage account.

2. Step 2: Check resource properties

   The name is "mystorageaccount" and location is "eastus", confirming the storage account details.

3. Final Answer:

   A storage account named mystorageaccount in East US region -> Option A

4. Quick Check:

   Resource type storageAccounts = storage account = A [OK]

Hint: Resource type defines what is created in ARM template [OK]

Common Mistakes:

• Confusing storage account with virtual machine
• Ignoring resource type and focusing on name
• Assuming location affects resource type

4. You try to deploy an ARM template but get an error saying the resource name is invalid. What is the most likely cause?

medium

A. The template schema URL is missing

B. The location is not specified

C. The API version is too old

D. The resource name contains unsupported characters

Solution

1. Step 1: Understand error message

   An invalid resource name error usually means the name has characters not allowed by Azure naming rules.

2. Step 2: Review other options

   Missing schema URL or old API version cause different errors; location missing usually triggers a different message.

3. Final Answer:

   The resource name contains unsupported characters -> Option D

4. Quick Check:

   Invalid name error = unsupported characters in name = B [OK]

Hint: Check resource name for invalid characters first [OK]

Common Mistakes:

• Assuming schema URL causes name errors
• Ignoring naming rules for resources
• Thinking location omission causes name errors

5. You want to deploy multiple resources together and ensure they are created in the right order using ARM templates. Which feature should you use?

hard

A. Define dependencies between resources using the "dependsOn" property

B. Deploy each resource separately in different templates

C. Use manual deployment steps outside ARM

D. Create resources without specifying order

Solution

1. Step 1: Identify how ARM manages resource order

   ARM uses the "dependsOn" property to specify which resources must be created first.

2. Step 2: Evaluate other options

   Deploying separately or manually loses automation benefits; no order risks deployment failures.

3. Final Answer:

   Define dependencies between resources using the "dependsOn" property -> Option A

4. Quick Check:

   Use dependsOn to control deployment order = C [OK]

Hint: Use dependsOn to set resource creation order [OK]

Common Mistakes:

• Deploying resources separately instead of together
• Ignoring dependsOn and causing deployment errors
• Relying on manual steps outside ARM