Technical guideDevOps

Getting started with infrastructure as code

Define an Azure resource in Bicep and see why it beats clicking in a portal.

  • Anavo team
  • October 20, 2026
  • 1 min read

Infrastructure as code describes your environment in files that can be reviewed, versioned, and reused. The result is repeatable environments and fewer surprises.

A first resource

The example below declares an Azure storage account in Bicep. The name is derived from the resource group so it stays unique.

bicep
param location string = resourceGroup().location

resource storage 'Microsoft.Storage/storageAccounts@2023-01-01' = {
  name: 'stexample${uniqueString(resourceGroup().id)}'
  location: location
  sku: {
    name: 'Standard_LRS'
  }
  kind: 'StorageV2'
}

Why it matters

  • Changes are reviewed like application code
  • Environments can be recreated on demand
  • Drift between environments is visible

Get new insights by email

Occasional articles, guides, and event invitations. No spam, unsubscribe any time.

Want to talk it through?

Book a consultation to discuss how this applies to you.

  1. 1Tell us your goalsShare a few details.
  2. 2We confirm a timeWe reply with a time that works.
  3. 3We talk it throughA focused conversation on next steps.