Azure Availability Zone, Available Set, Fault Domain

Last Updated on August 11, 2025 by Arnav Sharma

Azure Geographies and Regions

Azure offers a vast global infrastructure that is divided into geographies and regions. Each Azure geography contains one or more regions and is designed to meet specific data residency and compliance requirements. This structure ensures that business-critical data and applications are stored nearby on a fault-tolerant, high-capacity networking infrastructure.

Key Points:

1. Azure Geographies: Azure geographies are designed to cater to specific data residency and compliance needs. They allow businesses to keep their essential data and applications close, leveraging a robust networking infrastructure.
2. Azure Regions: Within these geographies, Azure has multiple regions. For instance, in the United States, there are regions like Central US, East US, West US, and more. Each region has specific features like availability zones, compliance offerings, data residency, disaster recovery options, and product availability.
3. Availability Zones: Some regions have availability zones, which are unique physical locations equipped with independent power, cooling, and networking. For example, the Central US region has availability zones with three zones available.
4. Data Residency: Azure ensures that data is stored at rest in specific locations. For the US regions mentioned, data is stored at rest in the United States.
5. Disaster Recovery: Azure offers cross-region options for disaster recovery, such as Azure Site Recovery and Region Pairing. There are also in-region options like Zonal DR with Azure Site Recovery.
6. Compliance: Azure provides compliance offerings for each region, ensuring that businesses meet the necessary regulatory and compliance requirements.

What are Azure Availability Zones?

Azure Availability Zones are a high-availability offering that protects applications and data from datacenter failures. These zones are essentially separate groups of datacenters within a region. They are close enough to maintain low-latency connections but are distanced sufficiently to minimize the chances of simultaneous outages due to local disruptions or adverse weather conditions.

Key Insights:

1. Definition and Purpose: Azure Availability Zones are distinct locations within an Azure region, each equipped with its own power, cooling, and networking to safeguard against datacenter failures. Their design ensures that if one zone faces an outage, the remaining zones can support regional services, capacity, and high availability.

2. Zonal and Zone-Redundant Services: Azure services can be deployed in two ways concerning availability zones:

   • Zonal Resources: These are pinned to a specific availability zone. Users can deploy across different zones for high reliability. In case of an outage in one zone, the user is responsible for failover to another zone.
   • Zone-Redundant Resources: These are spread across multiple availability zones. Microsoft handles the distribution of requests and data replication across zones. If one zone faces an outage, Microsoft automatically manages the failover.
3. Physical and Logical Zones: Each datacenter is linked to a physical zone. These physical zones are then mapped to logical zones in the Azure subscription. Different subscriptions might have varied mapping orders.
4. Updates and Availability Zones: Microsoft typically deploys updates to Azure services in one availability zone at a time. This strategy minimizes potential disruptions, allowing workloads in other zones to continue running during the update process.
5. Paired and Unpaired Regions: Some Azure regions have a paired region, supporting specific multi-region deployment strategies. Some newer regions, equipped with multiple availability zones, might not have a paired region.
6. Shared Responsibility Model: While Microsoft provides the infrastructure of availability zones and regions, users have a role in designing their solutions to meet specific requirements. Depending on the services used, the responsibility between Microsoft and the user varies.

Recommendations for Reliable Workloads:

• Production workloads should utilize availability zones if supported in their region.
• For mission-critical tasks, consider a solution that spans both multiple regions and multiple zones.

Understanding Fault Domains

Fault domains play a crucial role in ensuring high availability and fault tolerance in modern IT infrastructures. They are a foundational concept in Microsoft’s Failover Clustering, which enables multiple servers to work in tandem to provide high availability.

Key Insights:

1. Definition of Fault Domains: A fault domain is a collection of hardware components that share a single point of failure. For a system to be fault-tolerant at a particular level, it requires multiple fault domains at that level. For instance, to achieve rack fault tolerance, servers and data must be distributed across multiple racks.
2. Fault Tolerance and Failover Clustering: Failover Clustering in Windows Server 2016 introduced chassis, rack, and site fault tolerance. This means that the system can withstand failures at the chassis, rack, or even site level, ensuring high availability even in the face of significant disruptions.

