Study guide

3.5 Azure Blueprints, ARM Templates, and Bicep

Microsoft Azure Fundamentals AZ-900

Track your progress as you read

Finished sections get a check mark.

1 Introduction

About the Microsoft Azure Fundamentals (AZ-900) Exam Study Strategies and Exam Tips

2 Domain 1: Cloud Concepts (25-30%)

1.1 What Is Cloud Computing? 1.2 Cloud Service Models (IaaS, PaaS, SaaS) 1.3 Cloud Deployment Models (Public, Private, Hybrid) 1.4 The Consumption-Based Model

3 Domain 2A: Azure Architecture Components

2.1 Azure Regions and Availability Zones 2.2 Azure Resource Hierarchy (Management Groups, Subscriptions, Resource Groups) 2.3 Azure Resource Manager (ARM) Overview

4 Domain 2B: Azure Compute Services

2.3 Azure Virtual Machines 2.4 Azure App Service, Containers, and Serverless 2.5 Azure Virtual Desktop

5 Domain 2C: Azure Networking Services

2.6 Azure Virtual Networks (VNet) 2.7 Azure VPN Gateway and ExpressRoute 2.8 Azure Load Balancing and Content Delivery

6 Domain 2D: Azure Storage Services

2.9 Azure Storage Accounts and Services 2.10 Azure Database Services 2.11 Azure Data Services and Analytics

7 Domain 2E: Azure Identity, Access, and Security

2.11 Microsoft Entra ID (Azure Active Directory) 2.12 Azure RBAC, Zero Trust, and Defense in Depth 2.13 Azure Security Services

8 Domain 3A: Azure Cost Management

3.1 Factors That Affect Azure Costs 3.2 Azure Pricing Calculator and Cost Management 3.3 Using Tags for Cost Management and Organization

9 Domain 3B: Azure Governance and Compliance

3.3 Azure Policy 3.4 Resource Locks and Tags 3.5 Azure Blueprints, ARM Templates, and Bicep 3.6 Azure Governance Features: Putting It All Together

10 Domain 3C: Azure Monitoring and Management Tools

3.6 Azure Monitor and Service Health 3.7 Azure Compliance, Privacy, and Trust 3.8 Azure Activity Log, Diagnostics, and Resource Health

11 Additional Azure Services and Exam Review

Azure AI and Machine Learning Services Azure IoT and DevOps Services AZ-900 Exam Review: Key Concepts Summary Common AZ-900 Exam Scenarios and Practice

12 Advanced Azure Topics and Service Deep Dives

Azure Migration Services and Tools High Availability and Disaster Recovery in Azure Azure Networking: Private Link, Service Endpoints, and Bastion Azure Management Tools: Portal, CLI, PowerShell, and Cloud Shell Azure SLAs, Service Lifecycle, and Support Plans

3.5 Azure Blueprints, ARM Templates, and Bicep

Key Takeaways Explain This Topic AI

ARM (Azure Resource Manager) templates are declarative JSON files that define infrastructure as code for repeatable, idempotent deployments.

Bicep is Microsoft's domain-specific language that compiles down to ARM JSON with cleaner syntax, modules, and type safety.

Azure Blueprints packages policies, role assignments, ARM templates, and resource groups; Azure Blueprints (Preview) will be retired on January 31, 2027, with a phased retirement beginning July 31, 2026.

Microsoft says to migrate blueprint definitions and assignments to Deployment Stacks (recommended) and Template Specs before the retirement date.

AZ-900 tests WHAT these tools do, not how to write them; you must know ARM uses JSON and Bicep compiles to ARM.

Last updated: October 2026

Quick Answer: ARM templates (JSON) and Bicep (a cleaner DSL that compiles to ARM) define Azure infrastructure as code for repeatable, idempotent deployments. Azure Blueprints bundles policies, roles, and templates, but Azure Blueprints (Preview) will be retired on January 31, 2027 , with a phased retirement beginning July 31, 2026 ; Microsoft recommends migrating to Deployment Stacks and Template Specs.

Infrastructure as Code (IaC)

Infrastructure as Code (IaC) means provisioning and managing infrastructure through machine-readable definition files instead of clicking through portals. The same file deploys the same environment every time.

Benefit Why it matters

Consistency Dev, test, and prod come from one source of truth — no drift.

