Recurring VM SKU Instability in West US 2, New Compute Shapes in Germany

· AI summary
116 new4 regressions20 parked
Daily executive summary

Compared with the 2026-07-05 snapshot, the 2026-07-06 scan recorded 116 new listings, 4 regressions, and 20 parked unknown transitions.

Representative changes: Standard Dc1s V2 VM size was no longer listed in westus2; Standard Dc2s V2 VM size was no longer listed in westus2; Standard Dc4s V2 VM size was no longer listed in westus2.

What changed: 4 recurring disappearances, 82 net-new regional listings, 34 restored regional listings.

What this means: Review the 4 regressions against existing regional targets and fallbacks first; treat the 116 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-06-30 to 2026-07-06): across 7 recorded scans, there were 2,167 new listings and 2,878 regressions. New listings led on 4 scans; regressions led on 3.

Archived commentary and representative evidence

West US 2 is again showing recurring instability for the Standard DCv2 VM SKUs (dc1s, dc2s, dc4s, dc8s). These SKUs have disappeared for the second time in 55 days, with only a single day missing previously. SREs should revisit capacity planning and SKU fallback lists, as this pattern reduces confidence in the ongoing availability of these confidential compute shapes in the region.

Meanwhile, germanywestcentral sees a substantial restoration of the DCas/ads and ECas/ads v5 VM SKUs, with 18+ shapes returning after multiple prior disappearances. This boosts right-sizing, performance, and cost optimization options for workloads in the region, though the history of instability suggests ongoing monitoring is prudent.

Additionally, AKS extension capabilities are now available for the first time in southcentralus and southeastasia. This unlocks new managed cluster features such as GitOps, policy enforcement, and observability, expanding operational flexibility for Kubernetes clusters in these regions.

Engineering context

  • westus2 vmSkus.standard.dc1s.v2 available → unavailable recurring disappearance
    1 prior disappearance
  • westus2 vmSkus.standard.dc2s.v2 available → unavailable recurring disappearance
    1 prior disappearance
  • westus2 vmSkus.standard.dc4s.v2 available → unavailable recurring disappearance
    1 prior disappearance
  • westus2 vmSkus.standard.dc8.v2 available → unavailable recurring disappearance
    1 prior disappearance
  • germanywestcentral vmSkus.standard.dc16ads.cc.v5 unavailable → available restored availability
    2 prior disappearances
  • germanywestcentral vmSkus.standard.dc16as.cc.v5 unavailable → available restored availability
    2 prior disappearances
  • germanywestcentral vmSkus.standard.dc32ads.cc.v5 unavailable → available restored availability
    2 prior disappearances
  • germanywestcentral vmSkus.standard.dc32as.cc.v5 unavailable → available restored availability
    2 prior disappearances
  • germanywestcentral vmSkus.standard.dc48ads.cc.v5 unavailable → available restored availability
    2 prior disappearances
  • germanywestcentral vmSkus.standard.dc48as.cc.v5 unavailable → available restored availability
    2 prior disappearances

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.