trainer-demo-deploy: Skill for Claude Code

Azure Validate Skill

Pre-deployment and post-deployment validation gates that ensure Azure infrastructure is ready for deployment and correctly provisioned afterward. Used by the Deploy agent as hard gates before executing any deployment.

---

1. Pre-Deployment Validation Gates

All gates must pass before deployment proceeds. Each gate is a hard stop — failure means the deployment cannot continue until the issue is resolved.

[!CAUTION] GATE FAILURE POLICY: If a gate fails and cannot be auto-remediated, present the failure to the user and ask how to proceed. Do NOT autonomously skip deployment or generate a dry-run summary. The user must explicitly decide whether to:

1. Fix the issue and retry
2. Skip the gate (accepting risk)
3. Abort the deployment

Gate Sequence

Gate 1: Authentication    → az login / azd auth status
Gate 2: Subscription      → correct subscription selected
Gate 3: Template          → bicep build + bicep lint pass
Gate 4: Parameters        → required params have values
Gate 5: Resource Providers → all needed providers registered
Gate 6: What-If           → no unexpected destructive changes

---

2. Gate 1 — Authentication Check

Azure CLI

# Check if logged in
$account = az account show 2>$null | ConvertFrom-Json
if (-not $account) {
    Write-Error "Not authenticated. Run 'az login' first."
    exit 1
}
Write-Host "Authenticated as: $($account.user.name)"
Write-Host "Tenant: $($account.tenantId)"

Azure Developer CLI

# Check azd authentication
azd auth login --check-status

Expected Output

Field	Check
user.name or user.type	Non-empty; matches expected identity
tenantId	Matches the target tenant
state	Enabled

[!WARNING] Service principal authentication (user.type: "servicePrincipal") may have restricted permissions compared to interactive login. Verify RBAC before proceeding.