Regions, region pairs, availability zones and datacentres

Geography, region, zone, datacentre

A geography is a market with its own data-residency and compliance boundary — the sort of line a regulator draws — and it contains at least two regions. A region is a group of datacentres close enough together to be treated as one place: Azure picks the boundary so that traffic between them stays inside a tight latency budget, and joins them with a network of its own. When you create almost anything in Azure, the region is the first question you are asked, and it is a decision that is awkward to reverse.

Inside a region, an availability zone is one or more datacentres with independent power, cooling and networking, far enough apart that the same flood or the same substation failure is unlikely to reach two of them. A region that offers zones offers at least three, which is what makes a quorum-based design possible without leaving the region at all. Two spellings are worth keeping apart: a ZONAL resource is pinned to one named zone, and a ZONE-REDUNDANT one is spread across several by the platform without you placing it.

Below that, and easy to miss, is the availability set — which is not a geography level but a placement instruction inside a single datacentre. Azure spreads a set's members across fault domains, which are groups sharing a power supply and a top-of-rack switch, and across update domains, which are rebooted in turn during planned host maintenance. That covers a broken rack and a maintenance window. It does not cover the building, which is exactly the distinction the exam is built on.

Region pairs: distance, and updates one side at a time

Every region is paired with another by Microsoft, and you do not choose the partner — you choose only whether to use an option that replicates to it. The pair buys two things. The first is distance: the two are several hundred miles apart wherever the geography allows, so a single flood, fire or grid failure is unlikely to reach both. The second is staged maintenance: planned platform updates go to one region of a pair at a time, so a faulty rollout cannot land on your primary and your recovery target in the same window.

A pair normally sits inside the same geography, and that is not trivia — it is what keeps a data-residency commitment intact after a failover. Brazil South is the exception everybody is taught, because its partner lies in another geography. The other property worth remembering is that cross-region replication is asynchronous, because the distance that makes the pair useful is the same distance that makes a synchronous write impossible.

Sovereign regions are a different cloud, not a special label

Azure Government in the United States and Azure operated by 21Vianet in China are separate instances of Azure with their own regions, their own portals, their own service endpoints and their own operations staff. A subscription in the commercial cloud cannot simply reach across into one of them. When a requirement says physically and logically isolated from commercial tenants, or names a government accreditation, the answer is a sovereign cloud — not a region, not a zone, and certainly not a resource group.

Region choice is a design input, not a formality

Regions are not interchangeable. Availability zones, individual services, individual virtual machine sizes and prices all vary between them, which is why "we will pick the region later" produces a design that cannot be built. The four inputs to weigh are data residency and sovereignty, latency to the people and systems that will use it, whether every service and size the design needs is actually offered there, and cost.

The consequence worth internalising: when a region turns out not to offer a capability the design assumed, there is no switch to flip. Zones in particular are a property of the region, so the only honest options are to deploy somewhere that has them or to knowingly drop the requirement — and a question offering to enable zones in a region that lacks them is offering something that does not exist.