AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

azure-validate

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.

Original source
microsoft
License
MIT
Pinned revision
3f5b461b2314e01c400564051e92469114c5b68f

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

This skill also requires local files or dependencies. Remote reading alone may not be enough.

Ask your assistant

Use Agentic Memory skills to read microsoft--azure-validate at revision 3f5b461b2314e01c400564051e92469114c5b68f, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 17

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:

  1. project path exists and contains source files
  2. For framework apps: language: js is set
  3. dist is relative to project (not project root)
  4. Bicep has azd-service-name tag matching service name

Debug

azd <command> --debug