West US DCv2 VM SKUs Delisted, Canada East Sees DC/ECv5 Restorations

· AI summary
70 new4 regressions0 parked
Daily executive summary

Compared with the 2026-07-04 snapshot, the 2026-07-05 scan recorded 70 new listings, 4 regressions, and 0 parked unknown transitions.

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

What changed: 4 first recorded disappearances, 70 restored regional listings.

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

Archived commentary and representative evidence

Four DCv2 VM SKUs (dc1s.v2, dc2s.v2, dc4s.v2, dc8.v2) are now absent from the West US catalog after 54 days of uninterrupted availability. This marks them as likely deprecation candidates. SREs should immediately revisit capacity planning and SKU fallback strategies for West US, as these shapes can no longer be assumed available for new deployments or scaling.

Meanwhile, Canada East has restored a broad set of DCv5 and ECv5 VM SKUs, including both standard and confidential compute variants. Each SKU returns after a prior disappearance, offering more compute shapes for right-sizing, performance optimization, and cost tuning. This expansion enhances placement flexibility in Canada East, but the recent history of missing days suggests SREs should monitor for stability before relying on these SKUs for critical workloads.

Engineering context

  • westus vmSkus.standard.dc1s.v2 available → unavailable deprecation candidate
  • westus vmSkus.standard.dc2s.v2 available → unavailable deprecation candidate
  • westus vmSkus.standard.dc4s.v2 available → unavailable deprecation candidate
  • westus vmSkus.standard.dc8.v2 available → unavailable deprecation candidate
  • canadaeast vmSkus.standard.dc16ads.cc.v5 unavailable → available restored availability
    1 prior disappearance
  • canadaeast vmSkus.standard.dc16ads.v5 unavailable → available restored availability
    1 prior disappearance
  • canadaeast vmSkus.standard.dc16as.cc.v5 unavailable → available restored availability
    1 prior disappearance
  • canadaeast vmSkus.standard.dc16as.v5 unavailable → available restored availability
    1 prior disappearance
  • canadaeast vmSkus.standard.dc2ads.v5 unavailable → available restored availability
    1 prior disappearance
  • canadaeast vmSkus.standard.dc2as.v5 unavailable → available restored availability
    1 prior disappearance

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.