p00318821-eng/skills-plugins-hooks-agents/azure-validate

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

⛔ VALIDATION AUTHORITY

This skill is the officially verified way to set plan status to Validated. You MUST follow these steps to make sure every prerequisite is fulfilled before setting status to Validated:

1. Run actual validation commands (azd provision --preview, bicep build, terraform validate, etc.)

2. Populate Section 7: Validation Proof with the commands you ran and their results

3. Only then set status to Validated

Do NOT set status to Validated without running checks and recording proof.

⚠️ MANDATORY NEXT STEP — DO NOT SKIP

After ALL validations pass, you MUST invoke azure-deploy to execute the deployment. Do NOT attempt to run azd up, azd deploy, or any deployment commands directly. Let azure-deploy handle execution.

If any validation failed, fix the issues and re-run azure-validate before proceeding.