M365Con 2027 – free online conference · 11–22 Jan 2027 · 120 sessions m365con.net

Availability sets

Concept

An Azure feature that logically groups virtual machines inside one datacenter across fault domains and update domains so they do not all fail or restart together.

✦ CONCEPTAvailability setsM365.FM
Title graphic: Availability sets (Concept)

Also discussed

The episode about Availability sets also covers Availability zones.

Description

An availability set is a logical grouping of virtual machines in Microsoft Azure that lowers the chance of a correlated failure affecting all related machines at once. It works inside a single datacenter and is one of the older tools for building resilience into virtual machine workloads. The idea is simple: if several machines serve the same application, they should not all sit on the same power source, the same network switch, or the same maintenance schedule.

The mechanism relies on two kinds of domains. Fault domains are groups of hardware that share a power source and a network switch, so a hardware problem in one domain affects only the machines placed there. Update domains are groups of machines that can be restarted together during planned platform maintenance. When maintenance happens, only one update domain is restarted at a time, and the platform allows a recovery pause before moving on to the next one. Placing machines from the same application in different fault domains and update domains means that a single hardware fault or a single maintenance restart should not take down every instance.

Several constraints apply. The number of fault domains and update domains cannot be changed after the set is created, so the choice has to be made up front. For the platform's availability SLA to apply, a set needs at least two virtual machines. A managed availability set accepts only machines that use managed disks. There is no extra charge for the availability set itself beyond the cost of the virtual machines, and latency between machines can be lower than with availability zones, which is sometimes a reason to consider them.

The limits matter as much as the benefits. Availability sets do not protect against faults in the operating system or in the application running on the machines. They also remain exposed to some shared infrastructure outages in the datacenter, because all machines stay within one datacenter. Compared with availability zones, which place resources in separate physical locations within a region, availability sets give less resilience. For new designs, Microsoft Learn points to scale sets in flexible orchestration mode instead.

The M365.FM episode "Azure Availability Zones - Simply Explained" covers availability sets as "the older tool" within a broader walk through Azure resilience. The episode outline starts with regions and the idea of a region, then looks inside a region at availability zones and explains why one datacenter is not enough. It then places availability sets next to zonal versus zone-redundant services, and goes on to what SLAs actually mean, designing for resilience, region pairs, and the costs and trade-offs. The episode starts from the point that putting an app in the cloud does not by itself keep it running no matter what.

In practice, the decision around availability sets usually comes down to scope of protection. Spreading machines across fault and update domains addresses hardware faults and planned maintenance within one datacenter. If the requirement is to survive the loss of an entire datacenter, availability zones or other region-level designs are the relevant topics, as the episode's structure suggests. Availability sets therefore sit as a narrower, lower-level option under the broader Microsoft Azure resilience toolbox.

Overview compiled with AI from M365.FM episodes and the facts on this page. You can improve it with the edit button below.

TypeConcept
KindFeature

Episodes about Availability sets

Episodes in which Availability sets is discussed:

Frequently asked questions

Questions marked with AI were written with AI from the facts on this page.

What is an availability set in Azure? (AI)

An availability set is a logical grouping of virtual machines that spreads them across fault domains and update domains within one datacenter. This lowers the chance that a single hardware fault or maintenance restart affects all related machines at once.

What is the difference between fault domains and update domains? (AI)

Fault domains share a power source and network switch, so they represent hardware failure boundaries. Update domains are groups of machines that can be restarted together during planned maintenance, with only one update domain restarted at a time.

Do availability sets protect against everything? (AI)

No. They do not protect against operating system or application faults, they remain exposed to some shared infrastructure outages, and they offer less resilience than availability zones. For new designs, Microsoft Learn points to scale sets in flexible orchestration mode.

What is the difference between availability zones and availability sets?

A zone is a separate building, while an availability set spreads your machines across racks within one building. · From the episode: Azure Availability Zones - Simply Explained

What is a region pair?

A region pair is your backup city: a second region paired with the first, so that if a whole region is lost you have somewhere else to run. Zones and availability sets protect within a region, region pairs across regions. · From the episode: Azure Availability Zones - Simply Explained

Glossary

Community wiki

Short info above, community knowledge below: add practical tips, examples or corrections. New contributions are reviewed first; trusted members publish directly.

Experts and companies for this topic

Nobody has listed this topic yet. Add it to your profile.

Sources

Maintained by Mirko Peters (Microsoft MVP) · Last updated: