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…
Pre-deployment validation for Azure readiness with configuration, infrastructure, RBAC, and identity checks.
Runs recipe-specific validation commands including Bicep builds, Terraform validation, and Azure CLI preflight checks Verifies RBAC role assignments in infrastructure code and managed identity permissions before deployment Requires .azure/deployment-plan.md from azure-prepare skill; records validation proof and updates plan status to Validated only after all checks pass Integrates into the three-step workflow: azure-prepare → azure-validate → azure-deploy
Stronger alternatives
Audit results are mixed — compare nearby options before installing.
This skill provides a structured pre-deployment validation process for Azure infrastructure and configuration. It uses official command-line tools to ensure environments are correctly configured before deployment.
snykCRITICAL
Analyzed Apr 22, 2026
[CRITICAL] E004: Prompt injection detected in skill instructions.
socketScore 0.9000 · 0 alerts
Analyzed Apr 22, 2026
license1
maintenance1
quality0.9
supply chain1
vulnerability1
0 alerts
Also in this package
Other skills from microsoft/azure-skills · top by installs.
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](references/scripts/workflow.ps1) on Windows or [references/scripts/workflow.sh](references/scripts/workflow.sh) on macOS/Linux.
Start by calling the script without the completed-step argument:
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](references/recipes/README.md) and role checks in [references/role-verification.md](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 to Validated. Do NOT set status to Validated without 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.
