Generated banner for Azure Validate
Generated logo for Azure Validate

Azure Validate

MicrosoftOfficialCreated by Microsoft

  • Skill
  • Workflow
  • Cloud and DevOps
  • MIT
  • Low risk
  • Has scripts

From the author

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.
— the description by Microsoft

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

The azure-validate skill provides a structured, step-by-step workflow to ensure Azure readiness before deployment. It performs deep checks on infrastructure definitions (Bicep or Terraform), RBAC role assignments, managed identity permissions, and other prerequisites. This skill is designed to be used as the second step in a three-part deployment process: azure-prepare, azure-validate, and azure-deploy. It uses a script-based approach to guide the user through validation steps, tracking progress in a local JSON file to ensure all requirements are met before allowing a deployment to proceed.

What it does

  • Validates infrastructure configurations including Bicep and Terraform files.
  • Verifies RBAC role assignments and managed identity permissions.
  • Runs preflight checks to ensure environment readiness.
  • Tracks validation progress through a structured, multi-step script.
  • Ensures all prerequisites are met before deployment can occur.
  • Provides a mechanism to troubleshoot common deployment errors.

When to use it

  • Before executing an Azure deployment to ensure all configurations are correct.
  • When troubleshooting deployment errors to identify configuration or permission issues.
  • After completing the azure-prepare step to verify the deployment plan.
  • When you need to confirm that RBAC and managed identity settings are correctly configured.

Advantages

  • Prevents deployment failures by catching configuration issues early.
  • Ensures consistent and repeatable validation processes.
  • Integrates seamlessly into a standard deployment workflow.
  • Provides clear, actionable feedback on validation status.

Usage examples

“Validate my Azure deployment readiness.”
The agent initiates the azure-validate workflow script, guiding you through the necessary checks for your infrastructure and permissions.
“Check if my Bicep files are ready for deployment.”
The agent runs the validation script against your Bicep files and reports any configuration errors or missing prerequisites.

Install

  1. Download the skill as a ZIP:

    https://autogineer.com/agent-skills/microsoft/azure-validate/download
  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip azure-validate.zip -d .agents/skills

Documentation by Microsoft

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

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:

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.

The steps reference recipe details in references/recipes/README.md and role checks in 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.

Files

references/scripts/workflow.sh

#!/usr/bin/env bash
# workflow.sh
# Walks the agent through the azure-validate workflow, one step at a time.
#
# Usage:
#   ./workflow.sh --workspace-path <path> [--completed-step <step>]
#
# Options:
#   --workspace-path <path>    Path to the workspace being validated (required).
#   --completed-step <step>    The workflow step the agent just completed. Omit
#                              on the first call to start the workflow. The
#                              script records the value in
#                              .azure/validate-status.json and returns the next
#                              action to take, along with the value to pass as
#                              --completed-step on the next call.
#
# Exit codes:
#   0 - next action emitted (or workflow complete)
#   2 - usage / argument error (missing workspace path or invalid step)

set -uo pipefail

# Valid workflow steps, in order.
VALID_STEPS=(None LoadPlan AddValidationSteps RunValidation BuildVerification \
    StaticRoleVerification RecordProof ResolveErrors UpdateStatus)

# Ensure an option that consumes a value actually has one ($@ = remaining args).
need_val() {
    [ "$#" -ge 2 ] || { echo "ERROR: $1 requires a value." >&2; exit 2; }
}

WORKSPACE_PATH=""
COMPLETED_STEP=""

while [ $# -gt 0 ]; do
    case "$1" in
        --workspace-path) need_val "$@"; WORKSPACE_PATH="$2"; shift 2 ;;
        --completed-step) need_val "$@"; COMPLETED_STEP="$2"; shift 2 ;;
        -h|--help)
            grep '^#' "$0" | grep -v '^#!' | sed 's/^# \{0,1\}//'
            exit 0 ;;
        *)
            echo "Unknown argument: $1" >&2
            exit 2 ;;
    esac
done

if [ -z "$WORKSPACE_PATH" ]; then
    echo "ERROR: --workspace-path is required." >&2
    exit 2
fi

if [ ! -d "$WORKSPACE_PATH" ]; then
    echo "Error: --workspace-path '$WORKSPACE_PATH' does not exist or is not a directory." >&2
    exit 2
fi

