azure-validate
microsoft/azure-skills
Pre-deployment validation for Azure readiness with configuration, infrastructure, and RBAC checks.
What is azure-validate?
Runs deep validation checks on Azure configuration, Bicep/Terraform infrastructure, RBAC roles, managed identities, and prerequisites before deployment. Use this after azure-prepare and before azure-deploy to ensure your app is deployment-ready and catch issues early.
- Validates azure.yaml configuration and deployment plan status
- Checks Bicep and Terraform infrastructure code
- Verifies RBAC role assignments and managed identity permissions
- Runs preflight checks and prerequisite validation
- Performs what-if analysis to preview deployment impact
- Records validation progress and status in .azure/validate-status.json
How to install azure-validate
npx skills add https://github.com/microsoft/azure-skills --skill azure-validate- azure-prepare skill must be invoked first and .azure/deployment-plan.md must exist with status 'Approved' or later
- Azure CLI or Azure PowerShell installed and authenticated
- Bicep CLI (if validating Bicep templates) or Terraform (if validating Terraform)
How to use azure-validate
- 1.Run the workflow script for your OS: `pwsh references/scripts/workflow.ps1 -WorkspacePath <workspace-path>` (Windows) or `bash references/scripts/workflow.sh --workspace-path <workspace-path>` (macOS/Linux)
- 2.Follow the script's instructions for each validation step
- 3.Perform the action indicated by the script output
- 4.Re-run the script with the completed-step argument: `-CompletedStep <value>` (pwsh) or `--completed-step <value>` (bash)
- 5.Repeat until the script reports azure-validate workflow is complete
- 6.Review validation results in .azure/validate-status.json
- 7.If all checks pass and user requested deployment, invoke azure-deploy; otherwise stop and report results
Use cases
- Verify your app is ready to deploy before running azure-deploy
- Troubleshoot deployment errors by identifying configuration issues
- Validate Azure Functions, Container Apps, or serverless deployments
- Check if all required RBAC roles are assigned to your managed identity
- Run preflight checks to catch infrastructure problems early
- Azure developers preparing applications for deployment
- DevOps engineers validating infrastructure-as-code before production
- Teams using the azure-prepare → azure-validate → azure-deploy workflow
- Anyone troubleshooting Azure deployment failures
azure-validate FAQ
Fix the identified issues in your configuration, infrastructure, or RBAC setup, then re-run azure-validate before proceeding to deployment.
No. You must follow the workflow: azure-prepare → azure-validate → azure-deploy. Do not run azd up or azd deploy directly.
Stop immediately and invoke azure-prepare first. The skill will not proceed without .azure/deployment-plan.md with status 'Approved' or later.
No. It only validates readiness. If validation passes and the user requested deployment, it invokes azure-deploy to handle the actual deployment.
Validation progress and results are recorded in .azure/validate-status.json, which tracks each completed step and the final validation status.
Full instructions (SKILL.md)
Source of truth, from microsoft/azure-skills.
name: azure-validate description: "Pre-deployment validation for Azure readiness. Run deep checks on configuration, infrastructure (Bicep or Terraform), RBAC role assignments, managed identity permissions, and prerequisites before deploying. WHEN: validate my app, check deployment readiness, run preflight checks, verify configuration, check if ready to deploy, validate azure.yaml, validate Bicep, test before deploying, troubleshoot deployment errors, validate Azure Functions, validate function app, validate serverless deployment, verify RBAC roles, check role assignments, review managed identity permissions, what-if analysis, validate Container Apps deployment." license: MIT metadata: author: Microsoft version: "1.2.2"
Azure Validate
AUTHORITATIVE 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
Triggers
- Check if app is ready to deploy
- Validate azure.yaml or Bicep
- Run preflight checks
- Troubleshoot deployment errors
Rules
- Run after azure-prepare, before azure-deploy
- All checks must pass—do not deploy with failures
- ⛔ Destructive actions require
ask_user— global-rules
Steps
Run the workflow script and follow its instructions. It walks you through each validation step one at a time, recording progress in .azure/validate-status.json. Use references/scripts/workflow.ps1 on Windows or references/scripts/workflow.sh on macOS/Linux.
Start by calling the script without the completed-step argument:
pwsh references/scripts/workflow.ps1 -WorkspacePath <workspace-path>
# macOS/Linux: bash references/scripts/workflow.sh --workspace-path <workspace-path>
Each run prints the next action and the value to pass next. Perform the action, then re-run with that value (-CompletedStep <value> for pwsh, --completed-step <value> for bash). Repeat until it reports the azure-validate workflow is complete.
The steps reference recipe details in references/recipes/README.md and role checks in references/role-verification.md.
⛔ VALIDATION AUTHORITY
This skill is the officially verified way to set plan status to
Validated. You MUST follow the script's instructions to completion before setting status toValidated. Do NOT set status toValidatedwithout doing so.
⚠️ NEXT STEP — DEPENDS ON USER INTENT
After ALL validations pass, check whether the user asked to deploy:
- If the user explicitly requested deployment, you MUST invoke azure-deploy to execute it. Do NOT run
azd up,azd deploy, or any deployment commands directly — let azure-deploy handle execution.- If the user only asked to validate or prepare (not deploy), STOP after recording proof and setting status to
Validated. Report the validation results and do NOT invoke azure-deploy.If any validation failed, fix the issues and re-run azure-validate before proceeding.
Related skills
More from microsoft/azure-skills and the wider catalog.
