#7 of 28 infrastructure automation tools · Updated October 2026
Bicep review 2026
Azure Bicep (with ARM and deployment stacks) · Dependable builder
Bicep ranks #7 of 28 infrastructure automation tools in the Infrastructure Automation Ledger 2026, with a Ledger Index of 59.6 out of 100. Azure Bicep: a typed, state-free language for Azure, shipped monthly; on-prem VMs only through Azure Arc, no Proxmox VE, Nutanix or XCP-ng target.
Scores
Source: Infrastructure Automation Ledger 2026, edition 2026-10-16. How each score works: methodology.
Pros
- Language and authoring4/5
- Security and compliance4/5
Cons
- Bare metal and day-2 operations0.5/5
- Configuration management depth1/5
- Provisioning breadth2.5/5
What the Ledger says
Bicep scores as the single-cloud reference for a language without a state file: Azure holds the state, what-if is the plan, and deployment stacks added the managed-resource list and deny settings that a state-based tool gets from its state file. The language itself is the strongest part of the record, with a release about every month and experimental features that do reach GA, if slowly. Breadth and bare metal are low by design: vSphere and Hyper-V are reachable only through Azure Arc, which needs a resource bridge and a live connection to Azure, and Proxmox VE, Nutanix, XCP-ng and KubeVirt have no path at all. The one thing to check is which features your templates rely on, because experimental features are excluded from Microsoft Support, and the Kubernetes extension and local deploy have stayed experimental for more than two years.
Bicep's AI story is one local MCP server, shipped in the VS Code extension from 0.40.2 (2026-01-24) and as a NuGet package, with ten read-only tools for schemas, diagnostics, decompile, snapshots and Azure Verified Module metadata. It does not deploy, and the documentation claims no identity, guardrail or audit layer beyond local execution. There is no Bicep-specific code generator, no plan explanation and no AI in operations.
Capability by area
Buying, lock-in and release record
Buying and licence (commercial risk)(lower is better)
- Price and licence volatility0.5
- Free and MIT throughout; no pricing page exists
- Purchase constraints0.5
- Nothing to buy; an Azure subscription is needed to deploy
- Channel and access0.5
- Open download from GitHub, winget, the Azure CLI and the VS Code extension
- Owner stability0.5
- Microsoft, built in house; no ownership change
- Cost of staying supported1
- Free updates; the current CLI is expected; experimental features excluded from support; Arc-enabled SCVMM retires September 2029
Technical lock-in(lower is better)
- Formats3
- Azure-specific language compiled to ARM JSON; open-source compiler and decompiler
- Export path2.5
- Decompile ARM to Bicep and export stack resources as JSON; nothing out to another cloud or tool
- Stack coupling4
- Azure resource model only
- Hardware / cloud coupling4
- Azure control plane required even for on-prem VMs, through an Arc resource bridge; sovereign and custom clouds supported
- Skills and tooling coupling1.5
- Large Azure skills base; Azure CLI and PowerShell skills carry over
Release credibility
- Cadence3.5
- Ten minor versions in twelve months, about monthly; no published schedule
- Roadmap transparency3.5
- Open GitHub repository, release notes and experimental feature docs; no written roadmap
- Say-do3.5
- Experimental items reach GA (snapshot in 9 months, console in 6, extendable parameter files in 23); Kubernetes extension and local deploy still experimental after two years
- Velocity4
- Several language and tooling items per release
- Lifecycle stability3
- Still 0.x with breaking changes in minor versions and no support windows; ARM compatibility kept; deprecations carried out on notice
Partners and services
- Partner programme openness3.5
- Microsoft partner programme exists; terms not read; anyone can publish modules and contribute to Azure Verified Modules
- Multi-tenancy and self-service4
- Azure RBAC with two deployment stack roles, management group scope, deny settings, Arc RBAC for on-prem VMs
- API and infrastructure-as-code4.5
- First-class front end to ARM; SDKs in five languages; RPC client and language server packages
- Skills and certification4
- Microsoft certifications and a large skills pool; specific tracks not checked
Alternatives to Bicep
Questions about Bicep
Is Bicep any good?
Bicep ranks #7 of 28 infrastructure automation tools in the Infrastructure Automation Ledger 2026, with a Ledger Index of 59.6 out of 100. Its strongest areas are language and authoring, security and compliance. Its weakest are bare metal and day-2 operations, configuration management depth, provisioning breadth.
What are the best alternatives to Bicep?
The closest by Ledger Index are Harness IaCM (59.3), Ansible (60.4), env zero (58.8), Pulumi (61.2).
How is Bicep licensed and sold?
Free and MIT throughout; no pricing page exists.
How much lock-in does Bicep bring?
Bicep scores 15 out of 25 on technical lock-in (lower is better). Export path: Decompile ARM to Bicep and export stack resources as JSON; nothing out to another cloud or tool.
User reviews of Bicep
No reviews yet
Be the first to say how Bicep worked for you.
Write a review
No account needed and no email asked. We read every review before it appears and remove adverts, spam and personal attacks.