Azure regional changes — 2026-08-13

· Auto summary
603 new18 regressions0 parked
Daily executive summary

Compared with the 2026-08-12 snapshot, the 2026-08-13 scan recorded 603 new listings, 18 regressions, and 0 parked unknown transitions.

Where it changed: VM SKUs: 544 new listings, 18 regressions; AKS extensions: 59 new listings, 0 regressions.

Representative changes: Standard M208ms V2 VM size was no longer listed in 2 regions; Standard M208s V2 VM size was no longer listed in 2 regions; Standard M416 208ms V2 VM size was no longer listed in 2 regions.

What changed: 18 first recorded disappearances, 463 net-new regional listings, 140 restored regional listings.

What this means: Review the 18 regressions against existing regional targets and fallbacks first; treat the 603 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-07 to 2026-08-13): across 7 recorded scans, there were 2,381 new listings and 442 regressions. New listings led on 6 scans; regressions led on 1.

Archived commentary and representative evidence

Latest scan: 603 new availability signals and 18 regressions across 59 regions.

VM SKUs: VM sizes withdrawn (18 signals; 18 deprecation candidates). SRE impact: capacity planning and SKU fallback lists should be rechecked. Coverage now ranges from 40 to 40 of 64 monitored regions. The noisiest affected signal was unavailable 46.7% of prior observations. Examples: chilecentral · m208ms.v2; chilecentral · m208s.v2; chilecentral · m416.208ms.v2; chilecentral · m416.208s.v2; and 14 more.

AKS extensions: extension types now listed (59 signals; 59 net-new regional availabilities). 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 100.0% of prior observations. Expansion pattern: first observed anywhere in the monitored regions. Examples: australiacentral · optum.icp; australiacentral2 · optum.icp; australiaeast · optum.icp; australiasoutheast · optum.icp; and 55 more.

VM SKUs: VM sizes now offered (544 signals; 404 net-new regional availabilities, 140 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 42 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: southafricawest · d16pds.v6; southafricawest · d16plds.v6; southafricawest · d16pls.v6; southafricawest · d16ps.v6; and 540 more.

Engineering context

  • chilecentral vmSkus.standard.m208ms.v2 available → unavailable deprecation candidate
    unavailable 43/92 prior days (46.7%)coverage 40/64 monitored regions (62.5%, -2 regions)coverage removed from 4.8% of prior regionsSouth America: 2 current, 3 prior
    Still available in australiacentral, australiacentral2, australiaeast, australiasoutheast, brazilsouth, brazilsoutheast, and 34 more. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • chilecentral vmSkus.standard.m208s.v2 available → unavailable deprecation candidate
    unavailable 43/92 prior days (46.7%)coverage 40/64 monitored regions (62.5%, -2 regions)coverage removed from 4.8% of prior regionsSouth America: 2 current, 3 prior
    Still available in australiacentral, australiacentral2, australiaeast, australiasoutheast, brazilsouth, brazilsoutheast, and 34 more. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • chilecentral vmSkus.standard.m416.208ms.v2 available → unavailable deprecation candidate
    unavailable 43/92 prior days (46.7%)coverage 40/64 monitored regions (62.5%, -2 regions)coverage removed from 4.8% of prior regionsSouth America: 2 current, 3 prior
    Still available in australiacentral, australiacentral2, australiaeast, australiasoutheast, brazilsouth, brazilsoutheast, and 34 more. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • chilecentral vmSkus.standard.m416.208s.v2 available → unavailable deprecation candidate
    unavailable 43/92 prior days (46.7%)coverage 40/64 monitored regions (62.5%, -2 regions)coverage removed from 4.8% of prior regionsSouth America: 2 current, 3 prior
    Still available in australiacentral, australiacentral2, australiaeast, australiasoutheast, brazilsouth, brazilsoutheast, and 34 more. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • chilecentral vmSkus.standard.m416ms.v2 available → unavailable deprecation candidate
    unavailable 43/92 prior days (46.7%)coverage 40/64 monitored regions (62.5%, -2 regions)coverage removed from 4.8% of prior regionsSouth America: 2 current, 3 prior
    Still available in australiacentral, australiacentral2, australiaeast, australiasoutheast, brazilsouth, brazilsoutheast, and 34 more. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • chilecentral vmSkus.standard.m416s.10.v2 available → unavailable deprecation candidate
    unavailable 43/92 prior days (46.7%)coverage 40/64 monitored regions (62.5%, -2 regions)coverage removed from 4.8% of prior regionsSouth America: 2 current, 3 prior
    Still available in australiacentral, australiacentral2, australiaeast, australiasoutheast, brazilsouth, brazilsoutheast, and 34 more. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • chilecentral vmSkus.standard.m416s.8.v2 available → unavailable deprecation candidate
    unavailable 43/92 prior days (46.7%)coverage 40/64 monitored regions (62.5%, -2 regions)coverage removed from 4.8% of prior regionsSouth America: 2 current, 3 prior
    Still available in australiacentral, australiacentral2, australiaeast, australiasoutheast, brazilsouth, brazilsoutheast, and 34 more. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • chilecentral vmSkus.standard.m416s.9.v2 available → unavailable deprecation candidate
    unavailable 43/92 prior days (46.7%)coverage 40/64 monitored regions (62.5%, -2 regions)coverage removed from 4.8% of prior regionsSouth America: 2 current, 3 prior
    Still available in australiacentral, australiacentral2, australiaeast, australiasoutheast, brazilsouth, brazilsoutheast, and 34 more. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • chilecentral vmSkus.standard.m416s.v2 available → unavailable deprecation candidate
    unavailable 43/92 prior days (46.7%)coverage 40/64 monitored regions (62.5%, -2 regions)coverage removed from 4.8% of prior regionsSouth America: 2 current, 3 prior
    Still available in australiacentral, australiacentral2, australiaeast, australiasoutheast, brazilsouth, brazilsoutheast, and 34 more. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • malaysiawest vmSkus.standard.m208ms.v2 available → unavailable deprecation candidate
    unavailable 0/92 prior days (0.0%)coverage 40/64 monitored regions (62.5%, -2 regions)coverage removed from 4.8% of prior regionsAsia: 10 current, 11 prior
    Still available in australiacentral, australiacentral2, australiaeast, australiasoutheast, brazilsouth, brazilsoutheast, and 34 more. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes

Generated from the monitor's structured change evidence. See the status meanings for what each signal proves, or browse all posts.

Help make this page clearer

Two short answers; GitHub will open a draft for your review. No Forms, token, or automatic submission.

This repository is public. Review the text and image for private details. Opening the draft sends text/context to GitHub in its URL. Pasting or attaching an image uploads it to GitHub immediately.

Describe the desired outcome in plain text. This becomes the issue's ### Objective. After reviewing the issue, a maintainer can add azure-backlog to queue it for a scheduled agent; the website does not add that label or start a run.

Page context included in the draft

Nothing is posted by this website. Sign in to GitHub if needed, review, attach your screenshot, and choose Submit. Closing this panel clears the local draft and screenshot.