Azure validate skill
Pre-deployment validation for Azure readiness.
by microsoft·MIT license·★ 3,077 Stars on the repo·GitHub ↗
npx degit microsoft/skills/.github/plugins/azure-skills/skills/azure-validate#main ~/.claude/skills/azure-validateChecked ·commit main
Files of Azure validate
Show the full text68 lines
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.
| 1 | |
| 2 | name azure-validate |
| 3 | 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." |
| 4 | license MIT |
| 5 | metadata |
| 6 | author Microsoft |
| 7 | version "1.2.3" |
| 8 | |
| 9 | |
| 10 | # Azure Validate |
| 11 | |
| 12 | > **AUTHORITATIVE GUIDANCE** — Follow these instructions exactly unless they contradict security policies given to you. |
| 13 | |
| 14 | > **⛔ STOP — PREREQUISITE CHECK REQUIRED** |
| 15 | > |
| 16 | > Before proceeding, verify this prerequisite is met: |
| 17 | > |
| 18 | > **azure-prepare** was invoked and completed → `.azure/deployment-plan.md` exists with status `Approved` or later |
| 19 | > |
| 20 | > If the plan is missing, **STOP IMMEDIATELY** and invoke **azure-prepare** first. |
| 21 | > |
| 22 | > The complete workflow ensures success: |
| 23 | > |
| 24 | > `azure-prepare` → `azure-validate` → `azure-deploy` |
| 25 | |
| 26 | ## Triggers |
| 27 | |
| 28 | Check if app is ready to deploy |
| 29 | Validate azure.yaml or Bicep |
| 30 | Run preflight checks |
| 31 | Troubleshoot deployment errors |
| 32 | |
| 33 | ## Rules |
| 34 | |
| 35 | Run after azure-prepare, before azure-deploy |
| 36 | All checks must pass—do not deploy with failures |
| 37 | ⛔ **Destructive actions require `ask_user`** — [global-rules] |
| 38 | |
| 39 | ## Steps |
| 40 | |
| 41 | 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. |
| 42 | |
| 43 | Start by calling the script **without** the completed-step argument: |
| 44 | |
| 45 | |
| 46 | pwsh references/scripts/workflow.ps1 -WorkspacePath <workspace-path> |
| 47 | # macOS/Linux: bash references/scripts/workflow.sh --workspace-path <workspace-path> |
| 48 | |
| 49 | |
| 50 | 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. |
| 51 | |
| 52 | The steps reference recipe details in [references/recipes/README.md] and role checks in [references/role-verification.md]. |
| 53 | |
| 54 | > **⛔ VALIDATION AUTHORITY** |
| 55 | > |
| 56 | > 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`. |
| 57 | > Do NOT set status to `Validated` without doing so. |
| 58 | |
| 59 | |
| 60 | |
| 61 | > **⚠️ NEXT STEP — DEPENDS ON USER INTENT** |
| 62 | > |
| 63 | > After ALL validations pass, check whether the user asked to deploy: |
| 64 | > - **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. |
| 65 | > - **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. |
| 66 | > |
| 67 | > If any validation failed, fix the issues and re-run azure-validate before proceeding. |
| 68 |
Discussion
Alternatives
Docker MCP gatewayDocker's own CLI plugin: run any server from the Docker MCP Catalog in its own container, behind one connection, with secrets kept out of env vars.Azure cloud migrateAssess and migrate cross-cloud workloads to Azure with reports and code conversion. Supports Lambda→Functions, Beanstalk/Heroku/App Engine→App Service, Fargate/Kubernetes/Cloud Run/Spring Boot→Container Apps. WHEN: migrate Lambda to Functions, AWS to Azure, migrate Beanstalk, migrate Heroku, migrate App Engine, Cloud Run migration, Fargate to ACA, ECS/Kubernetes/GKE/EKS to Container Apps, Spring Boot to Container Apps, cross-cloud migration.Browse more free Claude skills or everything in Development.