Azure regional changes — 2026-09-03 | Azure regional availability 2026-09-03

377 new661 regressions0 parked

Daily executive summary

Compared with the 2026-09-02 snapshot, the 2026-09-03 scan recorded 377 new listings, 661 regressions, and 0 parked unknown transitions.

Where it changed: VM SKUs: 376 new listings, 650 regressions; Azure AI models: 0 new listings, 11 regressions; AKS extensions: 1 new listing, 0 regressions.

Representative changes: Standard Nc12s V3 VM size was no longer listed in 6 regions; Standard Nc24rs V3 VM size was no longer listed in 6 regions; Standard Nc24s V3 VM size was no longer listed in 6 regions.

What changed: 645 first recorded disappearances, 16 recurring disappearances, 377 net-new regional listings.

What this means: Review the 661 regressions against existing regional targets and fallbacks first; treat the 377 new listings as options to validate. These are read-only catalog/list signals, not quota, capacity, or deployment results. Zero new delistings does not establish recovery of earlier missing listings.

7-day context (2026-08-28 to 2026-09-03): across 7 recorded scans, there were 1,253 new listings and 1,070 regressions. New listings led on 5 scans; regressions led on 2.

Archived commentary and representative evidence

Latest scan: 377 new availability signals and 661 regressions across 15 regions.

Azure AI models: models/versions delisted (likely deprecation) (11 signals; 11 deprecation candidates). SRE impact: review model deployment targets and fallback model/version choices. Coverage now ranges from 31 to 33 of 64 monitored regions. Examples: qatarcentral · Azure AI model/version catalog entry for model selection (openai.gpt-4-1-mini.2025-04-14); qatarcentral · Azure AI model/version catalog entry for model selection (openai.gpt-4-1-nano.2025-04-14); qatarcentral · Azure AI model/version catalog entry for model selection (openai.gpt-4-1.2025-04-14); qatarcentral · Azure AI model/version catalog entry for model selection (openai.gpt-4o-mini.2024-07-18); and 7 more.

VM SKUs: VM sizes withdrawn (650 signals; 634 deprecation candidates, 16 recurring disappearances, up to 1 prior disappearance). SRE impact: capacity planning and SKU fallback lists should be rechecked. Coverage now ranges from 0 to 47 of 64 monitored regions. The noisiest affected signal was unavailable 90.2% of prior observations. Examples: australiaeast · Azure virtual-machine size for right-sizing compute (nc12s.v3); australiaeast · Azure virtual-machine size for right-sizing compute (nc24rs.v3); australiaeast · Azure virtual-machine size for right-sizing compute (nc24s.v3); australiaeast · Azure virtual-machine size for right-sizing compute (nc6s.v3); and 646 more.

AKS extensions: extension types now listed (1 signal; 1 net-new regional availability). SRE impact: new managed cluster capabilities such as GitOps, policy, or observability. Coverage now ranges from 59 to 59 of 64 monitored regions. The noisiest affected signal was unavailable 58.0% of prior observations. Expansion pattern: regional expansion of an existing signal. Examples: uaecentral · AKS cluster extension type for managed cluster capabilities (microsoft.kubernetesworkloadidfederation).

VM SKUs: VM sizes now offered (376 signals; 376 net-new regional availabilities). SRE impact: more compute shapes for right-sizing, performance, and cost tuning. Coverage now ranges from 36 to 39 of 64 monitored regions. The noisiest affected signal was unavailable 100.0% of prior observations. Expansion pattern: regional expansion of an existing signal. Examples: brazilsoutheast · Azure virtual-machine size for right-sizing compute (d128nds.v6); brazilsoutheast · Azure virtual-machine size for right-sizing compute (d128nlds.v6); brazilsoutheast · Azure virtual-machine size for right-sizing compute (d128nls.v6); brazilsoutheast · Azure virtual-machine size for right-sizing compute (d128ns.v6); and 372 more.

What this means for Azure users: review placement and fallback plans using these catalog/list signals before changing production deployments.

Engineering context

australiaeast vmSkus.standard.nc12s.v3 available → unavailable recurring disappearance
unavailable 36/112 prior days (32.1%)1 prior disappearancecoverage 5/64 monitored regions (7.8%, -6 regions)coverage removed from 54.5% of prior regions
Still available in canadacentral, eastus, eastus2, jioindiawest, westeurope. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
australiaeast vmSkus.standard.nc24rs.v3 available → unavailable recurring disappearance
unavailable 36/112 prior days (32.1%)1 prior disappearancecoverage 5/64 monitored regions (7.8%, -6 regions)coverage removed from 54.5% of prior regions
Still available in canadacentral, eastus, eastus2, jioindiawest, westeurope. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
australiaeast vmSkus.standard.nc24s.v3 available → unavailable recurring disappearance
unavailable 36/112 prior days (32.1%)1 prior disappearancecoverage 5/64 monitored regions (7.8%, -6 regions)coverage removed from 54.5% of prior regions
Still available in canadacentral, eastus, eastus2, jioindiawest, westeurope. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
australiaeast vmSkus.standard.nc6s.v3 available → unavailable recurring disappearance
unavailable 36/112 prior days (32.1%)1 prior disappearancecoverage 5/64 monitored regions (7.8%, -6 regions)coverage removed from 54.5% of prior regions
Still available in canadacentral, eastus, eastus2, jioindiawest, westeurope. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
indonesiacentral vmSkus.basic.a0 available → None deprecation candidate
unavailable 90/112 prior days (80.4%)coverage 0/64 monitored regions (0.0%, -1 region)coverage removed from 100.0% of prior regions
VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
indonesiacentral vmSkus.basic.a1 available → None deprecation candidate
unavailable 90/112 prior days (80.4%)coverage 0/64 monitored regions (0.0%, -1 region)coverage removed from 100.0% of prior regions
VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
indonesiacentral vmSkus.basic.a2 available → None deprecation candidate
unavailable 90/112 prior days (80.4%)coverage 0/64 monitored regions (0.0%, -1 region)coverage removed from 100.0% of prior regions
VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
indonesiacentral vmSkus.basic.a3 available → None deprecation candidate
unavailable 90/112 prior days (80.4%)coverage 0/64 monitored regions (0.0%, -1 region)coverage removed from 100.0% of prior regions
VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
indonesiacentral vmSkus.basic.a4 available → None deprecation candidate
unavailable 90/112 prior days (80.4%)coverage 0/64 monitored regions (0.0%, -1 region)coverage removed from 100.0% of prior regions
VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
indonesiacentral vmSkus.standard.a0 available → None deprecation candidate
unavailable 90/112 prior days (80.4%)coverage 0/64 monitored regions (0.0%, -1 region)coverage removed from 100.0% of prior regions
VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes