Azure regional changes — 2026-08-07

· Auto summary
164 new132 regressions0 parked
Daily executive summary

Compared with the 2026-08-06 snapshot, the 2026-08-07 scan recorded 164 new listings, 132 regressions, and 0 parked unknown transitions.

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

Representative changes: Standard Dc16ads Cc V5 VM size was no longer listed in southindia; Standard Dc16ads V5 VM size was no longer listed in southindia; Standard Dc16as Cc V5 VM size was no longer listed in southindia.

What changed: 132 recurring disappearances, 164 net-new regional listings.

What this means: Review the 132 regressions against existing regional targets and fallbacks first; treat the 164 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-01 to 2026-08-07): across 7 recorded scans, there were 1,226 new listings and 1,189 regressions. New listings led on 2 scans; regressions led on 3.

Archived commentary and representative evidence

Latest scan: 164 new availability signals and 132 regressions across 59 regions.

VM SKUs: VM sizes withdrawn (132 signals; 132 recurring disappearances, up to 1 prior disappearance). SRE impact: capacity planning and SKU fallback lists should be rechecked. Coverage now ranges from 12 to 18 of 64 monitored regions. The noisiest affected signal was unavailable 94.2% of prior observations. Examples: southindia · dc16ads.cc.v5; southindia · dc16ads.v5; southindia · dc16as.cc.v5; southindia · dc16as.v5; and 128 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 · thoughtswin.amplifi; australiacentral2 · thoughtswin.amplifi; australiaeast · thoughtswin.amplifi; australiasoutheast · thoughtswin.amplifi; and 55 more.

VM SKUs: VM sizes now offered (105 signals; 105 net-new regional availabilities). SRE impact: more compute shapes for right-sizing, performance, and cost tuning. Coverage now ranges from 12 to 54 of 64 monitored regions. The noisiest affected signal was unavailable 100.0% of prior observations. Expansion pattern: regional expansion of an existing signal. Examples: brazilsouth · dc16ads.cc.v5; brazilsouth · dc16ads.v5; brazilsouth · dc16as.cc.v5; brazilsouth · dc16as.v5; and 101 more.

Engineering context

  • southindia vmSkus.standard.dc16ads.cc.v5 available → unavailable recurring disappearance
    unavailable 73/86 prior days (84.9%)coverage 12/64 monitored regions (18.8%, -1 region)coverage removed from 7.7% of prior regionsAsia: 4 current, 5 prior
    Also newly available in brazilsouth. Still available in brazilsouth, centralindia, eastus, eastus2euap, italynorth, jioindiacentral, and 6 more. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • southindia vmSkus.standard.dc16ads.v5 available → unavailable recurring disappearance
    unavailable 73/86 prior days (84.9%)coverage 17/64 monitored regions (26.6%, -1 region)coverage removed from 5.6% of prior regionsAsia: 6 current, 7 prior
    Also newly available in brazilsouth. Still available in brazilsouth, centralindia, centraluseuap, eastasia, eastus, eastus2euap, and 11 more. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • southindia vmSkus.standard.dc16as.cc.v5 available → unavailable recurring disappearance
    unavailable 73/86 prior days (84.9%)coverage 12/64 monitored regions (18.8%, -1 region)coverage removed from 7.7% of prior regionsAsia: 4 current, 5 prior
    Also newly available in brazilsouth. Still available in brazilsouth, centralindia, eastus, eastus2euap, italynorth, jioindiacentral, and 6 more. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • southindia vmSkus.standard.dc16as.v5 available → unavailable recurring disappearance
    unavailable 73/86 prior days (84.9%)coverage 18/64 monitored regions (28.1%, -1 region)coverage removed from 5.3% of prior regionsAsia: 6 current, 7 prior
    Also newly available in brazilsouth. Still available in brazilsouth, centralindia, centraluseuap, eastasia, eastus, eastus2euap, and 12 more. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • southindia vmSkus.standard.dc2ads.v5 available → unavailable recurring disappearance
    unavailable 73/86 prior days (84.9%)coverage 17/64 monitored regions (26.6%, -1 region)coverage removed from 5.6% of prior regionsAsia: 6 current, 7 prior
    Also newly available in brazilsouth. Still available in brazilsouth, centralindia, centraluseuap, eastasia, eastus, eastus2euap, and 11 more. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • southindia vmSkus.standard.dc2as.v5 available → unavailable recurring disappearance
    unavailable 73/86 prior days (84.9%)coverage 17/64 monitored regions (26.6%, -1 region)coverage removed from 5.6% of prior regionsAsia: 6 current, 7 prior
    Also newly available in brazilsouth. Still available in brazilsouth, centralindia, centraluseuap, eastasia, eastus, eastus2euap, and 11 more. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • southindia vmSkus.standard.dc32ads.cc.v5 available → unavailable recurring disappearance
    unavailable 73/86 prior days (84.9%)coverage 12/64 monitored regions (18.8%, -1 region)coverage removed from 7.7% of prior regionsAsia: 4 current, 5 prior
    Also newly available in brazilsouth. Still available in brazilsouth, centralindia, eastus, eastus2euap, italynorth, jioindiacentral, and 6 more. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • southindia vmSkus.standard.dc32ads.v5 available → unavailable recurring disappearance
    unavailable 73/86 prior days (84.9%)coverage 17/64 monitored regions (26.6%, -1 region)coverage removed from 5.6% of prior regionsAsia: 6 current, 7 prior
    Also newly available in brazilsouth. Still available in brazilsouth, centralindia, centraluseuap, eastasia, eastus, eastus2euap, and 11 more. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • southindia vmSkus.standard.dc32as.cc.v5 available → unavailable recurring disappearance
    unavailable 73/86 prior days (84.9%)coverage 12/64 monitored regions (18.8%, -1 region)coverage removed from 7.7% of prior regionsAsia: 4 current, 5 prior
    Also newly available in brazilsouth. Still available in brazilsouth, centralindia, eastus, eastus2euap, italynorth, jioindiacentral, and 6 more. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • southindia vmSkus.standard.dc32as.v5 available → unavailable recurring disappearance
    unavailable 73/86 prior days (84.9%)coverage 17/64 monitored regions (26.6%, -1 region)coverage removed from 5.6% of prior regionsAsia: 6 current, 7 prior
    Also newly available in brazilsouth. Still available in brazilsouth, centralindia, centraluseuap, eastasia, eastus, eastus2euap, and 11 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.