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

391 new0 regressions0 parked

Daily executive summary

Compared with the 2026-08-31 snapshot, the 2026-09-01 scan recorded 391 new listings, 0 regressions, and 0 parked unknown transitions.

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

Representative changes: grok 4 6 model from xAI (version 1) was newly listed in 31 regions; Basic A0 VM size was newly listed in 2 regions; Basic A1 VM size was newly listed in 2 regions.

What changed: 52 net-new regional listings, 339 restored regional listings.

What this means: The 391 new listings expand the set of regional 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-26 to 2026-09-01): across 7 recorded scans, there were 1,137 new listings and 261 regressions. New listings led on 6 scans; regressions led on 1.

Archived commentary and representative evidence

Latest scan: 391 new availability signals and 0 regressions across 32 regions.

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 1 to 1 of 64 monitored regions. The noisiest affected signal was unavailable 100.0% of prior observations. Expansion pattern: first observed anywhere in the monitored regions. Examples: westus2 · AKS cluster extension type for managed cluster capabilities (microsoft.agentfabric).

Azure AI models: newer models/versions rolling out (31 signals; 31 net-new regional availabilities). SRE impact: new regional model/version options for latency, residency, and model selection. Coverage now ranges from 31 to 31 of 64 monitored regions. The noisiest affected signal was unavailable 100.0% of prior observations. Expansion pattern: first observed anywhere in the monitored regions. Examples: australiaeast · Azure AI model/version catalog entry for model selection (xai.grok-4-6.1); brazilsouth · Azure AI model/version catalog entry for model selection (xai.grok-4-6.1); canadacentral · Azure AI model/version catalog entry for model selection (xai.grok-4-6.1); canadaeast · Azure AI model/version catalog entry for model selection (xai.grok-4-6.1); and 27 more.

VM SKUs: VM sizes now offered (359 signals; 20 net-new regional availabilities, 339 restored availabilities, up to 3 prior disappearances). SRE impact: more compute shapes for right-sizing, performance, and cost tuning. Coverage now ranges from 2 to 23 of 64 monitored regions. The noisiest affected signal was unavailable 100.0% of prior observations. Expansion pattern: regional expansion of an existing signal; restored regional signal. Examples: eastus · Azure virtual-machine size for right-sizing compute (basic.a0); eastus · Azure virtual-machine size for right-sizing compute (basic.a1); eastus · Azure virtual-machine size for right-sizing compute (basic.a2); eastus · Azure virtual-machine size for right-sizing compute (basic.a3); and 355 more.

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

Engineering context

australiaeast aiModels.xai.grok-4-6.1 None → available net-new regional availability
unavailable 110/110 prior days (100.0%)coverage 31/64 monitored regions (48.4%, +31 regions)Oceania: 1 current, 0 priorfirst observed anywhere in the monitored regions
Also newly available in australiaeast, brazilsouth, canadacentral, canadaeast, centralus, eastus, and 25 more. Use this to evaluate model capabilities, regional deployment options, latency, and data residency. Azure OpenAI model availability
brazilsouth aiModels.xai.grok-4-6.1 None → available net-new regional availability
unavailable 110/110 prior days (100.0%)coverage 31/64 monitored regions (48.4%, +31 regions)South America: 1 current, 0 priorfirst observed anywhere in the monitored regions
Also newly available in australiaeast, brazilsouth, canadacentral, canadaeast, centralus, eastus, and 25 more. Use this to evaluate model capabilities, regional deployment options, latency, and data residency. Azure OpenAI model availability
canadacentral aiModels.xai.grok-4-6.1 None → available net-new regional availability
unavailable 110/110 prior days (100.0%)coverage 31/64 monitored regions (48.4%, +31 regions)North America: 11 current, 0 priorfirst observed anywhere in the monitored regions
Also newly available in australiaeast, brazilsouth, canadacentral, canadaeast, centralus, eastus, and 25 more. Use this to evaluate model capabilities, regional deployment options, latency, and data residency. Azure OpenAI model availability
canadaeast aiModels.xai.grok-4-6.1 None → available net-new regional availability
unavailable 110/110 prior days (100.0%)coverage 31/64 monitored regions (48.4%, +31 regions)North America: 11 current, 0 priorfirst observed anywhere in the monitored regions
Also newly available in australiaeast, brazilsouth, canadacentral, canadaeast, centralus, eastus, and 25 more. Use this to evaluate model capabilities, regional deployment options, latency, and data residency. Azure OpenAI model availability
centralus aiModels.xai.grok-4-6.1 None → available net-new regional availability
unavailable 110/110 prior days (100.0%)coverage 31/64 monitored regions (48.4%, +31 regions)North America: 11 current, 0 priorfirst observed anywhere in the monitored regions
Also newly available in australiaeast, brazilsouth, canadacentral, canadaeast, centralus, eastus, and 25 more. Use this to evaluate model capabilities, regional deployment options, latency, and data residency. Azure OpenAI model availability
eastus aiModels.xai.grok-4-6.1 None → available net-new regional availability
unavailable 110/110 prior days (100.0%)coverage 31/64 monitored regions (48.4%, +31 regions)North America: 11 current, 0 priorfirst observed anywhere in the monitored regions
Also newly available in australiaeast, brazilsouth, canadacentral, canadaeast, centralus, eastus, and 25 more. Use this to evaluate model capabilities, regional deployment options, latency, and data residency. Azure OpenAI model availability
eastus vmSkus.basic.a0 unavailable → available restored availability
unavailable 107/110 prior days (97.3%)3 prior disappearancescoverage 3/64 monitored regions (4.7%, +2 regions)North America: 2 current, 0 priorrestored regional signal
Also newly available in eastus, westus2. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
eastus vmSkus.basic.a1 unavailable → available restored availability
unavailable 107/110 prior days (97.3%)3 prior disappearancescoverage 3/64 monitored regions (4.7%, +2 regions)North America: 2 current, 0 priorrestored regional signal
Also newly available in eastus, westus2. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
eastus vmSkus.basic.a2 unavailable → available restored availability
unavailable 107/110 prior days (97.3%)3 prior disappearancescoverage 3/64 monitored regions (4.7%, +2 regions)North America: 2 current, 0 priorrestored regional signal
Also newly available in eastus, westus2. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
eastus vmSkus.basic.a3 unavailable → available restored availability
unavailable 107/110 prior days (97.3%)3 prior disappearancescoverage 3/64 monitored regions (4.7%, +2 regions)North America: 2 current, 0 priorrestored regional signal
Also newly available in eastus, westus2. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes