Azure East US 3 region in Atlanta, due early 2027: zones, DR and pricing

Summary. Microsoft says East US 3 will open in the Greater Atlanta Metro area in early 2027 with availability zones. On 1 November 2026 it has published no launch date, zone count, paired region or day-one service list, and the region is absent from its list of Azure regions, even as a preview. The concrete signal is the Azure Retail Prices API: the Arm-based D4ps v6 virtual machine is listed at $0.14 an hour, with 1-year and 3-year reservations at $726 and $1,402, matching East US and East US 2; South Central US charges $0.168. Transfer between North American regions costs $0.02 per GB, and Microsoft says traffic between zones in one region is not charged. One date may matter more than launch day: VM reservations bought from 1 February 2027 lose the exchange right you would use to change region. In India, Hyderabad's India South Central went live on 6 August 2026 with 3 zones at Central India's D4s v5 price of $0.202 an hour. Our advice: build zone-redundant now, treat East US 3 as a candidate secondary or capacity region, and re-check pairing and services at launch.

About this article. This guide is for cloud architects, platform leads and FinOps teams planning US or India Azure regions. Region status, zones, pairs, latency and prices were checked on 1 November 2026 against the Azure Blog, Microsoft Learn, the Azure bandwidth pricing page and the Azure Retail Prices API. Microsoft has not published East US 3 launch details and prices change, so re-check before you commit. This is general information, not financial or legal advice, and no vendor paid for inclusion. Researched with AI assistance and reviewed by our editorial team.

What Microsoft has confirmed about East US 3, and what it has not

Microsoft first named East US 3 in February 2021, with presence in Fulton and Douglas counties. The launch timing came on 9 December 2025, in an Azure Blog post by Omar Khan, Vice President of Azure Infrastructure Marketing. The post's metadata shows a last edit on 13 August 2026, and it still says early 2027. It says the Atlanta footprint, which already runs Microsoft's AI supercomputers, will expand to serve all customer workloads from East US 3.

So the news is a general-purpose public region on top of an existing AI site. Microsoft unveiled its Atlanta Fairwater AI site on 12 November 2025. DCD reports that East US 3 will draw on three projects: a Fulton County campus where ground was broken in July 2024, plus sites in East Point (Fulton County) and Douglasville (Douglas County).

The position on 1 November 2026, from those sources and Microsoft's region list, pairs page, geographies page and price API:

Three cautions. A price meter shows how Microsoft intends to bill, not that a size will be orderable on day one. Coverage is thin: AKS and Application Gateway have one meter each, and there are no Storage or Bandwidth meters, so you cannot price a whole estate yet. And the x86 D4s v5 and D4s v6 sizes have no meter, so Intel or AMD VM estates cannot price a like-for-like move.

The list is still growing: Arm VM meters date from 1 August 2026, GPU meters from 1 October, and 39 records, including PostgreSQL Flexible Server compute, from 1 November.

The rest of the December 2025 roadmap

The same post promised zone expansions in five existing US regions. Nearly 11 months on, progress is partial, and new zones have surfaced first as previews. Microsoft warns that some services may not support zones even where a region has them.

How East US 3 fits the US footprint

Teams serving the US South-East now choose between Virginia (East US, East US 2) and Texas (South Central US). East US 3 adds an eastern option outside Virginia. Prices below are Linux pay-as-you-go list prices; latency is Microsoft's median (P50) round trip from East US.

Parity is not unique to Atlanta: North Central US and West US 3 already match East US on pay-as-you-go for both sizes. Microsoft has not published latency for East US 3, and we have not measured it. Do not infer a number from geography; test from your own users once it is live.

Zones, pairs and what East US 3 changes for disaster recovery

An availability zone is one or more physically separate data centres with independent power, cooling and networking. Microsoft says zones are typically several kilometres apart, usually within 100 km, and targets inter-zone round trips under about 2 ms, low enough for synchronous replication. It also says Azure does not charge for transfer between zones in a region, on private or public IP addresses. One trap: the Retail Prices API still lists inter-zone meters at $0.01 per GB, dated 2021, so check your invoice if cross-zone traffic is heavy.

Microsoft says production workloads should use multiple zones where available, and mission-critical workloads should consider being both multi-zone and multi-region. Zones do not protect against a full-region outage.

Region pairs are a separate mechanism. A few services, most visibly geo-redundant storage (GRS), replicate to the paired region automatically, and Microsoft staggers planned updates across a pair. But many newer regions have zones and no pair, some pairs run one way (West US 3 pairs to East US, which pairs to West US), and Microsoft says not to rely on its managed failover between pairs as your primary recovery plan.

