Azure regional changes — 2026-08-16

· Auto summary
114 new0 regressions0 parked
Daily executive summary

Compared with the 2026-08-15 snapshot, the 2026-08-16 scan recorded 114 new listings, 0 regressions, and 0 parked unknown transitions.

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

Representative changes: Standard D128nds V6 VM size was newly listed in 2 regions; Standard D128nlds V6 VM size was newly listed in 2 regions; Standard D128nls V6 VM size was newly listed in 2 regions.

What changed: 114 net-new regional listings.

What this means: The 114 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-10 to 2026-08-16): across 7 recorded scans, there were 2,394 new listings and 776 regressions. New listings led on 5 scans; regressions led on 2.

Archived commentary and representative evidence

Latest scan: 114 new availability signals and 0 regressions across 3 regions.

VM SKUs: VM sizes now offered (114 signals; 114 net-new regional availabilities). SRE impact: more compute shapes for right-sizing, performance, and cost tuning. Coverage now ranges from 17 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: germanywestcentral · d128nds.v6; germanywestcentral · d128nlds.v6; germanywestcentral · d128nls.v6; germanywestcentral · d128ns.v6; and 110 more.

Engineering context

  • germanywestcentral vmSkus.standard.d128nds.v6 unavailable → available net-new regional availability
    unavailable 95/95 prior days (100.0%)coverage 17/64 monitored regions (26.6%, +2 regions)Europe: 6 current, 4 priorregional expansion of an existing signal
    Also newly available in germanywestcentral, switzerlandwest. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • germanywestcentral vmSkus.standard.d128nlds.v6 unavailable → available net-new regional availability
    unavailable 95/95 prior days (100.0%)coverage 17/64 monitored regions (26.6%, +2 regions)Europe: 6 current, 4 priorregional expansion of an existing signal
    Also newly available in germanywestcentral, switzerlandwest. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • germanywestcentral vmSkus.standard.d128nls.v6 unavailable → available net-new regional availability
    unavailable 95/95 prior days (100.0%)coverage 18/64 monitored regions (28.1%, +2 regions)Europe: 7 current, 5 priorregional expansion of an existing signal
    Also newly available in germanywestcentral, switzerlandwest. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • germanywestcentral vmSkus.standard.d128ns.v6 unavailable → available net-new regional availability
    unavailable 95/95 prior days (100.0%)coverage 18/64 monitored regions (28.1%, +2 regions)Europe: 7 current, 5 priorregional expansion of an existing signal
    Also newly available in germanywestcentral, switzerlandwest. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • germanywestcentral vmSkus.standard.d16nds.v6 unavailable → available net-new regional availability
    unavailable 95/95 prior days (100.0%)coverage 17/64 monitored regions (26.6%, +2 regions)Europe: 6 current, 4 priorregional expansion of an existing signal
    Also newly available in germanywestcentral, switzerlandwest. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • germanywestcentral vmSkus.standard.d16nlds.v6 unavailable → available net-new regional availability
    unavailable 95/95 prior days (100.0%)coverage 17/64 monitored regions (26.6%, +2 regions)Europe: 6 current, 4 priorregional expansion of an existing signal
    Also newly available in germanywestcentral, switzerlandwest. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • germanywestcentral vmSkus.standard.d16nls.v6 unavailable → available net-new regional availability
    unavailable 95/95 prior days (100.0%)coverage 18/64 monitored regions (28.1%, +2 regions)Europe: 7 current, 5 priorregional expansion of an existing signal
    Also newly available in germanywestcentral, switzerlandwest. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • germanywestcentral vmSkus.standard.d16ns.v6 unavailable → available net-new regional availability
    unavailable 95/95 prior days (100.0%)coverage 18/64 monitored regions (28.1%, +2 regions)Europe: 7 current, 5 priorregional expansion of an existing signal
    Also newly available in germanywestcentral, switzerlandwest. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • germanywestcentral vmSkus.standard.d2nds.v6 unavailable → available net-new regional availability
    unavailable 95/95 prior days (100.0%)coverage 17/64 monitored regions (26.6%, +2 regions)Europe: 6 current, 4 priorregional expansion of an existing signal
    Also newly available in germanywestcentral, switzerlandwest. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • germanywestcentral vmSkus.standard.d2nlds.v6 unavailable → available net-new regional availability
    unavailable 95/95 prior days (100.0%)coverage 17/64 monitored regions (26.6%, +2 regions)Europe: 6 current, 4 priorregional expansion of an existing signal
    Also newly available in germanywestcentral, switzerlandwest. 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.