How do I install the Microsoft Azure Validate skill?

Run npx skillmds@latest add pyfagorass/microsoft-azure-validate in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Microsoft Azure Validate safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Microsoft Azure Validate?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Microsoft Azure Validate free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Microsoft Azure Validate?

pyfagorass (@pyfagorass) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Microsoft Azure Validate by pyfagorass

Name: Microsoft Azure Validate
Author: pyfagorass

Microsoft Azure Validate

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.

pyfagorass 83080c8 17 files · 41.0 KB Updated Sep 17, 2026

File contents

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-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

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

Run actual validation commands (azd provision --preview, bicep build, terraform validate, etc.)

Populate Section 7: Validation Proof with the commands you ran and their results

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.

---name: microsoft-azure-validatedescription: 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---# 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-prepare` → `azure-validate` → `azure-deploy`## Triggers- Check if app is ready to deploy- Validate azure.yaml or Bicep- Run preflight checks- Troubleshoot deployment errors## Rules1. Run after azure-prepare, before azure-deploy2. All checks must pass—do not deploy with failures3. ⛔ **Destructive actions require `ask_user`** — [global-rules](references/global-rules.md)## Steps| # | Action | Reference ||---|--------|-----------|| 1 | **Load Plan** — Read `.azure/deployment-plan.md` for recipe and configuration. If missing → run azure-prepare first | `.azure/deployment-plan.md` || 2 | **Add Validation Steps** — Copy recipe "Validation Steps" to `.azure/deployment-plan.md` as children of "All validation checks pass" | [recipes/README.md](references/recipes/README.md), `.azure/deployment-plan.md` || 3 | **Run Validation** — Execute recipe-specific validation commands | [recipes/README.md](references/recipes/README.md) || 4 | **Build Verification** — Build the project and fix any errors before proceeding | See recipe || 5 | **Static Role Verification** — Review Bicep/Terraform for correct RBAC role assignments in code | [role-verification.md](references/role-verification.md) || 6 | **Record Proof** — Populate **Section 7: Validation Proof** with commands run and results | `.azure/deployment-plan.md` || 7 | **Resolve Errors** — Fix failures before proceeding | See recipe's `errors.md` || 8 | **Update Status** — Only after ALL checks pass, set status to `Validated` | `.azure/deployment-plan.md` || 9 | **Deploy** — 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.

Frequently asked questions