Azure regional changes — 2026-07-19

· Auto summary
66 new0 regressions0 parked
Daily executive summary

Compared with the 2026-07-18 snapshot, the 2026-07-19 scan recorded 66 new listings, 0 regressions, and 0 parked unknown transitions.

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

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

What changed: 66 restored regional listings.

What this means: The 66 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-07-13 to 2026-07-19): across 7 recorded scans, there were 1,009 new listings and 910 regressions. New listings led on 4 scans; regressions led on 3.

Archived commentary and representative evidence

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

VM SKUs: VM sizes now offered (66 signals; 66 restored availabilities, up to 2 prior disappearances). SRE impact: more compute shapes for right-sizing, performance, and cost tuning. Coverage now ranges from 12 to 19 of 64 monitored regions. The noisiest affected signal was unavailable 95.6% of prior observations. Expansion pattern: restored regional signal. Examples: southcentralus · dc16ads.cc.v5; southcentralus · dc16ads.v5; southcentralus · dc16as.cc.v5; southcentralus · dc16as.v5; and 62 more.

Engineering context

  • southcentralus vmSkus.standard.dc16ads.cc.v5 unavailable → available restored availability
    unavailable 65/68 prior days (95.6%)2 prior disappearancescoverage 12/64 monitored regions (18.8%, +1 region)North America: 5 current, 4 priorrestored regional signal
    Also newly available in southcentralus. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • southcentralus vmSkus.standard.dc16ads.v5 unavailable → available restored availability
    unavailable 65/68 prior days (95.6%)2 prior disappearancescoverage 18/64 monitored regions (28.1%, +1 region)North America: 6 current, 5 priorrestored regional signal
    Also newly available in southcentralus. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • southcentralus vmSkus.standard.dc16as.cc.v5 unavailable → available restored availability
    unavailable 65/68 prior days (95.6%)2 prior disappearancescoverage 12/64 monitored regions (18.8%, +1 region)North America: 5 current, 4 priorrestored regional signal
    Also newly available in southcentralus. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • southcentralus vmSkus.standard.dc16as.v5 unavailable → available restored availability
    unavailable 65/68 prior days (95.6%)2 prior disappearancescoverage 19/64 monitored regions (29.7%, +1 region)North America: 6 current, 5 priorrestored regional signal
    Also newly available in southcentralus. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • southcentralus vmSkus.standard.dc2ads.v5 unavailable → available restored availability
    unavailable 65/68 prior days (95.6%)2 prior disappearancescoverage 18/64 monitored regions (28.1%, +1 region)North America: 6 current, 5 priorrestored regional signal
    Also newly available in southcentralus. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • southcentralus vmSkus.standard.dc2as.v5 unavailable → available restored availability
    unavailable 65/68 prior days (95.6%)2 prior disappearancescoverage 18/64 monitored regions (28.1%, +1 region)North America: 6 current, 5 priorrestored regional signal
    Also newly available in southcentralus. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • southcentralus vmSkus.standard.dc32ads.cc.v5 unavailable → available restored availability
    unavailable 65/68 prior days (95.6%)2 prior disappearancescoverage 12/64 monitored regions (18.8%, +1 region)North America: 5 current, 4 priorrestored regional signal
    Also newly available in southcentralus. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • southcentralus vmSkus.standard.dc32ads.v5 unavailable → available restored availability
    unavailable 65/68 prior days (95.6%)2 prior disappearancescoverage 18/64 monitored regions (28.1%, +1 region)North America: 6 current, 5 priorrestored regional signal
    Also newly available in southcentralus. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • southcentralus vmSkus.standard.dc32as.cc.v5 unavailable → available restored availability
    unavailable 65/68 prior days (95.6%)2 prior disappearancescoverage 12/64 monitored regions (18.8%, +1 region)North America: 5 current, 4 priorrestored regional signal
    Also newly available in southcentralus. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • southcentralus vmSkus.standard.dc32as.v5 unavailable → available restored availability
    unavailable 65/68 prior days (95.6%)2 prior disappearancescoverage 18/64 monitored regions (28.1%, +1 region)North America: 6 current, 5 priorrestored regional signal
    Also newly available in southcentralus. 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.