That leaves three possibilities for East US 3:

The safe course in every case is the last row's logic: treat a Microsoft pair as a bonus. Our multi-region resilience and DR service covers that design work. Also note that logical zone numbers map to physical zones differently per subscription, so zone 1 in two subscriptions may be different buildings.

Latency: the published baseline

Microsoft publishes monthly P50 round-trip times over a 30-day window; the current dataset ends on 30 July 2026. Beyond the East US figures above, East US 2 to South Central US is 31 ms, Central India to South India is 19 to 20 ms, and East US to Central India is 198 ms. Your application will see more once protocol overhead and hops are added.

Keep synchronous replication inside a region, across zones. Between regions, 20 to 60 ms per round trip is fine for asynchronous replication but adds visible commit latency for synchronous writes.

Pricing: what the early meters tell you

The signal is parity. On the D4ps v6, East US 3 matches East US and East US 2 on pay-as-you-go and both reservation terms. South Central US is about 20% higher ($0.168; reservations $870 and $1,682), and 19.8% higher on the x86 D4s v5.

India offers one precedent, not a rule: India South Central launched at Central India's D4s v5 price of $0.202, while South India charges 34% more.

Data transfer is priced by geography, so East US 3 should inherit the North American rates on Microsoft's bandwidth page, though it has no Bandwidth meter yet. Our cloud egress comparison sets these rates against other clouds.

The reservation date to watch

An exchange is how you change a reservation's region. Microsoft's policy says reservations bought from 1 February 2027 for services covered by savings plans, including virtual machines, cannot be exchanged. Those bought earlier keep one final exchange, which starts a new term and must be worth at least the remaining commitment. Cancellations stay capped at $50,000 in a rolling 12 months.

So if you might move from East US 2 to East US 3 within the term, a reservation bought before 1 February keeps that option and one bought later does not. A savings plan, which applies across regions, is the flexible alternative.

Worked cost example: an eight-VM estate across zones and regions

Assume six D4ps v6 Linux VMs spread over three zones in the primary region, two warm-standby VMs in a secondary region, 730 hours a month and 3 TB a month of replication between regions. Prices are list prices on 1 November 2026, before discounts, disks, load balancers and support.

East US 3 saves nothing against a North Central US secondary you can buy today, so its case is geography, not price. The gap between the cheapest and dearest layout is $122.64 a month, or $1,471.68 a year. It scales linearly: every $0.01 an hour of price difference across eight VMs is $58.40 a month (8 × $0.01 × 730).

Reservations move the bill more than region choice. A 1-year D4ps v6 reservation costs $726, or $60.50 a month, against $102.20 at pay-as-you-go (0.14 × 730), a 40.8% saving. Reserving the six primary VMs cuts that line from $613.20 to $363.00 a month.

For x86 estates, the same primary on D4s v5 costs $840.96 a month in East US 2 (6 × $0.192 × 730) against $1,007.40 in South Central US (6 × $0.23 × 730). Our Windows Server 2016 options guide prices that size with Windows. Moving to Arm needs ARM64 builds of your images and dependencies, so test before counting the saving; our Cobalt 200 decision guide covers that choice.

Region selection: which to pick

India: Central India, South India, West India and India South Central

Microsoft made India South Central in Hyderabad generally available on 6 August 2026, its fourth cloud region in India alongside Central India (Pune), South India (Chennai) and West India (Mumbai). It also operates Jio India West and Jio India Central with Jio. The new region has three zones designed for India's regulatory and seismic-zone requirements and sits within a $20.5 billion investment commitment. Microsoft says services arrive there over time, so check each one.

Zones and pairs below are from Microsoft's region list, and prices from the Retail Prices API.

First, India now has two zone-enabled public regions. For a workload that must stay in India under your DPDP design, you can run zone-redundant in one and keep a warm secondary in the other. Price that pairing on x86, because Hyderabad has no D4ps v6 meter; its 1-year D4s v5 reservation is $48 below Pune's.

Second, the pairs are asymmetric. India South Central pairs to Central India, but Central India pairs to South India. Geo-redundant storage from Pune therefore replicates to Chennai, a region without zones. If you want Hyderabad as the recovery target for Pune data, configure replication yourself. HDFC Bank, in Microsoft's launch release, describes the new region as a dedicated recovery site alongside its Central India footprint.

Third, inter-region traffic within Asia costs $0.08 per GB, four times the North American rate. Running the worked example in India on D4s v5, with a Central India primary and 3 TB a month replicated, a Hyderabad secondary costs $884.76 + $294.92 + $240.00 = $1,419.68 a month. A Chennai secondary costs $884.76 + $395.66 + $240.00 = $1,520.42. Hyderabad saves $100.74 a month and gives the secondary zones.

