IaC Common Skill

Shared deployment patterns used by both Bicep and Terraform deploy agents (07b, 07t) and review subagents.

Preflight validation (CLI auth, governance mapping, stop rules, known issues) has moved to the azure-validate skill. See azure-validate/references/infraops-preflight.md.

Deployment Strategies

azd Deployment (default for all projects)

Use azd for all projects. Each project is a self-contained azd project with azure.yaml and .azure/ inside infra/{iac}/{project}/.

# Navigate to the project directory (azure.yaml must be here)
cd infra/{iac}/{project}

# Or use -C flag from repo root
azd -C infra/{iac}/{project} env list

# Create/select environment (use {project}-{env} naming to avoid collisions)
azd env new {project}-{env}
azd env set AZURE_LOCATION swedencentral

# Preview changes (replaces what-if)
azd provision --preview

# Deploy infrastructure
azd provision

# Full provision + deploy in one step
azd up

azd hooks replace the deprecated deploy.ps1 pre/post steps:

• preprovision — auth validation, banner, prerequisite checks
• postprovision — resource verification, diagnostic setup

Environment management replaces manual parameterization:

• azd env new prod / azd env new dev
• azd env set AZURE_LOCATION swedencentral

azd Environment Preflight (MANDATORY for --no-prompt Deploys)

Before azd provision --no-prompt, verify these environment values are set:

• AZURE_SUBSCRIPTION_ID — from az account show --query id -o tsv
• AZURE_RESOURCE_GROUP — target resource group name
• AZURE_ENV_NAME — environment name
• AZURE_LOCATION — target region

Run azd env get-values and check for missing values. If any are empty, set them via azd env set {KEY} {VALUE} before attempting --no-prompt.

Phased Deployment via deploy.ps1 (deprecated)

⚠️ Deprecated. Use azd hooks (preprovision/postprovision) for phased deployment workflows instead. deploy.ps1 is retained only for backward compatibility with projects that predate azure.yaml adoption.

• Bicep: Pass -Phase {name} to deploy.ps1
• Terraform: Pass -var deployment_phase={name} to plan/apply

Single Deployment (only for <5 resources, dev/test)

Deploy everything in one operation. Still requires user approval.

Decision: azd vs deploy.ps1

Full guide: azd-vs-deploy-guide.md — comparison, per-project conventions, workflow, hooks, troubleshooting.

Reference Index

Circuit Breaker

Deploy agents MUST read references/circuit-breaker.md before starting any deployment. It defines:

• Failure taxonomy: 6 categories (build, validation, deployment, empty, timeout, auth)
• Anomaly patterns: detection thresholds for repetitive failures
• Stopping rule: 3 consecutive same-type failures → halt + escalate
• Escalation protocol: write to session state, notify user, wait for guidance