Azure Storage backend in Terraform - Mini Project: Build & Apply

Azure Storage backend

📖 Scenario: You are setting up Terraform to store its state files securely in Azure Storage. This helps teams collaborate safely and keeps your infrastructure state consistent.

🎯 Goal: Create a Terraform configuration that uses an Azure Storage Account as the backend to store the Terraform state file.

📋 What You'll Learn

Create a resource group named exactly tfstate-rg

Create a storage account named exactly tfstateaccount

Create a storage container named exactly tfstatecontainer

Configure the Terraform backend to use the Azure Storage Account with the correct resource group, storage account, and container names

💡 Why This Matters

🌍 Real World

Storing Terraform state files in Azure Storage is a common practice in real projects to enable collaboration and state locking.

💼 Career

Understanding how to configure remote backends in Terraform is essential for cloud engineers and DevOps professionals working with Azure.

1

Create the Azure resource group

Write Terraform code to create a resource group named tfstate-rg in the eastus location. Use the resource type azurerm_resource_group and name the resource tfstate_rg.

Terraform

# Your code here to create resource group tfstate-rg

Hint

Use resource "azurerm_resource_group" "tfstate_rg" with name = "tfstate-rg" and location = "eastus".

2

Create the Azure storage account

Add Terraform code to create a storage account named tfstateaccount in the resource group tfstate-rg. Use the resource type azurerm_storage_account and name the resource tfstate_sa. Set account_tier to Standard and account_replication_type to LRS.

Terraform

resource "azurerm_resource_group" "tfstate_rg" {
  name     = "tfstate-rg"
  location = "eastus"
}

# Your code here to create storage account tfstateaccount

Hint

Use resource "azurerm_storage_account" "tfstate_sa" with the exact name and link to the resource group.

3

Create the storage container

Add Terraform code to create a storage container named tfstatecontainer inside the storage account tfstateaccount. Use the resource type azurerm_storage_container and name the resource tfstate_container. Set the container_access_type to private.

Terraform

resource "azurerm_resource_group" "tfstate_rg" {
  name     = "tfstate-rg"
  location = "eastus"
}

resource "azurerm_storage_account" "tfstate_sa" {
  name                     = "tfstateaccount"
  resource_group_name      = azurerm_resource_group.tfstate_rg.name
  location                 = azurerm_resource_group.tfstate_rg.location
  account_tier             = "Standard"
  account_replication_type = "LRS"
}

# Your code here to create storage container tfstatecontainer

Hint

Use resource "azurerm_storage_container" "tfstate_container" with the exact container name and link to the storage account.

4

Configure the Terraform backend

Add the terraform block to configure the backend to use Azure Storage. Set storage_account_name to tfstateaccount, container_name to tfstatecontainer, and resource_group_name to tfstate-rg. Use key as terraform.tfstate.

Terraform

resource "azurerm_resource_group" "tfstate_rg" {
  name     = "tfstate-rg"
  location = "eastus"
}

resource "azurerm_storage_account" "tfstate_sa" {
  name                     = "tfstateaccount"
  resource_group_name      = azurerm_resource_group.tfstate_rg.name
  location                 = azurerm_resource_group.tfstate_rg.location
  account_tier             = "Standard"
  account_replication_type = "LRS"
}

resource "azurerm_storage_container" "tfstate_container" {
  name                  = "tfstatecontainer"
  storage_account_name  = azurerm_storage_account.tfstate_sa.name
  container_access_type = "private"
}

# Your code here to configure terraform backend

Hint

Use the terraform block with backend "azurerm" and set the exact names for resource group, storage account, container, and key.

Practice

1. What is the main purpose of using an Azure Storage backend in Terraform?

easy

A. To write Terraform code in a graphical interface

B. To run Terraform commands faster locally

C. To create virtual machines automatically

D. To securely store Terraform state files in the cloud

Solution

1. Step 1: Understand Terraform state management

   Terraform state files keep track of resources it manages. Storing them securely is important.

2. Step 2: Role of Azure Storage backend

   Azure Storage backend stores these state files in the cloud, allowing safe sharing and locking.

3. Final Answer:

   To securely store Terraform state files in the cloud -> Option D

4. Quick Check:

   Azure Storage backend = secure state storage [OK]

Hint: Azure Storage backend = cloud storage for Terraform state [OK]

Common Mistakes:

• Thinking it speeds up Terraform commands locally
• Confusing backend with resource creation
• Assuming it provides a GUI for Terraform

2. Which of the following is the correct syntax to configure an Azure Storage backend in Terraform?

easy

A. backend "azure" { account = "myaccount" container = "tfstate" file = "terraform.tfstate" }