India South Central and West India are not yet in Microsoft's latency table, and East US to Central India is about 198 ms, so serve each market from its own regions. Our DPDP data residency guide covers residency patterns in more depth.

Launch-day checklist for East US 3

1. Confirm East US 3 is in Microsoft's region list, with its zone count and any preview flags.

1. Check the products-by-region page for every service and tier in your design.

1. Request quota early for the sizes you need.

1. Record whether East US 3 is paired, one-way paired or nonpaired.

1. Check your subscription's zone mapping (first command below).

1. Re-price your actual sizes from the Retail Prices API (second command below).

1. Measure latency from your users and other regions with your real protocol.

1. Update Azure Policy allowed-locations rules and landing zone templates.

1. Run a failover drill before naming East US 3 as a recovery target.

1. Review reservation terms before shifting committed workloads.

            az account list-locations \
  --query "[?name=='eastus3'].{name:name, zones:availabilityZoneMappings}" -o json
          

            curl -s "https://prices.azure.com/api/retail/prices?\$filter=armSkuName%20eq%20'Standard_D4ps_v6'%20and%20armRegionName%20eq%20'eastus3'"
          

How eCorpIT can help

eCorpIT is a Gurugram-based technology organisation, founded in 2021, assessed at CMMI Level 5 and MSME certified, with senior-led engineering teams working across AWS, Microsoft and Google platforms. Our cloud computing practice maps each service in your design to region and zone support, models compute, reservation and transfer costs across candidate regions, and builds zone-redundant primaries with service-level replication that does not depend on a Microsoft pair. Talk to us at /contact-us/.

Last updated: 1 November 2026.

References

1. Microsoft's commitment to supporting cloud infrastructure demand in the United States, 9 December 2025, modified 13 August 2026 — Microsoft Azure Blog

1. List of Azure regions — Microsoft Learn

1. Azure Retail Prices API: Standard_D4ps_v6 in East US 3 — Microsoft

1. Azure Retail Prices API: Standard_D4ps_v6 in East US — Microsoft

1. Azure Retail Prices API: Standard_D4ps_v6 in East US 2 — Microsoft

1. Azure Retail Prices API: Standard_D4ps_v6 in South Central US — Microsoft

1. Bandwidth pricing — Microsoft Azure

1. What are availability zones? — Microsoft Learn

1. Self-service exchanges and refunds for Azure Reservations, updated 29 July 2026 — Microsoft Learn

1. Microsoft's newest India datacenter region goes live to power the country's AI economy and enable Frontier Firms, 6 August 2026 — Microsoft Source Asia

1. Azure Retail Prices API: Standard_D4s_v5 in India South Central — Microsoft

1. Microsoft will establish its next US datacenter region in Georgia's Fulton and Douglas Counties, 11 February 2021 — Microsoft Azure Blog

1. Infinite scale: The architecture behind the Azure AI superfactory, 12 November 2025 — The Official Microsoft Blog

1. Microsoft to launch new cloud region in Atlanta, Georgia, in 2027, 11 December 2025 — DCD

1. Azure region pairs and nonpaired regions — Microsoft Learn

1. Choose the right Azure region for you — Microsoft Azure

1. Azure Retail Prices API: all meters for US East 3 (eastus3) — Microsoft

1. Azure Retail Prices API: Standard_D4s_v5 in East US 3 (no results) — Microsoft

1. Azure Retail Prices API: Standard_D4s_v6 in East US 3 (no results) — Microsoft

1. Azure Government overview, updated 19 May 2026 — Microsoft Learn

1. Azure Retail Prices API: Standard_D4ps_v6 across regions — Microsoft

1. Azure Retail Prices API: Standard_D4s_v5 across regions — Microsoft

1. Azure network round-trip latency statistics, dataset to 30 July 2026 — Microsoft Learn

1. Azure Retail Prices API: Bandwidth in East US 2 — Microsoft

1. Azure Retail Prices API: Standard_D4s_v5 in South Central US — Microsoft

1. Azure Retail Prices API: Standard_D4s_v5 in East US 2 — Microsoft

1. Azure Retail Prices API: Standard_D4s_v5 in Central India — Microsoft

1. Azure Retail Prices API: Standard_D4s_v5 in South India — Microsoft

1. Decide between a savings plan and a reservation — Microsoft Learn

1. Azure Retail Prices API: Standard_D4s_v5 in West India — Microsoft