Getting Started with Azure Bicep: Infrastructure as Code Made Simple

Why Bicep Over ARM Templates

If you've ever written an ARM template, you know the pain. Hundreds of lines of JSON, nested brackets everywhere, and error messages that make you question your career choices.

Bicep fixes this. It's a domain-specific language that compiles to ARM templates but is actually readable. Same power, less suffering.

Setting Up Your Environment

Install Bicep

If you have Azure CLI installed (you should), Bicep comes with it. Run az bicep version to check, and az bicep upgrade to get the latest version.

For VS Code, install the Bicep extension. It gives you IntelliSense, syntax highlighting, and validation as you type.

Bicep Basics

Parameters

Parameters let you customize deployments without changing the template:

param environment string
param location string = resourceGroup().location

@allowed(['Standard_LRS', 'Standard_GRS', 'Premium_LRS'])
param storageSku string = 'Standard_LRS'

@secure()
param adminPassword string

Variables

Variables help you build complex values. You can combine parameters, use conditional logic, and create derived values.

Resources

Resources are what you're actually deploying:

resource storageAccount 'Microsoft.Storage/storageAccounts@2023-01-01' = {
  name: storageAccountName
  location: location
  sku: { name: storageSku }
  kind: 'StorageV2'
}

Notice how Bicep automatically figures out deployment order based on resource references.

Outputs

Return values from your deployment to use in other templates or scripts.

Deploying Your Bicep Files

Using Azure CLI

Create a resource group, then deploy your template:

az group create --name rg-myproject-dev --location eastus
az deployment group create --resource-group rg-myproject-dev --template-file main.bicep --parameters projectName=myproject environment=dev

Using Parameter Files

For repeatable deployments, create parameter files (JSON) that specify your parameter values.

Modules: Organizing Your Code

As your infrastructure grows, use modules to stay organized. Create separate .bicep files for reusable components like storage accounts, web apps, or databases.

Tips for Success

1. Use the VS Code extension - The real-time validation saves hours of debugging
2. Start small - Convert one resource at a time from existing ARM templates
3. Use What-If - Preview changes before deploying
4. Version your templates - Store in Git, use branches for different environments
5. Automate deployments - Pair Bicep with [Azure DevOps Pipelines](/blog/azure-devops-pipelines-beginners-guide) for gate-protected, multi-environment deployments
6. Leverage existing modules - Check the Azure Verified Modules registry

Bicep makes infrastructure as code accessible. Start with simple deployments, build your library of modules, and soon you'll wonder how you ever managed Azure without it.

Frequently Asked Questions

What is Azure Bicep?

Azure Bicep is a domain-specific language (DSL) from Microsoft for deploying Azure resources declaratively. It compiles down to standard ARM template JSON, so it runs on the same deployment engine, but the syntax is far more concise and readable than hand-written JSON.

Is Bicep the same as ARM templates?

No, but they are closely related. Bicep is a syntax layer on top of ARM templates: every Bicep file compiles to an equivalent ARM JSON template before deployment. You get the same resource providers, API versions, and deployment behavior as ARM, with a cleaner authoring experience and built-in tooling like type checking and IntelliSense.

How do I convert an existing ARM template to Bicep?

Use the Azure CLI command az bicep decompile, pointing it at your ARM template JSON file. It generates a starting Bicep file that you should then review and clean up, since automated decompilation sometimes produces verbose variable names or structures that benefit from manual simplification.

What does the Bicep What-If command do?

az deployment group what-if runs a dry run of your deployment, showing exactly what resources will be created, modified, or deleted without actually making changes. This is essential before running deployments against production resource groups, since it catches unintended changes such as a resource being recreated due to an immutable property change.

Do I need to install anything extra to use Bicep?

If you have a recent version of the Azure CLI, Bicep is bundled in. Run az bicep version to confirm, and az bicep upgrade to update to the latest version. For local development, install the Bicep extension for VS Code to get syntax highlighting, IntelliSense, and inline validation as you write templates.