Skip to content
Azure Validate

Azure Validate Skill

Microsoft's official Azure skill for pre-deployment checks: validates azure.yaml, Bicep or Terraform, RBAC role assignments and managed identity permissions before an agent deploys.

GitHub Docs

Install

Install with the skills CLI

One command for Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf and dozens of other agents. Needs Node.js; the skill is fetched straight from microsoft/azure-skills.

$ npx skills add microsoft/azure-skills --skill azure-validate

Run it in a terminal. The CLI finds the agents installed on your machine, asks which ones to add the skill to, and whether to install it into the folder you ran it from or for all your projects.

Other ways to install

Copy the whole skill folder — SKILL.md and any scripts or references beside it — into ~/.claude/skills/azure-validate/, where Claude Code picks it up in every project. Only git is needed.

tmp=$(mktemp -d) && \
  git clone --depth 1 --branch main https://github.com/microsoft/azure-skills.git "$tmp" && \
  mkdir -p ~/.claude/skills && \
  cp -R "$tmp"/skills/azure-validate ~/.claude/skills/azure-validate

No scripts or references next to it? Saving the SKILL.md alone as ~/.claude/skills/azure-validate/SKILL.md works too.

Using another agent? Its personal skills folder
Codex
~/.agents/skills/
Cursor
~/.cursor/skills/
GitHub Copilot
~/.copilot/skills/
Gemini CLI
~/.gemini/skills/
Windsurf
~/.codeium/windsurf/skills/
OpenCode
~/.config/opencode/skills/

About

  • Pre-deployment checks for azure.yaml, Bicep and Terraform
  • Verifies RBAC role assignments and managed identity permissions
  • Step-by-step workflow script for PowerShell and Bash with saved progress
  • Requires an approved plan from Azure Prepare and blocks deploys on any failure
  • Destructive actions need explicit user confirmation
  • Hands off to Azure Deploy only when the user asked to deploy

Azure Validate is part of Microsoft's official Azure skills for coding agents (microsoft/azure-skills) and is the middle step of the prepare, validate, deploy workflow. It runs after Azure Prepare has produced an approved .azure/deployment-plan.md and before Azure Deploy, and it refuses to proceed if that plan is missing.

The skill runs deep readiness checks on a project before anything reaches Azure: configuration and azure.yaml, infrastructure written in Bicep or Terraform, RBAC role assignments, managed identity permissions and other prerequisites, with what-if analysis and troubleshooting for deployment errors. Its description lists Azure Functions and Container Apps deployments among the targets. The work is driven by a workflow script, in PowerShell for Windows or Bash for macOS and Linux, that walks the agent through one validation step at a time and records progress in .azure/validate-status.json; a Node.js runtime check applies to every recipe.

The rules are strict: every check must pass before deploying, destructive actions require asking the user, and only this skill may set the plan's status to Validated. Afterwards it hands off to Azure Deploy only if the user actually asked to deploy; if they only asked to validate, it stops and reports the results. MIT licensed, version 1.2.5.

SKILL.md

The instructions your agent loads, as published by Microsoft.

SKILL.md
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.2.5"

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
  1. Run after azure-prepare, before azure-deploy
  2. All checks must pass—do not deploy with failures
  3. ⛔ Destructive actions require `ask_user` — [global-rules](references/global-rules.md)
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](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:

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.

Read [references/recipes/README.md](references/recipes/README.md) and apply its Node.js runtime check for every recipe before provisioning or deployment. The steps also reference [role checks](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.
Install
New

Microsoft's official skill for preparing apps for Azure with the Azure Developer CLI: writes a deployment plan first, then generates azure.yaml, Bicep or Terraform infrastructure and Dockerfiles before handing off to validation.

Skill: Azure Deploy

by Microsoft

New

Microsoft's official skill for executing Azure deployments of already-prepared apps: it checks for a validated deployment plan, runs azd up, azd deploy, terraform apply or az deployment with error recovery, then verifies endpoints and RBAC roles.

New

Microsoft's official skill for Azure Blob Storage, File Shares, Queue and Table Storage and Data Lake: when to use each, access tiers, redundancy options, Azure MCP and az CLI commands, and SDK guides.

Browse all skills →