Azure regional changes — 2026-08-09

· Auto summary
120 new0 regressions0 parked
Daily executive summary

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

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

Representative changes: Standard Dc16ads Cc V5 VM size was newly listed in brazilsouth; Standard Dc16ads V5 VM size was newly listed in brazilsouth; Standard Dc16as Cc V5 VM size was newly listed in brazilsouth.

What changed: 54 net-new regional listings, 66 restored regional listings.

What this means: The 120 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-03 to 2026-08-09): across 7 recorded scans, there were 1,130 new listings and 944 regressions. New listings led on 3 scans; regressions led on 3.

Archived commentary and representative evidence

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

VM SKUs: VM sizes now offered (120 signals; 54 net-new regional availabilities, 66 restored availabilities, up to 1 prior disappearance). SRE impact: more compute shapes for right-sizing, performance, and cost tuning. Coverage now ranges from 8 to 18 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: brazilsouth · dc16ads.cc.v5; brazilsouth · dc16ads.v5; brazilsouth · dc16as.cc.v5; brazilsouth · dc16as.v5; and 116 more.

Engineering context

  • brazilsouth vmSkus.standard.dc16ads.cc.v5 unavailable → available restored availability
    unavailable 87/88 prior days (98.9%)1 prior disappearancecoverage 11/64 monitored regions (17.2%, +1 region)South America: 1 current, 0 priorrestored regional signal
    Also newly available in brazilsouth. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • brazilsouth vmSkus.standard.dc16ads.v5 unavailable → available restored availability
    unavailable 87/88 prior days (98.9%)1 prior disappearancecoverage 17/64 monitored regions (26.6%, +1 region)South America: 1 current, 0 priorrestored regional signal
    Also newly available in brazilsouth. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • brazilsouth vmSkus.standard.dc16as.cc.v5 unavailable → available restored availability
    unavailable 87/88 prior days (98.9%)1 prior disappearancecoverage 11/64 monitored regions (17.2%, +1 region)South America: 1 current, 0 priorrestored regional signal
    Also newly available in brazilsouth. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • brazilsouth vmSkus.standard.dc16as.v5 unavailable → available restored availability
    unavailable 87/88 prior days (98.9%)1 prior disappearancecoverage 18/64 monitored regions (28.1%, +1 region)South America: 1 current, 0 priorrestored regional signal
    Also newly available in brazilsouth. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • brazilsouth vmSkus.standard.dc2ads.v5 unavailable → available restored availability
    unavailable 87/88 prior days (98.9%)1 prior disappearancecoverage 17/64 monitored regions (26.6%, +1 region)South America: 1 current, 0 priorrestored regional signal
    Also newly available in brazilsouth. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • brazilsouth vmSkus.standard.dc2as.v5 unavailable → available restored availability
    unavailable 87/88 prior days (98.9%)1 prior disappearancecoverage 17/64 monitored regions (26.6%, +1 region)South America: 1 current, 0 priorrestored regional signal
    Also newly available in brazilsouth. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • brazilsouth vmSkus.standard.dc32ads.cc.v5 unavailable → available restored availability
    unavailable 87/88 prior days (98.9%)1 prior disappearancecoverage 11/64 monitored regions (17.2%, +1 region)South America: 1 current, 0 priorrestored regional signal
    Also newly available in brazilsouth. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • brazilsouth vmSkus.standard.dc32ads.v5 unavailable → available restored availability
    unavailable 87/88 prior days (98.9%)1 prior disappearancecoverage 17/64 monitored regions (26.6%, +1 region)South America: 1 current, 0 priorrestored regional signal
    Also newly available in brazilsouth. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • brazilsouth vmSkus.standard.dc32as.cc.v5 unavailable → available restored availability
    unavailable 87/88 prior days (98.9%)1 prior disappearancecoverage 11/64 monitored regions (17.2%, +1 region)South America: 1 current, 0 priorrestored regional signal
    Also newly available in brazilsouth. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • brazilsouth vmSkus.standard.dc32as.v5 unavailable → available restored availability
    unavailable 87/88 prior days (98.9%)1 prior disappearancecoverage 17/64 monitored regions (26.6%, +1 region)South America: 1 current, 0 priorrestored regional signal
    Also newly available in brazilsouth. 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.