azure-validate

Preflight checks for Azure Bicep or Terraform deployments validate that templates compile and previews succeed before deployment. Recipe-driven validation executes the appropriate flow for your chosen IaC approach and records the results.

Azure Developer CLI deployments fail when configuration, infrastructure definitions, or permissions are incorrect. Running pre-deployment validation catches template, build, policy, or environment issues early so the eventual deployment runs cleanly.

AZD pre-deployment validation works with both Bicep and Terraform, as well as AZCLI scenarios. It runs recipe-specific validation commands based on your chosen infrastructure as code approach to ensure readiness.

The best way to validate Azure infrastructure templates is using recipe-driven validation that checks azure.yaml configuration, compiles Bicep or Terraform definitions, and records proof of successful checks before deployment.

Yes, you need an approved plan file. Validation requires loading `.azure/plan.md` with status `Approved` or later to run the full preflight validation and record the results before proceeding to deployment.

You should not skip preflight validation for Azure IaC templates if you want to prevent failed deployments, but it cannot be run without an approved `.azure/plan.md` file from the prepare phase.