azure-deployment-preflight

Validate Azure Bicep/ARM templates and clear stale failed deployments before CI.

1|Updated Jun 24, 2026
One-click install
npx skills add https://github.com/eric-sabe/engsys --skill azure-deployment-preflight-eric-sabe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: azure-deployment-preflight
Source: https://github.com/eric-sabe/engsys/tree/main/stacks/cloud/azure/skills/azure-deployment-preflight
Command: npx skills add https://github.com/eric-sabe/engsys --skill azure-deployment-preflight-eric-sabe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the costly cycle of pushing Azure infrastructure changes, waiting 15-30 minutes for CI to run, and discovering preventable deployment errors that could have been caught locally.

Core Features & Use Cases

  • Multi-workflow validation: Supports both standalone az CLI and azd project deployment workflows for Bicep/ARM templates.
  • Blocking state cleanup: Automatically identifies and removes stale failed ARM deployment records that block new deployment attempts.
  • Edge case detection: Catches globally unique resource naming conflicts, SKU/tier incompatibilities (e.g., PgBouncer on Burstable VMs), and hard-to-spot Bicep template gotchas like incorrect alert module locations or KQL interpolation issues.
  • Use Case: A cloud engineer preparing to deploy a new Azure PostgreSQL Flexible Server can run this Skill to validate their Bicep template, confirm no naming conflicts exist for their Key Vault, and verify their chosen VM SKU supports PgBouncer before pushing, avoiding a failed CI run and 30 minute wait.

Quick Start

Use the azure-deployment-preflight skill to validate your Azure Bicep deployment template, clear any stale failed deployment state, and confirm all naming and SKU requirements are met before pushing your changes to CI.

Frequently Asked Questions about azure-deployment-preflight

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate Azure Bicep templates locally before pushing to CI?

Preflight validation catches Bicep template errors, stale failed ARM deployment records, globally unique naming conflicts, and SKU or tier incompatibilities before CI runs. This eliminates the 15-30 minute wait cycle for preventable Azure infrastructure deployment failures.

How do I clear stale failed ARM deployment records blocking new deployments?

Clearing stale failed ARM deployment records requires identifying and removing blocking deployment states automatically. Preflight validation workflows handle this cleanup to ensure new Azure infrastructure deployment attempts are not blocked by previous failures.

Can I use preflight validation with both az CLI and azd project deployment workflows?

Preflight validation supports both standalone az CLI and azd project deployment workflows for Azure infrastructure. It handles Bicep and ARM template validation across both deployment methods.

Why does my Azure PostgreSQL Flexible Server deployment fail with PgBouncer on Burstable VMs?

Azure PostgreSQL Flexible Server deployments fail with PgBouncer on Burstable VMs due to SKU and tier incompatibilities. Preflight validation catches these specific VM SKU constraints and Bicep template gotchas before pushing changes to CI.

How do I check for globally unique resource naming conflicts in Bicep templates?

Checking for globally unique resource naming conflicts in Bicep templates is handled by preflight validation workflows. They detect naming conflicts for resources like Key Vault before deployment, preventing CI run failures caused by duplicate names.

What Bicep template gotchas should I check before deploying Azure infrastructure?

Bicep template gotchas to check before deploying Azure infrastructure include incorrect alert module locations and KQL interpolation issues. Preflight validation catches these hard-to-spot errors alongside syntax validation and deployment what-if previews.