# Resolve the step the agent just completed (case-insensitive).
# Omitting --completed-step signals the start of the workflow (None).
STEP="None"
if [ -n "$COMPLETED_STEP" ]; then
    STEP=""
    for valid in "${VALID_STEPS[@]}"; do
        if [ "$(printf '%s' "$COMPLETED_STEP" | tr '[:upper:]' '[:lower:]')" = \
             "$(printf '%s' "$valid" | tr '[:upper:]' '[:lower:]')" ]; then
            STEP="$valid"
            break
        fi
    done
    if [ -z "$STEP" ]; then
        printf 'Error: '\''--completed-step %s'\'' is not a valid step. Valid values: %s\n' \
            "$COMPLETED_STEP" "$(printf '%s, ' "${VALID_STEPS[@]}" | sed 's/, $//')" >&2
        exit 2
    fi
fi

# Record progress in .azure/validate-status.json (creating it if needed).
AZURE_DIR="$WORKSPACE_PATH/.azure"
mkdir -p "$AZURE_DIR"
VALIDATE_STATUS_PATH="$AZURE_DIR/validate-status.json"
printf '{\n  "completedStep": "%s"\n}\n' "$STEP" > "$VALIDATE_STATUS_PATH"

# Emit the next action based on the step just completed.
case "$STEP" in
    None)
        # Step 1: Load Plan
        echo "Action: Read \`.azure/deployment-plan.md\` for recipe and configuration. If missing, run azure-prepare first, then come back to workflow.sh."
        echo "Next: re-run workflow.sh with --completed-step LoadPlan after completing the action."
        echo "Reference: \`.azure/deployment-plan.md"
        ;;
    LoadPlan)
        # Step 2: Add Validation Steps
        echo "Action: Copy the recipe's \`Validation Steps\` into \`.azure/deployment-plan.md\` as children of \`All validation checks pass\`."
        echo "Next: re-run workflow.sh with --completed-step AddValidationSteps after completing the action."
        echo "Reference: references/recipes/README.md, \`.azure/deployment-plan.md"
        ;;
    AddValidationSteps)
        # Step 3: Run Validation
        echo "Action: Execute the recipe-specific validation commands."
        echo "Next: re-run workflow.sh with --completed-step RunValidation after completing the action."
        echo "Reference: references/recipes/README.md"
        ;;
    RunValidation)
        # Step 4: Build Verification
        echo "Action: Build the project and fix any errors before proceeding."
        echo "Next: re-run workflow.sh with --completed-step BuildVerification after completing the action."
        echo "Reference: See the recipe for build details."
        ;;
    BuildVerification)
        # Step 5: Static Role Verification
        echo "Action: Review the Bicep/Terraform for correct RBAC role assignments in code."
        echo "Next: re-run workflow.sh with --completed-step StaticRoleVerification after completing the action."
        echo "Reference: references/role-verification.md"
        ;;
    StaticRoleVerification)
        # Step 6: Record Proof
        echo "Action: Populate **Section 7: Validation Proof** in the plan with the commands run and their results."
        echo "Next: re-run workflow.sh with --completed-step RecordProof after completing the action."
        echo "Reference: \`.azure/deployment-plan.md"
        ;;
    RecordProof)
        # Step 7: Resolve Errors
        echo "Action: Fix any validation failures before proceeding."
        echo "Next: re-run workflow.sh with --completed-step ResolveErrors after completing the action."
        echo "Reference: See the recipe's errors.md."
        ;;
    ResolveErrors)
        # Step 8: Update Status
        echo "Action: Only after ALL checks pass, set the plan status to \`Validated\`."
        echo "Next: re-run workflow.sh with --completed-step UpdateStatus after completing the action."
        echo "Reference: \`.azure/deployment-plan.md"
        ;;
    UpdateStatus)
        # Step 9: Deploy (workflow complete)
        echo "Action: The azure-validate workflow is complete. If the user explicitly requested deployment, invoke azure-deploy. Otherwise STOP and report the validation results."
        ;;
esac

exit 0

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Security

What our scanner noticed· Low risk

  • Scripts that your agent may run

This skill includes scripts that your agent may run. Read them before you use it.

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Created by
Microsoft
Publisher
Microsoft (Official)
Source
microsoft/skills · .github/plugins/azure-skills/skills/azure-validate · commit 0696600
Licence
MIT License (redistribution allowed)
  • LICENSE (added by AutoGineer from .github/plugins/azure-skills/LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced
Also distributed in
microsoft/azure-skills

AutoGineer is not affiliated with or endorsed by Microsoft or Microsoft.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download azure-validate.zip