Setting the file. One moment.
Chapter 23 · Azure Reliability
Subchapter 23.12
references/zone-redundancy-checks.mdMarkdown3 KBView on GitHub
Zone redundancy distributes compute instances across availability zones within a region. If one zone fails, instances in other zones continue serving traffic automatically.
This file covers platform-level discovery and concepts. For service-specific assessment queries, configuration commands, and IaC patches, see:
| Service | Reference |
|---|---|
| Azure App Service | services/app-service/reliability.md |
| Azure Functions | services/functions/reliability.md |
Azure Container Apps deep-dive references are planned for a future version of this skill. The discovery query below still surfaces those resources — just don’t dispatch to a per-service reference for them yet.
⚠️ Output format: Use
--query "data[]" -o jsonforaz graph query.-o tableonly renders summary columns (Count,Total_records) and hides projected fields. Pipe JSON throughjqif you need a table view.
Use this single query to discover every compute resource in scope that is not zone-redundant. Use it during Phase 1 (Discover Resources) to decide which service references to load.
az graph query -q "
Resources
| where type in~ ('microsoft.web/serverfarms', 'microsoft.app/managedenvironments')
| extend zoneRedundant = tobool(properties.zoneRedundant)
| where zoneRedundant == false or isnull(zoneRedundant)
| project name, type, resourceGroup, location, sku=sku.name
| order by type asc
" --query "data[]" -o jsonFor each row in the result, dispatch to the matching service reference:
microsoft.web/serverfarms with kind contains 'functionapp' → Functions referencemicrosoft.web/serverfarms (other kinds) → App Service referencemicrosoft.app/managedenvironments → planned (Container Apps) — surface in the discovery summary, do not deep-diveaz functionapp list-flexconsumption-locations --zone-redundant=trueCommon regions with AZ support across Functions, App Service, and Container Apps:
Service-specific region availability differs. Always confirm support for the specific SKU/plan in the target region using the per-service reference.
For the assessment table’s Zone redundancy — compute row, the per-service references define exactly what 🟢 ON / 🟡 PARTIAL / 🔴 OFF mean for that service (e.g. ZR + minimum instance count for App Service, Premium Functions). Only App Service and Functions have a per-service reference in this skill version; Container Apps support is planned.