3. Fault Domain Awareness in Windows Server 2019: While fault domain awareness is available in Windows Server 2019, it is disabled by default. It can be enabled through the Windows Registry, allowing for more granular control over fault domains.

4. Benefits of Fault Domains: Storage Spaces, a feature in Windows, uses fault domains to maximize data safety. By distributing data across multiple fault domains, Storage Spaces can ensure data resiliency, even if one domain fails. Additionally, the Health Service uses fault domains to provide more precise alerts, and stretch clustering leverages fault domains for storage affinity.

5. Levels of Fault Domains: There are four primary levels of fault domains: site, rack, chassis, and node. While nodes are discovered automatically, the other levels are optional and can be defined based on the specific deployment.
6. Defining Fault Domains: Fault domains can be defined using PowerShell or XML markup. PowerShell offers cmdlets like Get-ClusterFaultDomain, Set-ClusterFaultDomain, and New-ClusterFaultDomain to manage fault domains. Alternatively, an XML-inspired syntax can be used to specify fault domains, offering flexibility in defining the physical topology of a deployment.

Azure Availability Sets

Azure Availability Sets are a crucial feature that ensures the high availability of Azure Virtual Machines (VMs). They are designed to minimize the impact of failures, be it due to hardware, network, or power interruptions.

Key Insights:

1. Definition of Availability Sets: Availability sets are logical groupings of VMs that aim to reduce the likelihood of correlated failures affecting related VMs simultaneously. By placing VMs in different fault domains, availability sets enhance reliability, especially in regions that don’t support availability zones.

2. How Availability Sets Work: Each VM within an availability set is assigned both an update domain and a fault domain by Azure. An availability set can have up to 3 fault domains and 20 update domains. Update domains indicate groups of VMs that can be rebooted simultaneously. Fault domains, on the other hand, define groups of VMs that share a common power source and network switch. This separation ensures that potential physical hardware failures, network outages, or power interruptions impact only a subset of the VMs.

3. Benefits of Availability Sets: VMs within an availability set are located in closer proximity, resulting in improved VM-to-VM latencies compared to availability zones. They provide fault isolation for various possible failures, minimizing single points of failure and ensuring high availability. However, they are still vulnerable to certain shared infrastructure failures, such as datacenter network failures.
4. Comparison with Availability Zones: While availability sets offer high availability, availability zones provide even greater reliability. In availability zones, each VM is deployed across multiple datacenters, safeguarding against the loss of power, networking, or cooling in any single datacenter.
5. Cost Implications: There’s no additional cost for using availability sets. Users only pay for each VM instance they create.
6. Recommendation: Microsoft recommends using virtual machine scale sets with flexible orchestration mode for high availability combined with a broad range of features. While availability sets offer high availability, virtual machine scale sets provide centralized management, configuration, and updating of VM instances, adjusting the number of VM instances based on demand or a defined schedule.

Update Domain Vs Fault Domain in Azure

In the realm of Azure, understanding the fundamental differences between update domains and fault domains is crucial for ensuring high availability and redundancy for critical servers. This understanding is especially vital when leveraging Azure’s Availability Sets, which allow for the logical grouping of VMs to provide highly available applications.

Key Insights:

1. Availability Sets: Before diving into update and fault domains, it’s essential to grasp the concept of Availability Sets. These sets allow for region-based redundancy and availability for critical servers. By creating two or more VMs within an availability set, users can ensure highly available applications and meet Azure’s SLA of 99.95%. Notably, while the Availability Set feature is free, users only pay for the compute resources they use.

2. Update Domains: Update domains represent groups of VMs and their underlying physical hardware that can be rebooted simultaneously. This is typically done for maintenance activities initiated by Azure, such as driver updates or underlying platform patch updates. For instance, if more than five VMs are configured within a single availability set with five update domains, the sixth VM will be placed in the same update domain as the first VM, and so on. During planned maintenance, the rebooting of update domains may not be sequential, but only one is rebooted at a time. Each rebooted update domain gets 30 minutes to recover before maintenance starts on another update domain.

3. Fault Domains: Fault domains, on the other hand, define groups of VMs that share a common power source and network switch. By default, VMs within an availability set are spread across up to three fault domains. This distribution ensures that potential physical hardware failures, network outages, or power interruptions have a limited impact on the system.