azure-deployment-preflight_skill

This skill validates and previews Azure Bicep deployments, detects syntax issues, permissions, and what-if results to prevent failures.

JavaScript
Official

19.4k

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill github/awesome-copilot --skill azure-deployment-preflight

SKILL.md7.3 KB

Overview

This skill performs comprehensive preflight validation for Bicep deployments to Azure. It inspects Bicep syntax, runs what-if analyses, detects project type (azd vs standalone), and checks deployment permissions. Use it to preview changes, surface errors and generate a concise preflight report before you run any deployment commands.

How this skill works

The skill detects whether the repository uses Azure Developer CLI (azure.yaml) or a standalone Bicep workflow, locates Bicep and parameter files, and runs a Bicep build for syntax validation. It then executes the appropriate preview/what-if commands (azd provision --preview or az deployment ... what-if) with provider validation, falls back to ProviderNoRbac on RBAC failures, and parses what-if output into categorized resource changes. Finally it compiles a timestamped preflight-report.md with tools executed, issues, what-if results, and recommendations.

When to use it

Before running azd up, azd provision, or az deployment commands
When preparing or reviewing Bicep files for production or CI
To preview and understand resource changes a deployment will make
When verifying that the executing identity has required deployment permissions
Before opening a PR that introduces infrastructure changes

Best practices

Run this skill from the project root so the report and file discovery are accurate
Provide resource group, subscription and location upfront or allow the skill to prompt for them
Keep parameter files next to their Bicep files using .bicepparam or parameters.json conventions
Treat ProviderNoRbac fallbacks as indicators of missing permissions and document remediation in the report
Capture and address all syntax errors and warnings before attempting a real deployment

Example use cases

Developer wants a safe preview of changes before running azd provision --preview
CI pipeline step that validates Bicep templates and fails the build on critical issues
Ops engineer verifying RBAC scope and permission gaps for a subscription-level deployment
Reviewer generating a preflight-report.md to include in a pull request for infrastructure changes

FAQ

The skill will note missing tools in the report, skip the step that requires them, and continue other validations where possible; install the missing CLI to run the skipped checks.

How does the skill handle permission errors during what-if?

If Provider validation fails with RBAC errors the skill retries with ProviderNoRbac, records the fallback, and lists recommended permission changes in the report.