How is ResourcePulse different from az deployment what-if?

az deployment what-if tells you which resources will be created, modified, or deleted — but it says nothing about cost. ResourcePulse adds the cost dimension: a monthly cost delta appears directly in your GitHub PR comment so you can see the price of every Bicep change before it merges.

Do you need access to our Azure subscription?

No. ResourcePulse analyzes Bicep files and parameters statically. It resolves resource definitions, regions, and SKUs from your code — no Azure credentials or subscription access required.

How do you resolve regions in Bicep?

We trace the location parameter through your Bicep files and parameter files. If an explicit value is found (e.g. westeurope), we use it. If it references resourceGroup().location, we note it and use a configured default or flag it.

Can I use dev/prod parameters?

Yes. Set the param_file input in your workflow YAML to point to a .bicepparam file for the target environment. ResourcePulse will resolve pricing and governance checks against the correct parameter set.

Is this replacing Azure Policy?

No. ResourcePulse is a shift-left complement. It catches issues at PR time before they reach Azure. Azure Policy still enforces at deployment time. Think of ResourcePulse as an early warning system.

Each plan includes a monthly run quota. One run equals one PR event (open, sync, or reopen). If you hit your limit, new PRs are skipped with a notice. You can upgrade at any time.

FinOps for Azure Bicep: How to Catch Cost Before It Deploys

FinOps for Azure Bicep: How to Catch Cost Before It DeploysFinOps practice reaches engineers too late when it lives only in dashboards. Here is how to bring cost review into the Bicep PR workflow — where infrastructure decisions are still cheap to change.Please enable JavaScript to use this application.