PluginBench
Skill
Official
Fail
Audit score 45

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 role assignments, and managed identity permissions before deployment. Use this after azure-prepare and before azure-deploy to ensure your app is deployment-ready.

  • Validates azure.yaml configuration and deployment plan
  • Checks Bicep and Terraform infrastructure code for correctness
  • Verifies RBAC role assignments and managed identity permissions
  • Runs recipe-specific validation commands (azd provision --preview, bicep build, terraform validate)
  • Builds the project and identifies errors before deployment
  • Records validation proof and results in deployment plan

How to install azure-validate

npx skills add https://github.com/microsoft/azure-skills --skill azure-validate
Prerequisites
  • azure-prepare skill must be invoked first and completed
  • `.azure/deployment-plan.md` must exist with status `Approved` or later
Claude Code
Cursor
Windsurf
Cline

How to use azure-validate

  1. 1.Read `.azure/deployment-plan.md` to load the deployment plan and recipe
  2. 2.Copy validation steps from the recipe into the deployment plan
  3. 3.Execute recipe-specific validation commands (bicep build, terraform validate, azd provision --preview, etc.)
  4. 4.Build the project and fix any compilation or configuration errors
  5. 5.Review Bicep/Terraform code for correct RBAC role assignments
  6. 6.Populate Section 7 of the deployment plan with validation commands run and their results
  7. 7.Fix any validation failures and re-run checks if needed
  8. 8.Set deployment plan status to `Validated` only after all checks pass

Use cases

Good for
  • Validate app readiness before deploying to Azure
  • Run preflight checks on Bicep or Terraform infrastructure
  • Verify RBAC roles and managed identity permissions are correctly configured
  • Troubleshoot deployment errors by running validation checks
  • Perform what-if analysis on Container Apps or Azure Functions deployments
Who it's for
  • DevOps engineers managing Azure deployments
  • Cloud architects validating infrastructure code
  • Developers checking deployment readiness before pushing to production
  • Teams using Azure Developer CLI (azd) workflows

azure-validate FAQ

What if azure-prepare hasn't been run yet?

Stop immediately and run azure-prepare first. The complete workflow is azure-prepare → azure-validate → azure-deploy. The deployment plan must exist with status `Approved` or later.

Can I deploy if validation checks fail?

No. All checks must pass before deployment. Fix the failures and re-run azure-validate until all checks pass, then set status to `Validated`.

What counts as validation proof?

Populate Section 7 of the deployment plan with the actual commands you ran (e.g., `bicep build`, `terraform validate`, `azd provision --preview`) and their results.

Should I run azd up or azd deploy directly?

No. After validation passes, invoke the azure-deploy skill to handle deployment execution. Do not run deployment commands directly.

What recipes are supported?

Validation steps are recipe-specific and defined in the recipes/README.md. Load your deployment plan to see which recipe and validation steps apply to your project.

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.1.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.md exists with status Approved or later

If the plan is missing, STOP IMMEDIATELY and invoke azure-prepare first.

The complete workflow ensures success:

azure-prepareazure-validateazure-deploy

Triggers

  • Check if app is ready to deploy
  • Validate azure.yaml or Bicep
  • Run preflight checks
  • Troubleshoot deployment errors

Rules

  1. Run after azure-prepare, before azure-deploy
  2. All checks must pass—do not deploy with failures
  3. Destructive actions require ask_userglobal-rules

Steps

#ActionReference
1Load Plan — Read .azure/deployment-plan.md for recipe and configuration. If missing → run azure-prepare first.azure/deployment-plan.md
2Add 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
3Run Validation — Execute recipe-specific validation commandsrecipes/README.md
4Build Verification — Build the project and fix any errors before proceedingSee recipe
5Static Role Verification — Review Bicep/Terraform for correct RBAC role assignments in coderole-verification.md
6Record Proof — Populate Section 7: Validation Proof with commands run and results.azure/deployment-plan.md
7Resolve Errors — Fix failures before proceedingSee recipe's errors.md
8Update Status — Only after ALL checks pass, set status to Validated.azure/deployment-plan.md
9Deploy — 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 to Validated:

  1. Run actual validation commands (azd provision --preview, bicep build, terraform validate, etc.)
  2. Populate Section 7: Validation Proof with the commands you ran and their results
  3. Only then set status to Validated

Do NOT set status to Validated without 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.