Repeatability Redeploy an identical environment in minutes after a disaster.

Version control Store templates in Git for history, review, and rollback.

Automation Run deployments inside CI/CD pipelines with no manual steps.

Documentation The template is the documentation of what exists.

ARM Templates (JSON)

ARM templates are JSON files that declare the resources to deploy. They are declarative — you state the desired end state and Azure Resource Manager works out the order and the API calls.

Template section Purpose

$schema The JSON schema describing the template language version.

contentVersion Your version string (e.g., 1.0.0.0).

parameters Inputs supplied at deploy time (VM name, region).

variables Reusable values built from parameters.

resources The resources to create or update.

outputs Values returned after deployment (e.g., a public IP).

Key properties: ARM is idempotent (re-running yields the same result, not duplicates), deploys independent resources in parallel , validates the template before any change, and offers what-if to preview changes.

Bicep

Bicep is Microsoft's domain-specific language (DSL) for Azure. Bicep files ( .bicep ) transpile (compile) into ARM JSON before deployment, so the runtime is identical — Bicep just makes authoring far easier.

  • Aspect ARM JSON Bicep
  • Syntax Verbose JSON Concise, declarative
  • File size Large Typically much smaller
  • Modules Linked templates (complex) Native module system
  • Tooling Limited IntelliSense Full VS Code support, type checking
  • Learning curve Steeper Gentler

On the Exam: You will NOT write template code. Know that ARM templates are JSON , Bicep compiles to ARM , both are declarative IaC , and both give repeatable deployments.

Azure Blueprints (Retiring January 31, 2027)

Azure Blueprints packages several governance artifacts into one versioned, deployable definition so an entire compliant environment can be stamped out repeatedly. Microsoft says Azure Blueprints (Preview) will be retired on January 31, 2027 , with a phased retirement beginning July 31, 2026 ; migrate blueprint definitions and assignments to Deployment Stacks (recommended) and Template Specs . Blueprints is not in the July 20, 2026 AZ-900 skills outline.

  • Blueprint artifact What it provides
  • Role assignments RBAC roles to grant
  • Policy assignments Azure Policies to enforce
  • ARM templates Resources to deploy
  • Resource groups Containers to create
  • Capability Blueprints (retiring) Replacement
  • Packaging templates Blueprint definition Template Specs
  • Managing a deployment as a unit Blueprint assignment Deployment Stacks
  • Protecting deployed resources Blueprint locks Deployment Stack deny settings
  • Azure Management Tools Summary
  • Tool Role
  • Azure portal Web GUI for managing resources
  • Azure CLI Cross-platform command line ( az , Bash-friendly)
  • Azure PowerShell PowerShell module ( Az )

Azure Cloud Shell Browser shell with Bash AND PowerShell; a storage account is optional and only needed to persist files

  • ARM templates / Bicep Native IaC
  • Terraform Third-party multi-cloud IaC

On the Exam: Cloud Shell runs in the browser with no local install and supports both Bash and PowerShell. The first time you start it, you can continue with or without storage; an Azure Storage account (file share) is needed only to persist your files between sessions.

Choosing the Right Tool — A Scenario

A team needs to stand up an identical three-tier web app in dev, test, and production with zero configuration drift. The portal is wrong here because manual clicks are not repeatable; the CLI and PowerShell are imperative scripts that can drift over time. The right answer is declarative IaC : author the resources once in Bicep , store the file in Git, and deploy it through a pipeline to all three environments. Because the deployment is idempotent , re-running it to apply a patch updates only what changed rather than creating duplicates, and what-if previews the impact before anyone commits.

Now suppose the same team must also stamp out, for each new business unit, a resource group plus the policies and role assignments that keep it compliant. Historically that was Azure Blueprints , which packaged all of those artifacts together. With Blueprints retiring on January 31, 2027 , the team should instead store the templates as Template Specs and deploy them through Deployment Stacks , using the stack's deny settings to protect the deployed resources the way Blueprint locks used to.

Common Traps

ARM is JSON, Bicep is a DSL that compiles to ARM — they are not rivals, Bicep sits on top of ARM.

Terraform is third-party and multi-cloud; ARM and Bicep are Azure-native.

Blueprints is being retired — if a question offers it as a new recommendation, prefer Template Specs and Deployment Stacks.

Cloud Shell storage is optional : without a storage account, files don't persist between sessions.