Azure regional changes — 2026-07-30

· Auto summary
346 new70 regressions0 parked
Daily executive summary

Compared with the 2026-07-28 snapshot, the 2026-07-30 scan recorded 346 new listings, 70 regressions, and 0 parked unknown transitions.

Where it changed: VM SKUs: 160 new listings, 70 regressions; AKS extensions: 178 new listings, 0 regressions; Azure AI models: 8 new listings, 0 regressions.

Representative changes: Standard Dc16ads Cc V5 VM size was no longer listed in brazilsoutheast; Standard Dc16ads V5 VM size was no longer listed in brazilsoutheast; Standard Dc16as Cc V5 VM size was no longer listed in brazilsoutheast.

What changed: 4 first recorded disappearances, 66 recurring disappearances, 346 net-new regional listings.

What this means: Review the 70 regressions against existing regional targets and fallbacks first; treat the 346 new listings as 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-24 to 2026-07-30): across 6 recorded scans, there were 1,161 new listings and 770 regressions. New listings led on 5 scans; regressions led on 1.

Archived commentary and representative evidence

Latest scan: 346 new availability signals and 70 regressions across 59 regions.

VM SKUs: VM sizes withdrawn (70 signals; 4 deprecation candidates, 66 recurring disappearances). SRE impact: capacity planning and SKU fallback lists should be rechecked. Coverage now ranges from 6 to 17 of 64 monitored regions. The noisiest affected signal was unavailable 33.3% of prior observations. Examples: brazilsoutheast · dc16ads.cc.v5; brazilsoutheast · dc16ads.v5; brazilsoutheast · dc16as.cc.v5; brazilsoutheast · dc16as.v5; and 66 more.

AKS extensions: extension types now listed (178 signals; 178 net-new regional availabilities). SRE impact: new managed cluster capabilities such as GitOps, policy, or observability. Coverage now ranges from 1 to 59 of 64 monitored regions. The noisiest affected signal was unavailable 100.0% of prior observations. Expansion pattern: first observed anywhere in the monitored regions. Examples: australiacentral · kdblconsulting.kdblknowledgelayerlarge; australiacentral · kdblconsulting.kdblknowledgelayermedium; australiacentral · kdblconsulting.kdblknowledgelayersmall; australiacentral2 · kdblconsulting.kdblknowledgelayerlarge; and 174 more.

Azure AI models: newer models/versions rolling out (8 signals; 8 net-new regional availabilities). SRE impact: new regional model/version options for latency, residency, and model selection. Coverage now ranges from 2 to 6 of 64 monitored regions. The noisiest affected signal was unavailable 100.0% of prior observations. Expansion pattern: first observed anywhere in the monitored regions. Examples: canadacentral · openai.gpt-live-transcribe.2026-07-28; canadacentral · openai.gpt-transcribe.2026-07-28; centralus · openai.gpt-live-transcribe.2026-07-28; centralus · openai.gpt-transcribe.2026-07-28; and 4 more.

VM SKUs: VM sizes now offered (160 signals; 160 net-new regional availabilities). SRE impact: more compute shapes for right-sizing, performance, and cost tuning. Coverage now ranges from 19 to 20 of 64 monitored regions. The noisiest affected signal was unavailable 100.0% of prior observations. Expansion pattern: regional expansion of an existing signal. Examples: polandcentral · d128ads.v7; polandcentral · d128alds.v7; polandcentral · d128als.v7; polandcentral · d128as.v7; and 156 more.

Engineering context

  • brazilsoutheast vmSkus.standard.dc16ads.cc.v5 available → unavailable recurring disappearance
    unavailable 26/78 prior days (33.3%)coverage 10/64 monitored regions (15.6%, -1 region)coverage removed from 9.1% of prior regions
    Still available in centralindia, eastus, eastus2euap, italynorth, jioindiacentral, jioindiawest, and 4 more. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • brazilsoutheast vmSkus.standard.dc16ads.v5 available → unavailable recurring disappearance
    unavailable 26/78 prior days (33.3%)coverage 16/64 monitored regions (25.0%, -1 region)coverage removed from 5.9% of prior regions
    Still available in centralindia, centraluseuap, eastasia, eastus, eastus2euap, germanywestcentral, and 10 more. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • brazilsoutheast vmSkus.standard.dc16as.cc.v5 available → unavailable recurring disappearance
    unavailable 26/78 prior days (33.3%)coverage 10/64 monitored regions (15.6%, -1 region)coverage removed from 9.1% of prior regions
    Still available in centralindia, eastus, eastus2euap, italynorth, jioindiacentral, jioindiawest, and 4 more. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • brazilsoutheast vmSkus.standard.dc16as.v5 available → unavailable recurring disappearance
    unavailable 26/78 prior days (33.3%)coverage 17/64 monitored regions (26.6%, -1 region)coverage removed from 5.6% of prior regions
    Still available in centralindia, centraluseuap, eastasia, eastus, eastus2euap, germanywestcentral, and 11 more. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • brazilsoutheast vmSkus.standard.dc2ads.v5 available → unavailable recurring disappearance
    unavailable 26/78 prior days (33.3%)coverage 16/64 monitored regions (25.0%, -1 region)coverage removed from 5.9% of prior regions
    Still available in centralindia, centraluseuap, eastasia, eastus, eastus2euap, germanywestcentral, and 10 more. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • brazilsoutheast vmSkus.standard.dc2as.v5 available → unavailable recurring disappearance
    unavailable 26/78 prior days (33.3%)coverage 16/64 monitored regions (25.0%, -1 region)coverage removed from 5.9% of prior regions
    Still available in centralindia, centraluseuap, eastasia, eastus, eastus2euap, germanywestcentral, and 10 more. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • brazilsoutheast vmSkus.standard.dc32ads.cc.v5 available → unavailable recurring disappearance
    unavailable 26/78 prior days (33.3%)coverage 10/64 monitored regions (15.6%, -1 region)coverage removed from 9.1% of prior regions
    Still available in centralindia, eastus, eastus2euap, italynorth, jioindiacentral, jioindiawest, and 4 more. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • brazilsoutheast vmSkus.standard.dc32ads.v5 available → unavailable recurring disappearance
    unavailable 26/78 prior days (33.3%)coverage 16/64 monitored regions (25.0%, -1 region)coverage removed from 5.9% of prior regions
    Still available in centralindia, centraluseuap, eastasia, eastus, eastus2euap, germanywestcentral, and 10 more. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • brazilsoutheast vmSkus.standard.dc32as.cc.v5 available → unavailable recurring disappearance
    unavailable 26/78 prior days (33.3%)coverage 10/64 monitored regions (15.6%, -1 region)coverage removed from 9.1% of prior regions
    Still available in centralindia, eastus, eastus2euap, italynorth, jioindiacentral, jioindiawest, and 4 more. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • brazilsoutheast vmSkus.standard.dc32as.v5 available → unavailable recurring disappearance
    unavailable 26/78 prior days (33.3%)coverage 16/64 monitored regions (25.0%, -1 region)coverage removed from 5.9% of prior regions
    Still available in centralindia, centraluseuap, eastasia, eastus, eastus2euap, germanywestcentral, and 10 more. 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.