Azure regional changes — 2026-06-28

· AI summary
116 new451 regressions7,855 parked
Daily executive summary

Compared with the 2026-06-27 snapshot, the 2026-06-28 scan recorded 116 new listings, 451 regressions, and 7,855 parked unknown transitions.

Representative changes: Basic A0 VM size was no longer listed in australiasoutheast; Basic A1 VM size was no longer listed in australiasoutheast; Basic A2 VM size was no longer listed in australiasoutheast.

What this means: Review the 451 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-22 to 2026-06-28): across 7 recorded scans, there were 1,724 new listings and 863 regressions. New listings led on 5 scans; regressions led on 2.

Archived commentary and representative evidence

In the Australia Southeast region, all VM SKUs under both basic and standard modalities have stopped being available, including features from a0 to a4 and a variety of standard features such as b16pls.v2, d128ds.v7, and d16s.v7.

Engineering context

  • australiasoutheast vmSkus.basic.a0 available → unavailable
  • australiasoutheast vmSkus.basic.a1 available → unavailable
  • australiasoutheast vmSkus.basic.a2 available → unavailable
  • australiasoutheast vmSkus.basic.a3 available → unavailable
  • australiasoutheast vmSkus.basic.a4 available → unavailable
  • australiasoutheast vmSkus.standard.a0 available → unavailable
  • australiasoutheast vmSkus.standard.a1 available → unavailable
  • australiasoutheast vmSkus.standard.a10 available → unavailable
  • australiasoutheast vmSkus.standard.a11 available → unavailable
  • australiasoutheast vmSkus.standard.a2 available → unavailable

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.