AutoGineer
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
Download ZIP

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://mp-staging.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/aspire-functions-secrets.md

Aspire + Azure Functions: Secret Storage Validation

⚠️ Pre-provisioning check — Run this BEFORE azd provision.

When This Applies

This check is required when all of these are true:

ConditionHow to detect
.NET Aspire project*.AppHost.csproj exists or Aspire.Hosting package reference
Azure Functions componentAddAzureFunctionsProject call in AppHost.cs or Program.cs
Identity-based storageWithHostStorage call (Aspire default)

Detection

Run the scan script — it finds *.cs files that call AddAzureFunctionsProject, checks whether each one already sets AzureWebJobsSecretStorageType, and prints a single verdict so you don't have to parse raw grep output.

Bash — scripts/scan-aspire-functions-secrets.sh:

./scripts/scan-aspire-functions-secrets.sh [directory]   # directory defaults to .

PowerShell — scripts/scan-aspire-functions-secrets.ps1:

.\scripts\scan-aspire-functions-secrets.ps1 [-Path <directory>]   # -Path defaults to .

The script prints one of three verdicts:

VerdictMeaningAction
NOT APPLICABLENo AddAzureFunctionsProject call foundSkip this check
ALREADY CONFIGUREDEvery matching file already sets AzureWebJobsSecretStorageTypeNo change required
FIX REQUIREDMatching file(s) call AddAzureFunctionsProject but omit the setting (file/line listed)Apply the Fix below to each listed file

Fix

Add .WithEnvironment("AzureWebJobsSecretStorageType", "Files") to the Azure Functions project builder chain in the AppHost source file that contains the AddAzureFunctionsProject call (often Program.cs in the *.AppHost project).

Before
var functions = builder.AddAzureFunctionsProject<Projects.MyFunctions>("functions")
    .WithHostStorage(storage)
    .WithReference(queues);
After
var functions = builder.AddAzureFunctionsProject<Projects.MyFunctions>("functions")
    .WithHostStorage(storage)
    .WithEnvironment("AzureWebJobsSecretStorageType", "Files")
    .WithReference(queues);

💡 Tip: Place .WithEnvironment(...) immediately after .WithHostStorage(...) for clarity.

Why This Is Required

Azure Functions needs storage for managing host secrets/keys (function keys, host keys, master key). By default, it stores them as blobs in the AzureWebJobsStorage account.

When Aspire configures identity-based storage access (via WithHostStorage), it sets URI-based environment variables like AzureWebJobsStorage__blobServiceUri instead of a connection string. The Functions runtime's secret manager does not support these identity-based URIs — it requires either a connection string or SAS token.

Setting AzureWebJobsSecretStorageType=Files switches the Functions host to file-system-based key storage, bypassing the blob storage dependency for secrets.

Error Without This Setting

System.InvalidOperationException: Secret initialization from Blob storage failed
due to missing both an Azure Storage connection string and a SAS connection URI.
For Blob Storage, please provide at least one of these.

When This Check Does NOT Apply

ScenarioWhy
Aspire project without Azure FunctionsNo Functions secret manager involved
Standalone Azure Functions (not Aspire)Uses connection string by default
Functions with explicit connection stringAzureWebJobsStorage is a full connection string, not identity-based
AzureWebJobsSecretStorageType already setConfiguration is already present

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.

Download ZIP

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