Azure regional changes — 2026-08-08

· Auto summary
0 new96 regressions0 parked
Daily executive summary

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

Where it changed: VM SKUs: 0 new listings, 96 regressions.

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

What changed: 66 first recorded disappearances, 30 recurring disappearances.

What this means: Review the 96 regressions against existing regional targets and fallbacks. 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-02 to 2026-08-08): across 7 recorded scans, there were 1,010 new listings and 944 regressions. New listings led on 2 scans; regressions led on 3.

Archived commentary and representative evidence

Latest scan: 0 new availability signals and 96 regressions across 2 regions.

VM SKUs: VM sizes withdrawn (96 signals; 66 deprecation candidates, 30 recurring disappearances, up to 1 prior disappearance). SRE impact: capacity planning and SKU fallback lists should be rechecked. Coverage now ranges from 10 to 17 of 64 monitored regions. The noisiest affected signal was unavailable 98.9% of prior observations. Examples: brazilsouth · dc16ads.cc.v5; brazilsouth · dc16ads.v5; brazilsouth · dc16as.cc.v5; brazilsouth · dc16as.v5; and 92 more.

Engineering context

  • brazilsouth vmSkus.standard.dc16ads.cc.v5 available → unavailable deprecation candidate
    unavailable 86/87 prior days (98.9%)coverage 10/64 monitored regions (15.6%, -2 regions)coverage removed from 16.7% of prior regions
    Still available in centralindia, eastus, eastus2euap, italynorth, jioindiacentral, jioindiawest, and 4 more. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • brazilsouth vmSkus.standard.dc16ads.v5 available → unavailable deprecation candidate
    unavailable 86/87 prior days (98.9%)coverage 16/64 monitored regions (25.0%, -1 region)coverage removed from 5.9% of prior regions
    Still available in centralindia, centraluseuap, eastasia, eastus, eastus2euap, germanywestcentral, and 10 more. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • brazilsouth vmSkus.standard.dc16as.cc.v5 available → unavailable deprecation candidate
    unavailable 86/87 prior days (98.9%)coverage 10/64 monitored regions (15.6%, -2 regions)coverage removed from 16.7% of prior regions
    Still available in centralindia, eastus, eastus2euap, italynorth, jioindiacentral, jioindiawest, and 4 more. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • brazilsouth vmSkus.standard.dc16as.v5 available → unavailable deprecation candidate
    unavailable 86/87 prior days (98.9%)coverage 17/64 monitored regions (26.6%, -1 region)coverage removed from 5.6% of prior regions
    Still available in centralindia, centraluseuap, eastasia, eastus, eastus2euap, germanywestcentral, and 11 more. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • brazilsouth vmSkus.standard.dc2ads.v5 available → unavailable deprecation candidate
    unavailable 86/87 prior days (98.9%)coverage 16/64 monitored regions (25.0%, -1 region)coverage removed from 5.9% of prior regions
    Still available in centralindia, centraluseuap, eastasia, eastus, eastus2euap, germanywestcentral, and 10 more. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • brazilsouth vmSkus.standard.dc2as.v5 available → unavailable deprecation candidate
    unavailable 86/87 prior days (98.9%)coverage 16/64 monitored regions (25.0%, -1 region)coverage removed from 5.9% of prior regions
    Still available in centralindia, centraluseuap, eastasia, eastus, eastus2euap, germanywestcentral, and 10 more. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • brazilsouth vmSkus.standard.dc32ads.cc.v5 available → unavailable deprecation candidate
    unavailable 86/87 prior days (98.9%)coverage 10/64 monitored regions (15.6%, -2 regions)coverage removed from 16.7% of prior regions
    Still available in centralindia, eastus, eastus2euap, italynorth, jioindiacentral, jioindiawest, and 4 more. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • brazilsouth vmSkus.standard.dc32ads.v5 available → unavailable deprecation candidate
    unavailable 86/87 prior days (98.9%)coverage 16/64 monitored regions (25.0%, -1 region)coverage removed from 5.9% of prior regions
    Still available in centralindia, centraluseuap, eastasia, eastus, eastus2euap, germanywestcentral, and 10 more. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • brazilsouth vmSkus.standard.dc32as.cc.v5 available → unavailable deprecation candidate
    unavailable 86/87 prior days (98.9%)coverage 10/64 monitored regions (15.6%, -2 regions)coverage removed from 16.7% of prior regions
    Still available in centralindia, eastus, eastus2euap, italynorth, jioindiacentral, jioindiawest, and 4 more. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • brazilsouth vmSkus.standard.dc32as.v5 available → unavailable deprecation candidate
    unavailable 86/87 prior days (98.9%)coverage 16/64 monitored regions (25.0%, -1 region)coverage removed from 5.9% of prior regions
    Still available in centralindia, centraluseuap, eastasia, eastus, eastus2euap, germanywestcentral, and 10 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.