Overview
This guidance, supported and tested using SRE.Azure.com, helps Azure platform engineers understand how Availability Zones are mapped within their subscription and how virtual machines (VMs) are distributed across those zones.
SRE.Azure.com enables discovery and analysis of zone mappings, VM placement, and infrastructure resilience.
Why This Matters
Azure uses logical zones (1, 2, 3), but these map differently to physical datacenter zones (az1, az2, az3) in each subscription. This means workloads in the same logical zone across subscriptions may not be physically co-located.
Understanding this is critical for high availability, disaster recovery, compliance, and resilience planning.
Example
sub-prod-eastus-01 -> Zone 1 → az3
sub-prod-eastus-01 -> Zone 2 → az1
sub-prod-eastus-01 -> Zone 3 → az2
sub-prod-weu-01 -> Zone 1 → az1
sub-prod-weu-01 -> Zone 2 → az2
sub-prod-weu-01 -> Zone 3 → az3
Key takeaway: Logical zone numbers do not guarantee physical separation across subscriptions.
What SRE.Azure.com agent Enables
- Discover logical-to-physical zone mappings
- Analyze VM distribution across zones
- Identify resilience gaps
- Generate presentation-ready reports
Suggested Prompt
“Act as an Azure platform engineer and generate a clean, presentation-ready analysis for availability zone design.
For Azure subscription <subscription-id>, produce two outputs inline in chat.
Output 1 — Zone Mapping Summary
- Query Azure directly for region availability zone mappings
- Show how logical zones map to physical zones
- Include a takeaway and tables
Output 2 — VM Resilience Distribution
- List VMs with zone, physical mapping, and protection level
Formatting:
- Use markdown tables
- No raw JSON
- Screenshot-friendly layout
- End with 3 observations”
Example output:
And so on ……
Next Steps:
What is SRE Agent? | Azure SRE Agent