Azure regional changes — 2026-08-21

· Auto summary
250 new0 regressions0 parked
Daily executive summary

Compared with the 2026-08-20 snapshot, the 2026-08-21 scan recorded 250 new listings, 0 regressions, and 0 parked unknown transitions.

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

Representative changes: Standard D248ds V7 VM size was newly listed in 4 regions; Standard D248lds V7 VM size was newly listed in 4 regions; Standard D248ls V7 VM size was newly listed in 4 regions.

What changed: 250 net-new regional listings.

What this means: The 250 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-15 to 2026-08-21): across 7 recorded scans, there were 1,130 new listings and 559 regressions. New listings led on 5 scans; regressions led on 2.

Archived commentary and representative evidence

Latest scan: 250 new availability signals and 0 regressions across 5 regions.

VM SKUs: VM sizes now offered (250 signals; 250 net-new regional availabilities). SRE impact: more compute shapes for right-sizing, performance, and cost tuning. Coverage now ranges from 3 to 24 of 64 monitored regions. The noisiest affected signal was unavailable 100.0% of prior observations. Expansion pattern: first observed anywhere in the monitored regions; regional expansion of an existing signal. Examples: centralus · d248ds.v7; centralus · d248lds.v7; centralus · d248ls.v7; centralus · d248s.v7; and 246 more.

Engineering context

  • centralus vmSkus.standard.d248ds.v7 None → available net-new regional availability
    unavailable 100/100 prior days (100.0%)coverage 4/64 monitored regions (6.2%, +4 regions)North America: 2 current, 0 priorfirst observed anywhere in the monitored regions
    Also newly available in centralus, germanywestcentral, swedencentral, westus2. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • centralus vmSkus.standard.d248lds.v7 None → available net-new regional availability
    unavailable 100/100 prior days (100.0%)coverage 4/64 monitored regions (6.2%, +4 regions)North America: 2 current, 0 priorfirst observed anywhere in the monitored regions
    Also newly available in centralus, germanywestcentral, swedencentral, westus2. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • centralus vmSkus.standard.d248ls.v7 None → available net-new regional availability
    unavailable 100/100 prior days (100.0%)coverage 4/64 monitored regions (6.2%, +4 regions)North America: 2 current, 0 priorfirst observed anywhere in the monitored regions
    Also newly available in centralus, germanywestcentral, swedencentral, westus2. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • centralus vmSkus.standard.d248s.v7 None → available net-new regional availability
    unavailable 100/100 prior days (100.0%)coverage 4/64 monitored regions (6.2%, +4 regions)North America: 2 current, 0 priorfirst observed anywhere in the monitored regions
    Also newly available in centralus, germanywestcentral, swedencentral, westus2. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • centralus vmSkus.standard.d372ds.v7 None → available net-new regional availability
    unavailable 100/100 prior days (100.0%)coverage 4/64 monitored regions (6.2%, +4 regions)North America: 2 current, 0 priorfirst observed anywhere in the monitored regions
    Also newly available in centralus, germanywestcentral, swedencentral, westus2. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • centralus vmSkus.standard.d372s.v7 None → available net-new regional availability
    unavailable 100/100 prior days (100.0%)coverage 4/64 monitored regions (6.2%, +4 regions)North America: 2 current, 0 priorfirst observed anywhere in the monitored regions
    Also newly available in centralus, germanywestcentral, swedencentral, westus2. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • centralus vmSkus.standard.e248ds.v7 None → available net-new regional availability
    unavailable 100/100 prior days (100.0%)coverage 3/64 monitored regions (4.7%, +3 regions)North America: 1 current, 0 priorfirst observed anywhere in the monitored regions
    Also newly available in centralus, germanywestcentral, swedencentral. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • centralus vmSkus.standard.e248s.v7 None → available net-new regional availability
    unavailable 100/100 prior days (100.0%)coverage 3/64 monitored regions (4.7%, +3 regions)North America: 1 current, 0 priorfirst observed anywhere in the monitored regions
    Also newly available in centralus, germanywestcentral, swedencentral. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • centralus vmSkus.standard.e372ids.v7 None → available net-new regional availability
    unavailable 100/100 prior days (100.0%)coverage 3/64 monitored regions (4.7%, +3 regions)North America: 1 current, 0 priorfirst observed anywhere in the monitored regions
    Also newly available in centralus, germanywestcentral, swedencentral. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • centralus vmSkus.standard.e372is.v7 None → available net-new regional availability
    unavailable 100/100 prior days (100.0%)coverage 3/64 monitored regions (4.7%, +3 regions)North America: 1 current, 0 priorfirst observed anywhere in the monitored regions
    Also newly available in centralus, germanywestcentral, swedencentral. 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.