Azure Validate
MicrosoftOfficialCreated by Microsoft
- Skill
- Workflow
- Cloud and DevOps
- MIT
- Low risk
- Has scripts
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://autogineer.com/agent-skills/microsoft/azure-validate/downloadUnzip 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.mdexists with statusApprovedor laterIf 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 toValidated. Do NOT set status toValidatedwithout 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/recipes/azd/errors.md
AZD Validation Errors
Pre-Deployment Errors
These errors can be caught before running azd up:
| Error | Cause | Resolution |
|---|---|---|
Please run 'az login' | Not authenticated | az login or azd auth login |
No environment selected | Missing azd environment | azd env select <name> or azd env new <name> --no-prompt |
no default response for prompt 'Enter a unique environment name' | No azd environment created, or missing -e flag | Run azd env new <name> --no-prompt OR use azd init --from-code -e <name> --no-prompt with the -e flag |
no default response for prompt 'Enter a value for the 'environmentName' | Environment variables not set | Run azd env set AZURE_ENV_NAME <name> |
Service not found | Service name mismatch | Check service name in azure.yaml |
Invalid azure.yaml | YAML syntax error | Fix YAML syntax |
Project path does not exist | Wrong service project path | Fix service project path in azure.yaml |
Cannot connect to Docker daemon | Docker not running | Start Docker Desktop |
npm ci fails with missing: package-lock.json | Dockerfile uses npm ci but package-lock.json not in build context | Run npm install --package-lock-only in the service directory before building |
Could not find a part of the path 'infra\main.bicep' | Missing infrastructure files | Generate infra/ folder before azd up |
Invalid resource group location '<loc>'. The Resource group already exists in location '<other>' | RG exists in different region | Check RG location first with az group show, use that region or new env name |
expecting only '1' resource tagged with 'azd-service-name: web', but found '2' | Multiple resources with same tag in the same RG | Delete duplicate or rename service |
Static Web App Errors
| Error | Cause | Fix |
|---|---|---|
language 'html' is not supported | Invalid language value | Omit language for pure static sites |
language 'static' is not supported | Invalid language value | Omit language for pure static sites |
dist folder not found | Wrong dist path or missing build | Check dist is relative to project; add language: js if build needed |
LocationNotAvailableForResourceType | SWA not in region | See Region Availability for valid regions |
SWA Path Validation
Before deployment, verify:
projectpath exists and contains source filesFor framework apps:
language: jsis setdistis relative toproject(not project root)Bicep has
azd-service-nametag matching service name
Debug
azd <command> --debugRequirements 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