azure-deployment-preflight

This skill validates Bicep deployments before execution, supporting both Azure CLI ( az ) and Azure Developer CLI ( azd ) workflows. Follow these steps in order. Continue to the next step even if a previous step fails—capture all issues in the final report. Determine the deployment workflow by checking for project indicators: Check for azd project : Look for azure.yaml in the project root Locate Bicep files : Find all .bicep files to validate Auto-detect parameter files : For each Bicep file, look for matching parameter files: Run Bicep CLI to check template syntax before attempting deployment validation: What to capture: If Bicep CLI is not installed: Choose the appropriate validation based on project type detected in Step 1. Use azd provision --preview to validate the deployment: If an environment is specified or multiple environments exist: Determine the deployment scope from the Bicep file's targetScope declaration: Run with Provider validation level first: Fallback Strategy: If --validation-level Provider fails with permission errors (RBAC), retry with ProviderNoRbac : Note the fallback in the report—the user may lack full deployment permissions. Parse the what-if output to categorize resource changes: For modified resources, capture the specific property changes. Create a Markdown report file in the project root named: Use the template structure from...