All Articles
On this page
DevOps

Azure Bicep vs Terraform in 2026: Which to Use

C
Chandan Kumar
Founder, beCloudReady
April 19, 2024Updated November 1, 20266 min read
Azure Bicep vs Terraform in 2026: Which to Use

Azure Bicep or Terraform in 2026? A comparison of licensing, state, provider support and when each one fits your Azure team.

Last updated November 2, 2026. We re-checked the licence, release and feature claims below against Microsoft Learn and the project repositories.

Short answer

  • Azure only, and you want the least to manage: Bicep. It is free, Microsoft supports it, and Azure keeps the state for you.
  • More than Azure, or you want one tool across clouds and SaaS: Terraform, or OpenTofu if you need an open-source licence.

Both are declarative infrastructure as code. Both show you a preview before they change anything. The real differences are scope, state and licence.

Where things stand in 2026

Azure BicepTerraform
ScopeAzure resources onlyPublic clouds, private clouds and SaaS, through providers
Latest release we checkedv0.48.1 (October 5, 2026)v1.17.1 (October 28, 2026)
Licence and costFree and open source, supported by Microsoft SupportBusiness Source License from version 1.6.0, licensor listed as IBM
StateAzure stores it. No state files to manageYou manage a state file, usually in a remote backend
New Azure featuresMicrosoft says new resource types and API versions work as soon as the provider releases themAzureRM covers stable resources. AzAPI calls Azure APIs directly for the latest features
Preview before deploywhat-ifterraform plan
Code reuseModulesModules, plus a large public registry
Open-source forkNot applicableOpenTofu (latest release we checked: v1.13.2, October 21, 2026)

What changed since 2024

  • Licensing. Terraform moved to the Business Source License from version 1.6.0, and the licence file now lists IBM as licensor. For most teams that run Terraform internally, nothing breaks. If your legal team requires open-source licences, or you build a product on top of Terraform, check the licence terms. OpenTofu exists for that case.
  • Two Azure providers. Microsoft documents several Terraform providers for Azure: AzureRM for stable resources and AzAPI for the Azure Resource Manager APIs directly. AzAPI gives you the latest Azure features without waiting for a provider update. AzureRM's latest release we checked is v5.12.0 (October 29, 2026).
  • Bicep is steady. Microsoft describes Bicep as supporting "all preview and GA versions for Azure services" as soon as a resource provider ships them. It also says Bicep has "no state or state files to manage."

How each one works

Bicep is a language for Azure only. It is a transparent layer over Azure Resource Manager (ARM) templates: the Bicep tooling turns your file into an ARM template at deploy time. You can also decompile an existing ARM JSON template into Bicep. Azure Resource Manager orders the deployment of dependent resources for you.

Terraform uses HashiCorp Configuration Language (HCL). You describe resources from any provider, and Terraform builds a plan from your code and its state file. The state file records what Terraform manages, so you must store it safely, lock it during runs and control who can read it. A remote backend such as an Azure Storage account is the usual choice.

Choosing

Pick Bicep when:

  • Your estate is Azure only and will stay that way.
  • You want Microsoft support and no state file to protect.
  • Your team already knows ARM templates or Azure Policy.

Pick Terraform (or OpenTofu) when:

  • You manage Azure plus AWS, GitHub, Datadog or other services in one workflow.
  • You already run Terraform elsewhere and want one skill set.
  • You want the public module and provider ecosystem.

Plan for the learning curve. Bicep is easier for an Azure team to pick up. Terraform asks you to learn providers, state and backends too, which pays off once you leave Azure.

Moving between them

Moving from ARM JSON to Bicep is supported by the Bicep decompile command. Moving from Bicep to Terraform, or the reverse, means rewriting. Terraform can import existing resources into state, but you write the configuration yourself. Start with one landing-zone module, not the whole estate.

Need a hand?

If a migration or an Azure environment rebuild is on your list, we do that at a fixed price. See Kubernetes setup and migration for AKS and EKS work, and the IT end-of-life calendar for upcoming Microsoft and AWS deadlines such as Azure Front Door classic and Azure Lab Services.

Sources

Frequently asked questions

Does Bicep need a state file?

No. Microsoft says Azure stores the state, so there are no state files to manage. Terraform keeps a state file that you store and protect, usually in a remote backend.

Is Terraform still open source?

Terraform versions 1.6.0 and later use the Business Source License, and the licensor is listed as IBM. OpenTofu is the open-source fork if you need an open-source licence.

Can I use both?

Yes. Some teams use Bicep for Azure-only landing zones and Terraform where they also manage other clouds or SaaS. Pick one per project so the team does not maintain two styles of the same thing.

Azure BicepTerraformOpenTofuIaCAzureInfrastructure