Regions, Availability Zones & Indian Regions

By the end of this lesson you will be able to explain regions, availability zones and region pairs, name the Azure regions in India with their CLI names, and choose a sensible region for a project. Where your app runs affects its speed, its cost, its legal position and how it survives failures.

Regions

A region is a set of data centres in one geographic area, connected by a fast, low-latency network. Azure has dozens of public regions around the world, and new ones open every year. Each region has a display name, such as "Central India", and a programmatic name used in the CLI and templates, such as centralindia.

Think of a region like a city that has several bank branches. Your account is opened in one city, and your money stays there unless you choose to move it. In the same way, a resource you create in Central India stays in Central India unless you copy it somewhere else.

Regions are grouped into geographies, such as India, Europe or the United States. A geography is a market that usually matches a country's data residency and compliance boundary.

Azure regions in India

Microsoft's official regions list (checked in November 2026) shows four regions in the India geography:

Central India is the usual first choice for new projects, because it has availability zones and the widest range of services. India South Central in Hyderabad is the newest Indian region and also has three zones. Not every service is available in every region, so check before you design. The Azure regions list is the place to confirm today's details.

Step by step: list regions with the CLI

Step 1: list the Indian regions your subscription can see. The --query option uses JMESPath, a small query language for JSON, to filter and reshape the reply.

az account list-locations \
  --query "[?metadata.geography=='India'].{Name:name, City:metadata.physicalLocation}" \
  --output table

Name               City
-----------------  ---------
centralindia       Pune
indiasouthcentral  Hyderabad
southindia         Chennai
westindia          Mumbai

This output is traced from the documented shape of az account list-locations. Your list may contain more rows or a different order.

Step 2: look at one region in full JSON to see the extra metadata, such as the paired region.

az account list-locations --query "[?name=='centralindia'].{name:name, pair:metadata.pairedRegion[0].name, type:metadata.regionType}"

[
  {
    "name": "centralindia",
    "pair": "southindia",
    "type": "Physical"
  }
]

Availability zones

An availability zone is one or more separate data centres inside a region, each with its own power, cooling and network. The zones in a region are far enough apart that a fire or power cut in one should not hit the others, yet close enough for fast replication.

Picture three railway reservation counters in different buildings of the same station. If one building loses power, passengers queue at the other two. That is what zones give your app.

Azure services use zones in two ways:

• Zonal: you pin a resource to one zone, such as zone 1. A VM in zone 1 stops if zone 1 fails, so you place copies in zones 2 and 3 yourself.
• Zone-redundant: the service spreads itself across zones for you. Zone-redundant storage (ZRS) keeps three copies of your data in three zones.

Zone numbers are logical. Zone 1 in your subscription may be a different building from zone 1 in your friend's subscription. Azure does this to spread load.

Step 3: create a public IP address in a specific zone. The --zone flag is common across many az commands.

az network public-ip create --resource-group rg-practice --name pip-web-z1 \
  --sku Standard --zone 1 --location centralindia

Region pairs

Many older regions are paired with another region in the same geography, usually hundreds of kilometres away. Azure uses pairs for some built-in features, such as geo-redundant storage (GRS), which copies your data to the paired region. During planned platform updates, Azure avoids updating both regions of a pair at the same time.

Newer regions often have no pair. In those regions you design cross-region copies yourself. A region pair is a convenience, not a full disaster recovery plan: you will learn proper DR planning in Backup & Disaster Recovery.

How to choose a region

Ask these questions, in order:

1. Where must the data live? If a contract or law says Indian data must stay in India, use an Indian region. The data residency lesson covers this.
2. Where are your users? Users in Lucknow get faster responses from Central India than from Europe. The delay is called latency.
3. Is the service available there? Check the "products available by region" page before you commit.
4. Do you need zones? For production apps that must survive a data centre failure, pick a region with availability zones.
5. What does it cost? Prices differ between regions. Compare in the official Azure pricing calculator.

Beyond regions: edge and sovereign clouds

Some services work at the edge, close to users rather than in one region. Azure Front Door, for example, caches and routes web traffic through Microsoft's global network. There are also separate sovereign clouds, such as Azure Government in the US and Azure operated by 21Vianet in China, with their own portals and endpoints. Indian customers use the global Azure cloud.

Common mistakes

• Choosing a far region by accident. The portal sometimes suggests "East US". Always check the region box.
• Assuming every region has zones. South India and West India have none. Plan high availability differently there.
• Spreading one app across regions without a reason. Traffic between regions adds latency and data transfer charges.

Key points

• A region is a group of data centres; resources stay in the region you choose.
• India has four public Azure regions: Central India (Pune), India South Central (Hyderabad), South India (Chennai) and West India (Mumbai).
• Availability zones are separate buildings inside a region; zone-redundant services spread across them for you.
• Region pairs help some services replicate, but you still need your own DR plan.
• Choose a region by data rules, user location, service availability, zone support and price.

az account list-locations \
  --query "[?name=='indiasouthcentral' || name=='centralindia'].name" --output table