Azure Resource Manager's What-If operation is the Bicep equivalent of `terraform plan` — it predicts infrastructure changes before applying them. The post covers how to run What-If at different deployment scopes, how to interpret its output symbols (create, delete, modify, nochange), and how to integrate it as a mandatory pipeline stage. Key guidance includes treating deletions as a separate risk class, classifying modifications by blast radius rather than line count, handling provider-generated noise by establishing a baseline, using JSON output for automated policy gates, and understanding that What-If is pre-deployment evidence rather than a state lock.

12m read timeFrom build5nines.com
Post cover image
Table of contents
Generate an Azure Bicep Plan with What-IfPull Requests Show Intent, Not ImpactInsight and AnalysisConclusion
1.2K Impressions