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/bicep/README.md

Bicep Validation

Validation steps for standalone Bicep deployments.

Prerequisites

  • ./infra/main.bicep exists
  • ./infra/main.parameters.json exists
  • Azure CLI authenticated

Validation Steps

  • [ ] 1. Core Validation (CLI, auth, build, validate, what-if) — run validate-deployment script
  • [ ] 2. Linting (optional)
  • [ ] 3. Azure Policy Validation

Validation Details

1. Core Validation Script

The core validation checks are a fixed, deterministic sequence — identical to the AZCLI recipe. Run the shared validate-deployment helper instead of executing and parsing each command by hand. It confirms the Azure CLI is installed and authenticated, compiles the Bicep template (az bicep build), validates it against the target scope (az deployment ... validate), and runs a what-if preview — printing a compact PASS/FAIL summary plus a what-if change count (Create/Modify/Delete).

Subscription scope:

../scripts/validate-deployment.sh --scope sub --location <location>
../scripts/validate-deployment.ps1 -Scope sub -Location <location>

Resource group scope:

../scripts/validate-deployment.sh --scope group --resource-group <rg-name>
../scripts/validate-deployment.ps1 -Scope group -ResourceGroup <rg-name>

Defaults: --template ./infra/main.bicep, --parameters ./infra/main.parameters.json (skipped if absent). Pass --subscription <id> to target a specific subscription.

Interpreting results:

  • OVERALL: PASS — all checks passed; record the summary in Section 7 (Validation Proof).
  • Any step FAIL — the script prints the failing command's error. If Authenticated fails, run az login. Otherwise see Error handling.

2. Linting (optional)

Use Bicep linter rules:

az bicep lint --file ./infra/main.bicep

3. Azure Policy Validation

See Policy Validation Guide for instructions on retrieving and validating Azure policies for your subscription.

Checklist

| Check | Command | Pass | |-------|---------|------| | Core validation (CLI, auth, build, validate, what-if) | validate-deployment script | ☐ | | Policies validated | MCP Policy tool | ☐ |

References

Next

All checks pass → azure-deploy