Azure regional changes — 2026-08-30

· Auto summary
52 new0 regressions0 parked
Daily executive summary

Compared with the 2026-08-29 snapshot, the 2026-08-30 scan recorded 52 new listings, 0 regressions, and 0 parked unknown transitions.

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

Representative changes: Standard D128ds V7 VM size was newly listed in westus; Standard D128lds V7 VM size was newly listed in westus; Standard D128ls V7 VM size was newly listed in westus.

What changed: 52 restored regional listings.

What this means: The 52 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-24 to 2026-08-30): across 6 recorded scans, there were 908 new listings and 195 regressions. New listings led on 5 scans; regressions led on 1.

Archived commentary and representative evidence

Latest scan: 52 new availability signals and 0 regressions across 1 region.

VM SKUs: VM sizes now offered (52 signals; 52 restored availabilities, up to 1 prior disappearance). SRE impact: more compute shapes for right-sizing, performance, and cost tuning. Coverage now ranges from 10 to 10 of 64 monitored regions. The noisiest affected signal was unavailable 99.1% of prior observations. Expansion pattern: restored regional signal. Examples: westus · Azure virtual-machine size for right-sizing compute (d128ds.v7); westus · Azure virtual-machine size for right-sizing compute (d128lds.v7); westus · Azure virtual-machine size for right-sizing compute (d128ls.v7); westus · Azure virtual-machine size for right-sizing compute (d128s.v7); and 48 more.

What this means for Azure users: review placement and fallback plans using these catalog/list signals before changing production deployments.

Engineering context

  • westus vmSkus.standard.d128ds.v7 unavailable → available restored availability
    unavailable 107/108 prior days (99.1%)1 prior disappearancecoverage 10/64 monitored regions (15.6%, +1 region)North America: 7 current, 6 priorrestored regional signal
    Also newly available in westus. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • westus vmSkus.standard.d128lds.v7 unavailable → available restored availability
    unavailable 107/108 prior days (99.1%)1 prior disappearancecoverage 10/64 monitored regions (15.6%, +1 region)North America: 7 current, 6 priorrestored regional signal
    Also newly available in westus. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • westus vmSkus.standard.d128ls.v7 unavailable → available restored availability
    unavailable 107/108 prior days (99.1%)1 prior disappearancecoverage 10/64 monitored regions (15.6%, +1 region)North America: 7 current, 6 priorrestored regional signal
    Also newly available in westus. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • westus vmSkus.standard.d128s.v7 unavailable → available restored availability
    unavailable 107/108 prior days (99.1%)1 prior disappearancecoverage 10/64 monitored regions (15.6%, +1 region)North America: 7 current, 6 priorrestored regional signal
    Also newly available in westus. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • westus vmSkus.standard.d16ds.v7 unavailable → available restored availability
    unavailable 107/108 prior days (99.1%)1 prior disappearancecoverage 10/64 monitored regions (15.6%, +1 region)North America: 7 current, 6 priorrestored regional signal
    Also newly available in westus. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • westus vmSkus.standard.d16lds.v7 unavailable → available restored availability
    unavailable 107/108 prior days (99.1%)1 prior disappearancecoverage 10/64 monitored regions (15.6%, +1 region)North America: 7 current, 6 priorrestored regional signal
    Also newly available in westus. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • westus vmSkus.standard.d16ls.v7 unavailable → available restored availability
    unavailable 107/108 prior days (99.1%)1 prior disappearancecoverage 10/64 monitored regions (15.6%, +1 region)North America: 7 current, 6 priorrestored regional signal
    Also newly available in westus. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • westus vmSkus.standard.d16s.v7 unavailable → available restored availability
    unavailable 107/108 prior days (99.1%)1 prior disappearancecoverage 10/64 monitored regions (15.6%, +1 region)North America: 7 current, 6 priorrestored regional signal
    Also newly available in westus. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • westus vmSkus.standard.d192ds.v7 unavailable → available restored availability
    unavailable 107/108 prior days (99.1%)1 prior disappearancecoverage 10/64 monitored regions (15.6%, +1 region)North America: 7 current, 6 priorrestored regional signal
    Also newly available in westus. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • westus vmSkus.standard.d192lds.v7 unavailable → available restored availability
    unavailable 107/108 prior days (99.1%)1 prior disappearancecoverage 10/64 monitored regions (15.6%, +1 region)North America: 7 current, 6 priorrestored regional signal
    Also newly available in westus. 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.