Azure regional changes — 2026-07-21 | Azure regional availability 2026-07-21

272 new283 regressions1 parked

Daily executive summary

Compared with the 2026-07-20 snapshot, the 2026-07-21 scan recorded 272 new listings, 283 regressions, and 1 parked unknown transition.

Where it changed: VM SKUs: 272 new listings, 283 regressions.

Representative changes: Basic A0 VM size was no longer listed in westus; Basic A1 VM size was no longer listed in westus; Basic A2 VM size was no longer listed in westus.

What changed: 275 first recorded disappearances, 8 recurring disappearances, 220 net-new regional listings, 52 restored regional listings.

What this means: Review the 283 regressions against existing regional targets and fallbacks first; treat the 272 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-07-15 to 2026-07-21): across 7 recorded scans, there were 1,488 new listings and 553 regressions. New listings led on 5 scans; regressions led on 2.

Archived commentary and representative evidence

Latest scan: 272 new availability signals and 283 regressions across 6 regions.

VM SKUs: VM sizes withdrawn (283 signals; 275 deprecation candidates, 8 recurring disappearances, up to 2 prior disappearances). SRE impact: capacity planning and SKU fallback lists should be rechecked. Coverage now ranges from 1 to 30 of 64 monitored regions. The noisiest affected signal was unavailable 98.6% of prior observations. Examples: westus · basic.a0; westus · basic.a1; westus · basic.a2; westus · basic.a3; and 279 more.

VM SKUs: VM sizes now offered (272 signals; 220 net-new regional availabilities, 52 restored availabilities, up to 1 prior disappearance). SRE impact: more compute shapes for right-sizing, performance, and cost tuning. Coverage now ranges from 7 to 39 of 64 monitored regions. The noisiest affected signal was unavailable 100.0% of prior observations. Expansion pattern: first observed in Europe; regional expansion of an existing signal; restored regional signal. Examples: germanywestcentral · d128ds.v7; germanywestcentral · d128lds.v7; germanywestcentral · d128ls.v7; germanywestcentral · d128s.v7; and 268 more.

Engineering context

westus vmSkus.basic.a0 available → unavailable deprecation candidate
unavailable 69/70 prior days (98.6%)coverage 1/64 monitored regions (1.6%, -1 region)coverage removed from 50.0% of prior regionsNorth America: 1 current, 2 prior
Still available in westus3. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
westus vmSkus.basic.a1 available → unavailable deprecation candidate
unavailable 69/70 prior days (98.6%)coverage 1/64 monitored regions (1.6%, -1 region)coverage removed from 50.0% of prior regionsNorth America: 1 current, 2 prior
Still available in westus3. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
westus vmSkus.basic.a2 available → unavailable deprecation candidate
unavailable 69/70 prior days (98.6%)coverage 1/64 monitored regions (1.6%, -1 region)coverage removed from 50.0% of prior regionsNorth America: 1 current, 2 prior
Still available in westus3. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
westus vmSkus.basic.a3 available → unavailable deprecation candidate
unavailable 69/70 prior days (98.6%)coverage 1/64 monitored regions (1.6%, -1 region)coverage removed from 50.0% of prior regionsNorth America: 1 current, 2 prior
Still available in westus3. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
westus vmSkus.basic.a4 available → unavailable deprecation candidate
unavailable 69/70 prior days (98.6%)coverage 1/64 monitored regions (1.6%, -1 region)coverage removed from 50.0% of prior regionsNorth America: 1 current, 2 prior
Still available in westus3. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
westus vmSkus.standard.a0 available → unavailable deprecation candidate
unavailable 69/70 prior days (98.6%)coverage 1/64 monitored regions (1.6%, -1 region)coverage removed from 50.0% of prior regionsNorth America: 1 current, 2 prior
Still available in westus3. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
westus vmSkus.standard.a1 available → unavailable deprecation candidate
unavailable 69/70 prior days (98.6%)coverage 1/64 monitored regions (1.6%, -1 region)coverage removed from 50.0% of prior regionsNorth America: 1 current, 2 prior
Still available in westus3. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
westus vmSkus.standard.a10 available → unavailable deprecation candidate
unavailable 69/70 prior days (98.6%)coverage 1/64 monitored regions (1.6%, -1 region)coverage removed from 50.0% of prior regionsNorth America: 1 current, 2 prior
Still available in westus3. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
westus vmSkus.standard.a11 available → unavailable deprecation candidate
unavailable 69/70 prior days (98.6%)coverage 1/64 monitored regions (1.6%, -1 region)coverage removed from 50.0% of prior regionsNorth America: 1 current, 2 prior
Still available in westus3. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
westus vmSkus.standard.a2 available → unavailable deprecation candidate
unavailable 69/70 prior days (98.6%)coverage 1/64 monitored regions (1.6%, -1 region)coverage removed from 50.0% of prior regionsNorth America: 1 current, 2 prior
Still available in westus3. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes