Index of every page on this site: llms.txt
All skills
github avatar

/azure-deployment-preflight

@f10fdb8 official
by githubgithub/awesome-copilot41k stars
5,399
Run it yourself

Performs comprehensive preflight validation of Bicep deployments to Azure, including template syntax validation, what-if analysis, and permission checks. Use this skill before any deployment to Azure to preview changes, identify potential issues, and ensure the deployment will succeed. Activate when users mention deploying to Azure, validating Bicep files, checking deployment permissions, previewing infrastructure changes, running what-if, or preparing for azd provision.

Use this Skill: https://skilld.dev/gh/github/awesome-copilot/azure-deployment-preflight

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈126 tokens for metadata: the name and description. ≈1.7k when used: this file. ≈6.2k more on demand in 3 files.

Description uses 6.3% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈504 characters, or 6.3%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Azure Deployment Preflight Validation

This skill validates Bicep deployments before execution, supporting both Azure CLI (az) and Azure Developer CLI (azd) workflows.

When to Use This Skill

  • Before deploying infrastructure to Azure
  • When preparing or reviewing Bicep files
  • To preview what changes a deployment will make
  • To verify permissions are sufficient for deployment
  • Before running azd up, azd provision, or az deployment commands

Validation Process

Follow these steps in order. Continue to the next step even if a previous step fails—capture all issues in the final report.

Step 1: Detect Project Type

Determine the deployment workflow by checking for project indicators:

  1. Check for azd project: Look for azure.yaml in the project root

    • If found → Use azd workflow
    • If not found → Use az CLI workflow
  2. Locate Bicep files: Find all .bicep files to validate

    • For azd projects: Check infra/ directory first, then project root
    • For standalone: Use the file specified by the user or search common locations (infra/, deploy/, project root)
  3. Auto-detect parameter files: For each Bicep file, look for matching parameter files:

    • <filename>.bicepparam (Bicep parameters - preferred)
    • <filename>.parameters.json (JSON parameters)
    • parameters.json or parameters/<env>.json in same directory

Step 2: Validate Bicep Syntax

Run Bicep CLI to check template syntax before attempting deployment validation:

bicep build <bicep-file> --stdout

What to capture:

  • Syntax errors with line/column numbers
  • Warning messages
  • Build success/failure status

If Bicep CLI is not installed:

  • Note the issue in the report
  • Continue to Step 3 (Azure will validate syntax during what-if)

Step 3: Run Preflight Validation

Choose the appropriate validation based on project type detected in Step 1.

For azd Projects (azure.yaml exists)

Use azd provision --preview to validate the deployment:

azd provision --preview

If an environment is specified or multiple environments exist:

azd provision --preview --environment <env-name>
For Standalone Bicep (no azure.yaml)

Determine the deployment scope from the Bicep file's targetScope declaration:

Target Scope Command
resourceGroup (default) az deployment group what-if
subscription az deployment sub what-if
managementGroup az deployment mg what-if
tenant az deployment tenant what-if

Run with Provider validation level first:

# Resource Group scope (most common)
az deployment group what-if \
  --resource-group <rg-name> \
  --template-file <bicep-file> \
  --parameters <param-file> \
  --validation-level Provider

# Subscription scope
az deployment sub what-if \
  --location <location> \
  --template-file <bicep-file> \
  --parameters <param-file> \
  --validation-level Provider

# Management Group scope
az deployment mg what-if \
  --location <location> \
  --management-group-id <mg-id> \
  --template-file <bicep-file> \
  --parameters <param-file> \
  --validation-level Provider

# Tenant scope
az deployment tenant what-if \
  --location <location> \
  --template-file <bicep-file> \
  --parameters <param-file> \
  --validation-level Provider

Fallback Strategy:

If --validation-level Provider fails with permission errors (RBAC), retry with ProviderNoRbac:

az deployment group what-if \
  --resource-group <rg-name> \
  --template-file <bicep-file> \
  --validation-level ProviderNoRbac

Note the fallback in the report—the user may lack full deployment permissions.

Step 4: Capture What-If Results

Parse the what-if output to categorize resource changes:

