C✳CODEZ.WIN
🌐 English

Localized reading guide

azure-validatePurpose, usage and source

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.

Source retrieved:

Source repository
microsoft/skills
SKILL.md
.github/plugins/azure-skills/skills/azure-validate/SKILL.md
Repository stars
3,157
Repository updated
2026-10-31
Categories
Cloud
Last collected

License: License file needs review

Workflow excerpts are reading aids, not executable instructions from Codez. No third-party Skill was run to produce this page.

The purpose and workflow passages below are upstream material, organized and translated for reading. They are distinct from the separately labeled Codez editorial analysis.

What this Skill does

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.

How the upstream workflow works

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: Each run prints the next action and the value to pass next. Perform the action, then re-run with that value (-CompletedStep for pwsh, --completed-step 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.

Upstream passage · L39 ↗

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

Upstream passage · L10 ↗

Triggers

Check if app is ready to deploy Validate azure.yaml or Bicep

Upstream passage · L26 ↗
Upstream passage · bash ↗
pwsh references/scripts/workflow.ps1 -WorkspacePath <workspace-path>
# macOS/Linux: bash references/scripts/workflow.sh --workspace-path <workspace-path>

Requirements and setup

No short requirements passage was selected from this file. This does not mean the Skill has no dependencies. Check the repository setup instructions and referenced files.

Limits and quality checks

No separate limits passage was selected from this file. This does not mean the Skill is safe for every input or environment. Review the complete source and validate your own result.

Start with a safe trial

  1. Check the supported host and the repository installation instructions. Keep the Skill directory and its referenced scripts, assets and documentation together; SKILL.md alone may omit dependencies.
  2. Give the agent your real input, desired output and acceptance criteria. Invocation syntax and available tools depend on the host; this site does not assume a universal install command.
  3. Try the source workflow in a disposable project or on a copy. Review operations that change files, remote services or billable resources before allowing them.
  4. Validate the output against the source quality checks and your own requirements. A successful trigger or a high repository Star count does not establish a correct result.

Skill format and directory specification ↗

Read further in the source

Translation and scope

This reading guide selects passages from the pinned upstream SKILL.md. Translation is assisted. It is not a complete manual or a claim of tested compatibility. Read the original and its referenced files before use.

This introduction refers to the pinned version below; current repository activity and collection time are shown separately.

Source retrieved
Source commit
41138f3cb4825d1ba9812d35358d5513be08c20e
Source SHA-256
53648cbaa1653cdc6860cfa55eaac8e0b8ea925a94d594971b935e9ad9d1b4a4
Back to the full Skill catalog