Azure Deployment Validator
Preflight Azure deployments by checking configuration, infrastructure, permissions, prerequisites, and builds.
The evidence requires azure-prepare first, ask_user confirmation for destructive, security, and cost-impacting actions, and confirmation of subscription and region. However, the workflow still runs azd, az, Docker, npm, and file/source modifications without explicit least-privilege guidance, sensitive-data handling, data-flow disclosure, rollback, or isolation of command results, so points are deducted.
The main workflow and AZD/AZCLI recipes are broadly consistent and include prerequisites, stop conditions, and some error guidance. Several referenced files are absent from the supplied material, while Bicep/Terraform/RBAC key paths lack reproducible skill-specific tests and comprehensive diagnostic feedback. Static review cannot establish executability, so the score remains within the static cap.
Triggers, AZD/AZCLI/Bicep/Terraform scenarios, Aspire conditions, and some skip cases are reasonably clear. Input/output contracts, non-fit boundaries, anti-misrouting conditions, and environment requirements remain incomplete, with no Chinese-language interaction or mainland-China reachability guidance, so points are deducted.
The skill provides a clear name and description, MIT license, author, version 1.1.2, and a layered main-document plus recipe/error-reference structure. It lacks a changelog, explicit maintenance responsibility, and update path; the supplied material also cannot confirm that all referenced files exist or are complete, so points are deducted.
The procedure covers plan loading, IaC compilation and validation, previews, builds, policy checks, RBAC review, and proof recording, making the core task actionable. However, it depends on external Azure credentials, subscriptions, and tools, provides no representative execution evidence for this skill, and mandates deployment after validation, expanding scope; therefore the static score is below the cap.
The documentation requires recording commands and results in Section 7, and the repository shows general CI and test infrastructure. The supplied evidence contains no dedicated azure-validate key-path tests, real execution results, or independent corroboration, so only limited static verifiability is justified.
- Validation invokes Azure CLI/MCP, reads subscription and resource information, and may modify the deployment plan, source files, environment variables, or generate package-lock.json; confirm scope, permissions, and backup/rollback before each change.
- The skill mandates invoking azure-deploy after all checks pass; deployment should not be assumed when the user requested validation only.
- Several referenced recipe, error, and RBAC files are not included in the supplied material, so reference completeness and actual command compatibility remain unverified.
What does this skill do, and when should you use it?
Azure Validate is a deployment-readiness skill in the azure-skills plugin from microsoft/skills. It requires azure-prepare to have completed and an approved .azure/deployment-plan.md to exist. The skill runs plan-specific checks for configuration, Bicep or Terraform, builds, RBAC assignments, managed identity permissions, and prerequisites, then records the evidence. Only after every check passes does it mark the plan Validated and hand execution to azure-deploy.
Reads .azure/deployment-plan.md; copies the recipe's validation steps into the plan; runs recipe-specific commands such as azd provision --preview, Bicep build, or terraform validate; builds the project and requires build errors to be fixed; reviews RBAC assignments in Bicep or Terraform; records commands and results in Section 7, Validation Proof; resolves failures and reruns validation; sets the plan status to Validated only after all checks pass; then invokes azure-deploy.
- An Azure engineer checks application and deployment configuration before provisioning resources.
- A team using Bicep or Terraform validates infrastructure definitions before deployment.
- An application team reviews RBAC assignments and managed identity permissions before release.
- A developer troubleshooting Azure Functions or Container Apps deployment errors runs preflight checks.
What are this skill's strengths and limitations?
- Covers configuration, infrastructure, build, RBAC, and managed identity checks before deployment.
- Requires concrete validation commands and results to be recorded as proof.
- Defines a clear prepare, validate, deploy workflow and blocks deployment after failures.
- Requires azure-prepare and an approved deployment plan before it can proceed.
- Does not deploy by itself; it depends on azure-deploy for execution.
- The source does not document detailed per-client installation paths, authentication setup, or complete test coverage for this individual skill.
How do you install this skill?
Install the repository collection with npx skills add microsoft/skills and select the needed skill in the wizard, or clone the repository and copy the relevant skill directory. The source does not document a complete standalone installation command for this skill in every client.
How do you use this skill?
First invoke and complete azure-prepare, ensuring .azure/deployment-plan.md exists with status Approved or later. Then use a request such as “check whether my Azure app is ready to deploy” or “validate my Bicep and run preflight checks.” Do not run deployment commands directly; after validation passes, let azure-deploy execute the deployment.