Azure regional changes — 2026-08-14

· Auto summary
65 new259 regressions0 parked
Daily executive summary

Compared with the 2026-08-13 snapshot, the 2026-08-14 scan recorded 65 new listings, 259 regressions, and 0 parked unknown transitions.

Where it changed: VM SKUs: 4 new listings, 259 regressions; AKS extensions: 60 new listings, 0 regressions; Azure model latency: 1 new listing, 0 regressions.

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

What changed: 123 first recorded disappearances, 136 recurring disappearances, 61 net-new regional listings, 4 restored regional listings.

What this means: Review the 259 regressions against existing regional targets and fallbacks first; treat the 65 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-08-08 to 2026-08-14): across 7 recorded scans, there were 2,282 new listings and 569 regressions. New listings led on 5 scans; regressions led on 2.

Archived commentary and representative evidence

Latest scan: 65 new availability signals and 259 regressions across 59 regions.

VM SKUs: VM sizes withdrawn (259 signals; 123 deprecation candidates, 136 recurring disappearances, up to 3 prior disappearances). SRE impact: capacity planning and SKU fallback lists should be rechecked. Coverage now ranges from 2 to 19 of 64 monitored regions. The noisiest affected signal was unavailable 98.9% of prior observations. Examples: brazilsouth · dc16ads.cc.v5; brazilsouth · dc16ads.v5; brazilsouth · dc16as.cc.v5; brazilsouth · dc16as.v5; and 255 more.

AKS extensions: extension types now listed (60 signals; 60 net-new regional availabilities). SRE impact: new managed cluster capabilities such as GitOps, policy, or observability. Coverage now ranges from 59 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; first observed in this geography. Examples: australiacentral · microsoft.kubernetesupgradeinsights; australiacentral2 · microsoft.kubernetesupgradeinsights; australiaeast · microsoft.kubernetesupgradeinsights; australiasoutheast · microsoft.kubernetesupgradeinsights; and 56 more.

Azure model latency: started measuring new model/region deployments (1 signal; 1 net-new regional availability). SRE impact: new measured deployment paths for latency-aware routing decisions. Coverage now ranges from 9 to 9 of 64 monitored regions. The noisiest affected signal was unavailable 100.0% of prior observations. Expansion pattern: regional expansion of an existing signal. Examples: switzerlandnorth · openai.gpt-5.1.

VM SKUs: VM sizes now offered (4 signals; 4 restored availabilities, up to 1 prior disappearance). SRE impact: more compute shapes for right-sizing, performance, and cost tuning. Coverage now ranges from 5 to 5 of 64 monitored regions. The noisiest affected signal was unavailable 37.6% of prior observations. Expansion pattern: restored regional signal. Examples: westeurope · dc1s.v2; westeurope · dc2s.v2; westeurope · dc4s.v2; westeurope · dc8.v2.

Engineering context

  • brazilsouth vmSkus.standard.dc16ads.cc.v5 available → unavailable recurring disappearance
    unavailable 87/93 prior days (93.5%)1 prior disappearancecoverage 12/64 monitored regions (18.8%, -2 regions)coverage removed from 14.3% of prior regions
    Still available in centralindia, eastus, eastus2euap, indonesiacentral, italynorth, jioindiacentral, and 6 more. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • brazilsouth vmSkus.standard.dc16ads.v5 available → unavailable recurring disappearance
    unavailable 87/93 prior days (93.5%)1 prior disappearancecoverage 18/64 monitored regions (28.1%, -2 regions)coverage removed from 10.0% of prior regions
    Still available in centralindia, centraluseuap, eastasia, eastus, eastus2euap, germanywestcentral, and 12 more. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • brazilsouth vmSkus.standard.dc16as.cc.v5 available → unavailable recurring disappearance
    unavailable 87/93 prior days (93.5%)1 prior disappearancecoverage 12/64 monitored regions (18.8%, -2 regions)coverage removed from 14.3% of prior regions
    Still available in centralindia, eastus, eastus2euap, indonesiacentral, italynorth, jioindiacentral, and 6 more. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • brazilsouth vmSkus.standard.dc16as.v5 available → unavailable recurring disappearance
    unavailable 87/93 prior days (93.5%)1 prior disappearancecoverage 19/64 monitored regions (29.7%, -2 regions)coverage removed from 9.5% of prior regions
    Still available in centralindia, centraluseuap, eastasia, eastus, eastus2euap, germanywestcentral, and 13 more. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • brazilsouth vmSkus.standard.dc2ads.v5 available → unavailable recurring disappearance
    unavailable 87/93 prior days (93.5%)1 prior disappearancecoverage 18/64 monitored regions (28.1%, -2 regions)coverage removed from 10.0% of prior regions
    Still available in centralindia, centraluseuap, eastasia, eastus, eastus2euap, germanywestcentral, and 12 more. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • brazilsouth vmSkus.standard.dc2as.v5 available → unavailable recurring disappearance
    unavailable 87/93 prior days (93.5%)1 prior disappearancecoverage 18/64 monitored regions (28.1%, -2 regions)coverage removed from 10.0% of prior regions
    Still available in centralindia, centraluseuap, eastasia, eastus, eastus2euap, germanywestcentral, and 12 more. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • brazilsouth vmSkus.standard.dc32ads.cc.v5 available → unavailable recurring disappearance
    unavailable 87/93 prior days (93.5%)1 prior disappearancecoverage 12/64 monitored regions (18.8%, -2 regions)coverage removed from 14.3% of prior regions
    Still available in centralindia, eastus, eastus2euap, indonesiacentral, italynorth, jioindiacentral, and 6 more. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • brazilsouth vmSkus.standard.dc32ads.v5 available → unavailable recurring disappearance
    unavailable 87/93 prior days (93.5%)1 prior disappearancecoverage 18/64 monitored regions (28.1%, -2 regions)coverage removed from 10.0% of prior regions
    Still available in centralindia, centraluseuap, eastasia, eastus, eastus2euap, germanywestcentral, and 12 more. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • brazilsouth vmSkus.standard.dc32as.cc.v5 available → unavailable recurring disappearance
    unavailable 87/93 prior days (93.5%)1 prior disappearancecoverage 12/64 monitored regions (18.8%, -2 regions)coverage removed from 14.3% of prior regions
    Still available in centralindia, eastus, eastus2euap, indonesiacentral, italynorth, jioindiacentral, and 6 more. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • brazilsouth vmSkus.standard.dc32as.v5 available → unavailable recurring disappearance
    unavailable 87/93 prior days (93.5%)1 prior disappearancecoverage 18/64 monitored regions (28.1%, -2 regions)coverage removed from 10.0% of prior regions
    Still available in centralindia, centraluseuap, eastasia, eastus, eastus2euap, germanywestcentral, and 12 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.