Regions and zones

A region is several separate buildings, so that one can fail

Region: West EuropeZone 1own power and coolingVMZone 2own power and coolingVMZone 3own power and coolingVM✗Datacentrea building full of serversAvailability zoneone or more datacentres,physically apart from the restRegionthe zones of one area, joinedby a fast private networkPut a copy of the application in each zone and it survives the loss of a whole datacentre.A region with availability zones has at least three of them. Each can fail without taking the others down, andthey are close enough to copy data between them almost instantly. Not every region has zones, and a virtualmachine sits in the one zone you choose, so the spreading is your job.

A region holds three or more availability zones, each with its own power, cooling and network.

Regions and zones · Going deeper

How services use zones

Kind of serviceWhat it does with zonesExamplesZonalYou pin the resource to one zone you chooseVirtual machines, managed disks, IP addressesZone-redundantAzure copies it across zones for youZone-redundant storage, SQL DatabaseNon-regionalNot tied to a region at all; survives a regional outageMicrosoft Entra ID, Azure DNS, the portalOne VM, one datacentreA fault in that building stops itAvailability setCopies on different racks of one datacentre: survives a rack or an updateAvailability zonesCopies in different zones: survives a whole datacentreTwo regionsCopies in a region pair: survives a regional disasterEach step down this list protects against a bigger failure, and costs more to run.

Zonal services are pinned to a zone. Zone-redundant services are spread for you.

Region pairs

Each region has a distant partner in the same geography

North EuropeIrelandzone 1zone 2zone 3West EuropeNetherlandszone 1zone 2zone 3300 miles or more apart, where possiblegeo-redundant storage copies acrossupdates reach one region at a timeafter a wide outage, one is restored firstA region pair is two regions in the same geography, far enough apart that one disaster cannot hit both.Most regions have a fixed partner. Data copied to the pair stays inside the same geography, which matters forresidency rules. Some services use the pair automatically; for most, you choose to deploy to the second region.A few pairs work in one direction only, and some newer regions rely on availability zones and have no pair.

A region pair is two regions at least 300 miles apart where possible, in one geography.

Region pairs · Going deeper

Sovereign regions, and choosing a region

Sovereign regions: separate copies of AzureAzure GovernmentFor United States government bodies and their partners; run by screened US personsAzure operated by 21VianetRegions in China, run by 21Vianet and not by MicrosoftChoosing a regionDistance to usersNearer means lower latencyLaw and residencySome data must stay inside a country or geographyServices offeredNot every service, or virtual machine size, is in every regionPriceThe same service can cost more in one region than anotherZones and pairCheck the region has availability zones, and where its pair isA sovereign region is isolated from the public regions: separate sign-in, separate datacentres.

Sovereign regions are isolated copies of Azure for a government or a country.

Check yourself

RegionZone 1Zone 2Zone 3VMVM

Both copies of an application are placed as shown. Which single failure stops the application?

The hierarchy

Resources sit in groups, groups in subscriptions

Root management groupProductionNon-productionSalesHRDevelopmentrg-webrg-datarg-payrollrg-testVMdiskSQLappVMManagement groupsSubscriptionsResource groupsResourcesEvery resource is in one resource group, every group in one subscription. The tree has no exceptions.Build it from the bottom. A resource is one thing you created. A resource group is a folder for resources thatlive and die together. A subscription is the unit of billing and access. Management groups collect subscriptionsso one rule can cover many of them.

Resource, resource group, subscription, management group: each sits inside exactly one of the next.

The hierarchy · Going deeper

What to know about each level

LevelWhat to knowResourceAnything you create: a virtual machine, a database, a virtual network, a diskResource groupA resource is in exactly one. Groups cannot be nested. Delete the group and everything in it goesThe group has a region, but that is only where its record is kept; its resources can be anywhereSubscriptionA billing boundary (one bill) and an access boundary. An account can have manySplit them by environment, by department for billing, or to get past a limit on one subscriptionManagement groupHolds subscriptions and other management groups, up to six levels deep under the rootEach group and subscription has exactly one parent. A directory can have 10,000 management groupsResources move between resource groups and subscriptions; they never sit in two at once.Limits as documented on Microsoft Learn, checked November 2026.

Groups cannot be nested. Deleting a group deletes its resources. A subscription is a billing boundary.

Inheritance

A setting flows down the tree, never sideways

Root management groupProductionNon-productionSalesHRDevelopmentrg-webrg-datarg-payrollrg-testVMdiskSQLappVMManagement groupsSubscriptionsResource groupsResourcespolicy set hererole given hereWhatever you set at one level applies to everything beneath it, and to nothing beside it.The purple policy was assigned once, to the Production management group, and reaches both subscriptions andevery resource under them. The green role was given on one resource group and reaches only its resources.This is true of Azure Policy, of role-based access control and of resource locks alike.

A policy, role or lock set at one level is inherited by everything beneath it.

Inheritance · Going deeper

Choosing the scope

The four scopesManagement groupone rule for many subscriptionsSubscriptionone rule for a whole environment or billResource groupone rule for one applicationResourceone rule for one thingAssign as high as the rule truly applies, and no higher.A policy that every company resource must meet belongs on a management group. A lock that protects onedatabase belongs on that database or its resource group. A setting lower down cannot remove what wasinherited from above; to make an exception you change it at the level where it was set.

There are four scopes. Assign as high as the rule applies, and no higher.

Check yourself

Subscription A ★Subscription Brg-1rg-2rg-3VMVMVMVMVM

A resource lock is placed on the subscription marked with a star. How many of the resources shown does it protect?

Two addresses

Where a resource runs and who owns it are separate questions

Where it runsGeography: EuropeRegion: West EuropeAvailability zone 2Who owns and paysManagement group: ProductionSubscription: SalesResource group: rg-webOne virtual machinevm-web-01the two do not depend on each otherEvery resource has two addresses: a place on the map, and a place in the tree.The region decides latency, law and what survives a failure. The resource group and subscription decide whomay touch it, which rules apply and whose bill it is on. A resource group in West Europe can hold a resource inEast US, and moving a resource to another group does not move it on the map.

The region is where it runs. The resource group and subscription are who owns and pays.

Two addresses · Going deeper

Clue words for architecture

When the question saysThe service isBecause it"survive a datacentre failure in the region"Availability zonesseparate buildings, one region"survive a regional disaster"A region pair (a second region)far apart, same geography"US government", "compliance isolation"Azure Governmenta sovereign region"logical container", "same lifecycle"Resource groupdelete together"separate bills", "billing boundary"Subscriptionone bill each"apply to many subscriptions at once"Management groupabove subscriptions"where a rule is applied"Scopeand it is inherited downward"lowest latency for users in ..."The nearest regiondistance is delay"data must remain in the country"A region in that geographyresidencyZones answer a building failing. Pairs answer a region failing. The tree answers who and whose bill.

Zones answer a building failing, pairs a region failing, the tree who and whose bill.

Check yourself

rg-shop · group's own region: West EuropeVMWest EuropeStorageNorth EuropeSQLEast US

The resource group shown is deleted. What happens to the three resources?

Lesson complete

You finished “Regions, zones and the Azure resource hierarchy”

Answer the questions along the way to see your score here.

Open in a new tab