Change Type Symbol Meaning
Create + New resource will be created
Delete - Resource will be deleted
Modify ~ Resource properties will change
NoChange = Resource unchanged
Ignore * Resource not analyzed (limits reached)
Deploy ! Resource will be deployed (changes unknown)

For modified resources, capture the specific property changes.

Step 5: Generate Report

Create a Markdown report file in the project root named:

  • preflight-report.md

Use the template structure from references/REPORT-TEMPLATE.md.

Report sections:

  1. Summary - Overall status, timestamp, files validated, target scope
  2. Tools Executed - Commands run, versions, validation levels used
  3. Issues - All errors and warnings with severity and remediation
  4. What-If Results - Resources to create/modify/delete/unchanged
  5. Recommendations - Actionable next steps

Required Information

Before running validation, gather:

Information Required For How to Obtain
Resource Group az deployment group Ask user or check existing .azure/ config
Subscription All deployments az account show or ask user
Location Sub/MG/Tenant scope Ask user or use default from config
Environment azd projects azd env list or ask user

If required information is missing, prompt the user before proceeding.

Error Handling

See references/ERROR-HANDLING.md for detailed error handling guidance.

Key principle: Continue validation even when errors occur. Capture all issues in the final report.

Error Type Action
Not logged in Note in report, suggest az login or azd auth login
Permission denied Fall back to ProviderNoRbac, note in report
Bicep syntax error Include all errors, continue to other files
Tool not installed Note in report, skip that validation step
Resource group not found Note in report, suggest creating it

Tool Requirements

This skill uses the following tools:

  • Azure CLI (az) - Version 2.76.0+ recommended for --validation-level
  • Azure Developer CLI (azd) - For projects with azure.yaml
  • Bicep CLI (bicep) - For syntax validation
  • Azure MCP Tools - For documentation lookups and best practices

Check tool availability before starting:

az --version
azd version
bicep --version

Example Workflow

  1. User: "Validate my Bicep deployment before I run it"
  2. Agent detects azure.yaml → azd project
  3. Agent finds infra/main.bicep and infra/main.bicepparam
  4. Agent runs bicep build infra/main.bicep --stdout
  5. Agent runs azd provision --preview
  6. Agent generates preflight-report.md in project root
  7. Agent summarizes findings to user

Reference Documentation

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 warning25d5 checks · Risk SAFE
  • Gen Agent Trust Hub25d

    This skill automates Azure infrastructure validation using official CLI tools. It is generally safe but carries a low risk of command injection through maliciously crafted file names and indirect prompt injection from the contents of the Bicep files it processes.

  • Socket25d

    No alerts

  • Snyk25d

    Risk: LOW · No issues

  • Runlayer9mo

    4/4 files flagged

  • ZeroLeaks7mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at f10fdb8. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 10 months ago
  • Infrastructure
  • azure
  • bicep
  • deployment
  • validation
  • what-if
  • azd
  • azure-cli
  • iac

README badge

README badge for github/awesome-copilot/azure-deployment-preflight

Validates Bicep deployments to Azure before execution, running syntax checks, what-if analysis, and permission verification across both Azure CLI and Azure Developer CLI workflows. Detects project type automatically, captures all issues in a structured preflight report, and handles permission fallbacks when RBAC access is limited.

Generated from the current SKILL.md.

Does this skill work with both Azure CLI and Azure Developer CLI?
Yes. The skill detects whether the project uses azd (by checking for azure.yaml) and runs azd provision --preview for azd projects, or az deployment what-if commands for standalone Bicep files.
What happens if I don't have permission to deploy?
The skill falls back from --validation-level Provider to ProviderNoRbac and notes the permission limitation in the report, so you can still see syntax errors and some validation results.
Does this actually deploy anything to Azure?
No. The skill uses what-if analysis and azd provision --preview, which preview changes without making them. No resources are created or modified.
What if Bicep CLI is not installed?
The skill skips the Bicep syntax check step but continues with Azure-side validation via what-if, which will catch syntax errors during the deployment preview.
Does this handle management group and tenant scope deployments?
Yes. The skill detects the targetScope declaration in the Bicep file and runs the appropriate what-if command for resourceGroup, subscription, managementGroup, or tenant scope.

Generated from the current SKILL.md. These answers refresh after source changes.