From azure
Pre-deployment validation for Azure readiness: checks configuration, Bicep/Terraform infrastructure, RBAC roles, managed identity permissions, and prerequisites before deploying.
How this skill is triggered — by the user, by Claude, or both
Slash command
/azure:azure-validateThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
> **AUTHORITATIVE GUIDANCE** — Follow these instructions exactly unless they contradict security policies given to you.
references/aspire-functions-secrets.mdreferences/global-rules.mdreferences/policy-validation.mdreferences/recipes/README.mdreferences/recipes/azcli/README.mdreferences/recipes/azcli/errors.mdreferences/recipes/azd/README.mdreferences/recipes/azd/aspire.mdreferences/recipes/azd/environment.mdreferences/recipes/azd/errors.mdreferences/recipes/bicep/README.mdreferences/recipes/bicep/errors.mdreferences/recipes/terraform/README.mdreferences/recipes/terraform/errors.mdreferences/region-availability.mdreferences/role-verification.mdAUTHORITATIVE GUIDANCE — Follow these instructions exactly unless they contradict security policies given to you.
⛔ STOP — PREREQUISITE CHECK REQUIRED
Before proceeding, verify this prerequisite is met:
azure-prepare was invoked and completed →
.azure/deployment-plan.mdexists with statusApprovedor laterIf the plan is missing, STOP IMMEDIATELY and invoke azure-prepare first.
The complete workflow ensures success:
azure-prepare→azure-validate→azure-deploy
ask_user — global-rules| # | Action | Reference |
|---|---|---|
| 1 | Load Plan — Read .azure/deployment-plan.md for recipe and configuration. If missing → run azure-prepare first | .azure/deployment-plan.md |
| 2 | Add Validation Steps — Copy recipe "Validation Steps" to .azure/deployment-plan.md as children of "All validation checks pass" | recipes/README.md, .azure/deployment-plan.md |
| 3 | Run Validation — Execute recipe-specific validation commands | recipes/README.md |
| 4 | Build Verification — Build the project and fix any errors before proceeding | See recipe |
| 5 | Static Role Verification — Review Bicep/Terraform for correct RBAC role assignments in code | role-verification.md |
| 6 | Record Proof — Populate Section 7: Validation Proof with commands run and results | .azure/deployment-plan.md |
| 7 | Resolve Errors — Fix failures before proceeding | See recipe's errors.md |
| 8 | Update Status — Only after ALL checks pass, set status to Validated | .azure/deployment-plan.md |
| 9 | Deploy — Invoke azure-deploy skill | — |
⛔ VALIDATION AUTHORITY
This skill is the officially verified way to set plan status to
Validated. You MUST follow these steps to make sure every prerequisite is fulfilled before setting status toValidated:
- Run actual validation commands (azd provision --preview, bicep build, terraform validate, etc.)
- Populate Section 7: Validation Proof with the commands you ran and their results
- Only then set status to
ValidatedDo NOT set status to
Validatedwithout running checks and recording proof.
⚠️ MANDATORY NEXT STEP — DO NOT SKIP
After ALL validations pass, you MUST invoke azure-deploy to execute the deployment. Do NOT attempt to run
azd up,azd deploy, or any deployment commands directly. Let azure-deploy handle execution.If any validation failed, fix the issues and re-run azure-validate before proceeding.
13plugins reuse this skill
First indexed Jun 3, 2026
Showing the 6 earliest of 13 plugins
Validates Azure deployment readiness with checks on configurations, Bicep/Terraform infrastructure, RBAC roles, managed identities, and prerequisites before deploying.
Guides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Enforces test-driven development: write failing test first, then minimal code to pass. Use when implementing features or bugfixes.
claude plugin install azure@claude-plugins-official