This chapter covers Availability Sets, a resiliency feature for virtual machines that's distinct from Availability Zones. AZ-900 tests this under objective 2.1, alongside the Availability Zones and Region Pairs chapter.
Jump to a section
A simple way to picture Availability Sets
If you're moving eggs to a new house, you'd avoid putting them all in one basket (so dropping one basket doesn't break everything), and you might also avoid sending them all in a single delivery truck (so one truck breaking down doesn't strand the whole shipment). Availability Sets apply both ideas to virtual machines: they spread VMs across separate hardware (so one hardware failure doesn't take all of them down) and stagger their updates (so a maintenance event doesn't restart all of them at once).
What an Availability Set is
An Availability Set is a logical grouping of virtual machines that Azure distributes across separate physical hardware within a single datacenter, to reduce the chance that a single hardware failure or maintenance event takes down every VM in the group at once.
Fault domains
A fault domain represents a group of underlying hardware (server rack, power source, network) sharing a common point of failure. VMs in an Availability Set are spread across multiple fault domains, so a failure affecting one fault domain doesn't affect VMs in the others.
Update domains
An update domain represents a group of VMs that can be rebooted together during planned maintenance. VMs in an Availability Set are spread across multiple update domains, so Azure doesn't restart every VM in the set simultaneously during a maintenance event — some remain available while others are updated.
How Availability Sets differ from Availability Zones
Availability Sets distribute VMs across separate hardware *within a single datacenter*. Availability Zones (covered in their own chapter) distribute resources across physically separate datacenters *within a region* — a larger-scale form of separation. Availability Sets protect against a rack- or hardware-level failure; Availability Zones protect against an entire datacenter-level failure. Depending on the scenario and what's available in a given region, an architecture might use one, the other, or in some cases both together.
Group related VMs into an Availability Set
VMs performing the same role (for example, web servers behind a load balancer) are placed in the same Availability Set.
Azure distributes them across fault domains
Azure automatically spreads the VMs across multiple fault domains to reduce shared hardware failure risk.
Azure distributes them across update domains
Azure automatically spreads the VMs across multiple update domains so planned maintenance doesn't restart them all simultaneously.
A company runs three identical web server VMs behind a load balancer, placing them in an Availability Set so a single rack-level hardware failure or a planned maintenance event doesn't take down all three simultaneously — at least one keeps serving traffic.
Objective 2.1 expects candidates to distinguish Availability Sets (hardware-level separation within one datacenter, via fault and update domains) from Availability Zones (separation across physically distinct datacenters within a region).
A common wrong answer is confusing Availability Sets with Availability Zones — they operate at different scales and solve related but distinct problems.
Stable terms: Availability Set, fault domain, update domain. Memory trick: fault domain = shared hardware failure risk; update domain = shared maintenance-reboot timing. Availability Sets spread VMs across both.
An Availability Set spreads VMs across separate hardware (fault domains) and staggers maintenance reboots (update domains) within a single datacenter.
This is distinct from Availability Zones, which separate resources across physically distinct datacenters within a region.
Availability Sets protect against rack/hardware-level failures; Availability Zones protect against datacenter-level failures.
These come up on the exam all the time. Here's how to tell them apart.
Availability Set
Separates VMs across hardware within one datacenter
Uses fault domains and update domains
Availability Zone
Separates resources across distinct datacenters in a region
A larger-scale, physically separate form of resiliency
Mistake
Availability Sets and Availability Zones are the same feature.
Correct
Availability Sets separate VMs across hardware within a single datacenter; Availability Zones separate resources across physically distinct datacenters within a region — a larger-scale form of separation.
A logical grouping of VMs that Azure spreads across separate hardware (fault domains) and staggers for maintenance (update domains) within a single datacenter, reducing the chance a single failure or maintenance event affects every VM at once.
A fault domain is a group of hardware sharing a common failure point (like a rack or power source). An update domain is a group of VMs rebooted together during planned maintenance. Availability Sets spread VMs across both.
You've just covered Availability Sets — now see how well it sticks with free AZ-900 practice questions. Full explanations included, no account needed.
Done with this chapter?