Azure regional changes — 2026-07-20

· Auto summary
331 new0 regressions1 parked
Daily executive summary

Compared with the 2026-07-19 snapshot, the 2026-07-20 scan recorded 331 new listings, 0 regressions, and 1 parked unknown transition.

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

Representative changes: Standard D16pds V6 VM size was newly listed in indonesiacentral; Standard D16plds V6 VM size was newly listed in indonesiacentral; Standard D16pls V6 VM size was newly listed in indonesiacentral.

What changed: 323 net-new regional listings, 8 restored regional listings.

What this means: The 331 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-14 to 2026-07-20): across 7 recorded scans, there were 1,340 new listings and 743 regressions. New listings led on 5 scans; regressions led on 2.

Archived commentary and representative evidence

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

VM SKUs: VM sizes now offered (331 signals; 323 net-new regional availabilities, 8 restored availabilities, up to 2 prior disappearances). SRE impact: more compute shapes for right-sizing, performance, and cost tuning. Coverage now ranges from 2 to 39 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: indonesiacentral · d16pds.v6; indonesiacentral · d16plds.v6; indonesiacentral · d16pls.v6; indonesiacentral · d16ps.v6; and 327 more.

Engineering context

  • indonesiacentral vmSkus.standard.d16pds.v6 unavailable → available net-new regional availability
    unavailable 69/69 prior days (100.0%)coverage 39/64 monitored regions (60.9%, +1 region)Asia: 9 current, 8 priorregional expansion of an existing signal
    Also newly available in indonesiacentral. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • indonesiacentral vmSkus.standard.d16plds.v6 unavailable → available net-new regional availability
    unavailable 69/69 prior days (100.0%)coverage 39/64 monitored regions (60.9%, +1 region)Asia: 9 current, 8 priorregional expansion of an existing signal
    Also newly available in indonesiacentral. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • indonesiacentral vmSkus.standard.d16pls.v6 unavailable → available net-new regional availability
    unavailable 69/69 prior days (100.0%)coverage 39/64 monitored regions (60.9%, +1 region)Asia: 9 current, 8 priorregional expansion of an existing signal
    Also newly available in indonesiacentral. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • indonesiacentral vmSkus.standard.d16ps.v6 unavailable → available net-new regional availability
    unavailable 69/69 prior days (100.0%)coverage 39/64 monitored regions (60.9%, +1 region)Asia: 9 current, 8 priorregional expansion of an existing signal
    Also newly available in indonesiacentral. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • indonesiacentral vmSkus.standard.d2pds.v6 unavailable → available net-new regional availability
    unavailable 69/69 prior days (100.0%)coverage 39/64 monitored regions (60.9%, +1 region)Asia: 9 current, 8 priorregional expansion of an existing signal
    Also newly available in indonesiacentral. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • indonesiacentral vmSkus.standard.d2plds.v6 unavailable → available net-new regional availability
    unavailable 69/69 prior days (100.0%)coverage 39/64 monitored regions (60.9%, +1 region)Asia: 9 current, 8 priorregional expansion of an existing signal
    Also newly available in indonesiacentral. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • indonesiacentral vmSkus.standard.d2pls.v6 unavailable → available net-new regional availability
    unavailable 69/69 prior days (100.0%)coverage 39/64 monitored regions (60.9%, +1 region)Asia: 9 current, 8 priorregional expansion of an existing signal
    Also newly available in indonesiacentral. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • indonesiacentral vmSkus.standard.d2ps.v6 unavailable → available net-new regional availability
    unavailable 69/69 prior days (100.0%)coverage 39/64 monitored regions (60.9%, +1 region)Asia: 9 current, 8 priorregional expansion of an existing signal
    Also newly available in indonesiacentral. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • indonesiacentral vmSkus.standard.d32pds.v6 unavailable → available net-new regional availability
    unavailable 69/69 prior days (100.0%)coverage 39/64 monitored regions (60.9%, +1 region)Asia: 9 current, 8 priorregional expansion of an existing signal
    Also newly available in indonesiacentral. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • indonesiacentral vmSkus.standard.d32plds.v6 unavailable → available net-new regional availability
    unavailable 69/69 prior days (100.0%)coverage 39/64 monitored regions (60.9%, +1 region)Asia: 9 current, 8 priorregional expansion of an existing signal
    Also newly available in indonesiacentral. 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.