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

Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/microsoft/azure-validate/download

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

Run after azure-prepare, before azure-deploy
All checks must pass—do not deploy with failures
⛔ 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

ATTRIBUTION.mdAdded by AutoGineer974 B
LICENSELicence file added by AutoGineer1.1 KiB
SKILL.md3.5 KiB
references/aspire-functions-secrets.md3.7 KiB
references/global-rules.md1.2 KiB
references/policy-validation.md1.5 KiB
references/recipes/README.md374 B
references/recipes/azcli/README.md2.7 KiB
references/recipes/azcli/errors.md505 B
references/recipes/azd/README.md5.3 KiB
references/recipes/azd/aspire.md1.7 KiB
references/recipes/azd/environment.md1.9 KiB
references/recipes/azd/errors.md2.6 KiB
references/recipes/azd/scripts/set-aspire-aca-env.ps1Script3.5 KiB
references/recipes/azd/scripts/set-aspire-aca-env.shScript3.6 KiB
references/recipes/bicep/README.md2.5 KiB
references/recipes/bicep/errors.md374 B
references/recipes/scripts/validate-deployment.ps1Script5.2 KiB
references/recipes/scripts/validate-deployment.shScript6.1 KiB
references/recipes/terraform/README.md3.9 KiB
references/recipes/terraform/errors.md2.8 KiB
references/recipes/terraform/scripts/validate-terraform.ps1Script6.8 KiB
references/recipes/terraform/scripts/validate-terraform.shScript6.6 KiB
references/region-availability.md3.0 KiB
references/role-verification.md3.9 KiB
references/scripts/scan-aspire-functions-secrets.ps1Script3.0 KiB
references/scripts/scan-aspire-functions-secrets.shScript3.3 KiB
references/scripts/workflow.ps1Script5.2 KiB
references/scripts/workflow.shScript5.7 KiB

references/role-verification.md

Role Assignment Verification

Verify that all RBAC role assignments in the generated infrastructure are correct and sufficient before deployment. Incorrect or missing roles are a common cause of runtime failures.

When to Verify

After build verification (step 4) and before recording proof (step 6). Role issues surface as cryptic auth errors during deployment — catching them here saves debugging time.

Verification Checklist

Review every resource-to-identity relationship in the generated Bicep/Terraform:

Check	How
Every service identity has roles	Each app with a managed identity must have at least one role assignment
Roles match data operations	Use service-specific data-plane roles for data access (see mapping table below); use generic Reader/Contributor/Owner only for management-plane operations
Scope is least privilege	Roles scoped to specific resources, not resource groups or subscriptions
No missing roles	Cross-check app code operations against assigned roles (see table below)
Local dev identity has roles	If testing locally, the user's identity needs equivalent roles via `az login`

Common Service-to-Role Mapping

Service Operation	Required Role	Common Mistake
Read blobs	Storage Blob Data Reader	Using generic Reader (no data access)
Read + write blobs	Storage Blob Data Contributor	Missing write permission
Generate SAS via user delegation	Storage Blob Delegator + Data Reader/Contributor	Forgetting Delegator role
Read Key Vault secrets	Key Vault Secrets User	Using Key Vault Reader (no secret access)
Read + write Cosmos DB	Cosmos DB Built-in Data Contributor	Using generic Contributor
Send Service Bus messages	Azure Service Bus Data Sender	Using generic Contributor
Read queues	Storage Queue Data Reader	Using Blob role for queues

How to Verify (Static Code Review)

Review the generated Bicep/Terraform files directly — do not query live Azure state here. For each role assignment resource in your infrastructure code:

Identify the principal (which managed identity)
Identify the role (which role definition)
Identify the scope (which target resource)
Cross-check against the app code to confirm the role grants the required data-plane access

💡 Tip: Search your Bicep for Microsoft.Authorization/roleAssignments or your Terraform for azurerm_role_assignment to find all role assignments.

⚠️ Live role verification (querying Azure for actually provisioned roles) is handled by azure-deploy step 8 as a post-deployment check. This step is a static code review only.

Decision Tree

For each app identity in the generated infrastructure:
├── Has role assignments?
│   ├── No → Add required role assignments to Bicep/Terraform
│   └── Yes → Check each role:
│       ├── Role matches code operations? → ✅ OK
│       ├── Role too broad? → Narrow to least privilege
│       └── Role insufficient? → Upgrade or add missing role
│
For local testing:
├── User identity has equivalent roles?
│   ├── No → Grant roles via CLI or inform user
│   └── Yes → ✅ Ready for functional verification

⚠️ Warning: Generic roles like Contributor or Reader do not include data-plane access. For example, Contributor on a Storage Account cannot read blobs — you need Storage Blob Data Contributor. This is the most common RBAC mistake.

Record in Plan

After role verification, update .azure/deployment-plan.md:

## Role Assignment Verification
- Status: Verified / Issues Found
- Identities checked: <list of app identities>
- Roles confirmed: <list of role assignments>
- Issues: <any missing or incorrect roles fixed>

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

2026-11-08

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

From the author

AutoGineer summary

What it does

When to use it

Advantages

Usage examples

Install

Documentation by Microsoft

Azure Validate

Triggers

Rules

Steps

Files

references/role-verification.md

Role Assignment Verification

When to Verify

Verification Checklist

Common Service-to-Role Mapping

How to Verify (Static Code Review)

Decision Tree

Record in Plan

Requirements and compatibility

Security

Attribution and licence

Related skills

Modal

Cloud Infrastructure Network Engineer

Deployment Validation Cloud Architect

Airflow Dag Patterns

Cost Optimization

Hybrid Cloud Networking

Download ZIP