Estimate ARM template and Bicep costs before you deploy
Blog post from Infracost
Infracost CLI v2.15.0 adds native support for estimating costs from Azure ARM JSON templates without deployments, Azure credentials, or subscriptions, addressing cost changes that can depend on parameter files, conditional resource definitions, loops, regions, and VM-size expressions. The tool evaluates ARM templates using an interpreter designed to handle Azure’s extensive function set, copy loops, conditions, nested templates, custom functions, and parameter-resolution behavior, enabling separate estimates for discovered development and production parameter files. ARM estimates use the same Infracost pricing data, policies, tagging rules, local caching, CI integration, and pull-request cost reporting available for Terraform, CloudFormation, Kubernetes, and other supported infrastructure-as-code formats. Bicep files must first be compiled into ARM JSON, and limitations include no expansion of Template Specs, no support for sovereign clouds or Bicep metadata, and some Azure resource values reported as unknown rather than estimated.
No tracked trend matches for this post yet.
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.