B. backend "azurerm" { storage_account_name = "myaccount" container_name = "tfstate" key = "terraform.tfstate" }

C. backend "azurerm" { storage = "myaccount" bucket = "tfstate" state_file = "terraform.tfstate" }

D. backend "azure_storage" { account_name = "myaccount" container_name = "tfstate" key_name = "terraform.tfstate" }

Solution

1. Step 1: Identify correct backend type and keys

   The official backend type for Azure Storage is "azurerm" with keys: storage_account_name, container_name, and key.

2. Step 2: Match syntax with official docs

   backend "azurerm" { storage_account_name = "myaccount" container_name = "tfstate" key = "terraform.tfstate" } matches the correct syntax exactly, others use wrong backend names or keys.

3. Final Answer:

   backend "azurerm" { storage_account_name = "myaccount" container_name = "tfstate" key = "terraform.tfstate" } -> Option B

4. Quick Check:

   Backend type "azurerm" with correct keys = backend "azurerm" { storage_account_name = "myaccount" container_name = "tfstate" key = "terraform.tfstate" } [OK]

Hint: Use backend "azurerm" with storage_account_name, container_name, key [OK]

Common Mistakes:

• Using wrong backend type like "azure" or "azure_storage"
• Incorrect key names like bucket or file
• Missing quotes around string values

3. Given this backend configuration snippet, what will happen if you run terraform init?

terraform {
  backend "azurerm" {
    storage_account_name = "tfstorage123"
    container_name       = "tfstate"
    key                  = "prod.terraform.tfstate"
  }
}

medium

A. Terraform will ignore the backend and use local state

B. Terraform will create the storage account automatically

C. Terraform will initialize and connect to the Azure Storage backend to manage state

D. Terraform will fail because the container name is missing

Solution

1. Step 1: Understand terraform init with backend

   terraform init reads backend config and connects to remote storage for state management.

2. Step 2: Check config completeness

   All required fields (storage_account_name, container_name, key) are present, so initialization succeeds.

3. Final Answer:

   Terraform will initialize and connect to the Azure Storage backend to manage state -> Option C

4. Quick Check:

   terraform init + valid backend config = connect to remote state [OK]

Hint: terraform init connects backend if config is complete [OK]

Common Mistakes:

• Assuming terraform creates storage account or container
• Thinking missing container name causes failure here
• Believing backend is ignored without explicit flag

4. You configured your Terraform backend with Azure Storage but get this error on terraform init: "Error: storage account name must be between 3 and 24 characters, and use only numbers and lowercase letters." What is the likely cause?

medium

A. The storage_account_name contains uppercase letters or invalid characters

B. The container_name is missing in the backend block

C. The key value is too long

D. Terraform version is outdated

Solution

1. Step 1: Analyze error message details

   The error states storage account name rules: length 3-24, only numbers and lowercase letters.

2. Step 2: Identify cause from options

   The storage_account_name contains uppercase letters or invalid characters matches the error cause: invalid characters or uppercase letters in storage_account_name.

3. Final Answer:

   The storage_account_name contains uppercase letters or invalid characters -> Option A

4. Quick Check:

   Storage account name rules violated = The storage_account_name contains uppercase letters or invalid characters [OK]

Hint: Storage account name must be 3-24 lowercase letters/numbers [OK]

Common Mistakes:

• Ignoring case sensitivity in storage account name
• Assuming container_name missing causes this error
• Blaming Terraform version without checking config

5. You want to share Terraform state securely among your team using Azure Storage backend. Which combination of settings ensures state locking and encryption at rest?

hard

A. Use backend "azurerm" with storage_account_name, container_name, key; enable blob storage versioning and Azure Storage encryption

B. Use backend "azurerm" with storage_account_name and key only; disable container access control

C. Use backend "azurerm" with container_name and key only; enable public access to container

D. Use backend "azurerm" with storage_account_name, container_name, key; disable encryption for faster access

Solution

1. Step 1: Identify required backend config for state sharing

   Storage account name, container name, and key are needed to locate the state file.

2. Step 2: Ensure state locking and encryption

   Azure Blob Storage supports state locking via blob leases and encryption at rest by default; enabling versioning adds safety.

3. Final Answer:

   Use backend "azurerm" with storage_account_name, container_name, key; enable blob storage versioning and Azure Storage encryption -> Option A

4. Quick Check:

   Proper backend config + encryption + locking = secure shared state [OK]

Hint: Enable blob versioning and encryption for secure shared state [OK]

Common Mistakes:

• Omitting container_name causes backend failure
• Allowing public access weakens security
• Disabling encryption risks data exposure