Azure regional changes — 2026-08-27

· Auto summary
108 new195 regressions0 parked
Daily executive summary

Compared with the 2026-08-26 snapshot, the 2026-08-27 scan recorded 108 new listings, 195 regressions, and 0 parked unknown transitions.

Where it changed: VM SKUs: 0 new listings, 195 regressions; Azure AI models: 69 new listings, 0 regressions; AKS extensions: 39 new listings, 0 regressions.

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

What changed: 62 first recorded disappearances, 133 recurring disappearances, 108 net-new regional listings.

What this means: Review the 195 regressions against existing regional targets and fallbacks first; treat the 108 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-21 to 2026-08-27): across 6 recorded scans, there were 1,182 new listings and 204 regressions. New listings led on 5 scans; regressions led on 1.

Archived commentary and representative evidence

Latest scan: 108 new availability signals and 195 regressions across 33 regions.

VM SKUs: VM sizes withdrawn (195 signals; 62 deprecation candidates, 133 recurring disappearances, up to 1 prior disappearance). SRE impact: capacity planning and SKU fallback lists should be rechecked. Coverage now ranges from 1 to 17 of 64 monitored regions. The noisiest affected signal was unavailable 99.0% of prior observations. Examples: westeurope · Azure virtual-machine size for right-sizing compute (basic.a0); westeurope · Azure virtual-machine size for right-sizing compute (basic.a1); westeurope · Azure virtual-machine size for right-sizing compute (basic.a2); westeurope · Azure virtual-machine size for right-sizing compute (basic.a3); and 191 more.

AKS extensions: extension types now listed (39 signals; 39 net-new regional availabilities). SRE impact: new managed cluster capabilities such as GitOps, policy, or observability. Coverage now ranges from 10 to 58 of 64 monitored regions. The noisiest affected signal was unavailable 100.0% of prior observations. Expansion pattern: first observed anywhere in the monitored regions; regional expansion of an existing signal. Examples: centralus · AKS cluster extension type for managed cluster capabilities (microsoft.test.prasanna.1pbilling); centralus · AKS cluster extension type for managed cluster capabilities (microsoft.test.prasanna.1pbilling2); eastasia · AKS cluster extension type for managed cluster capabilities (microsoft.test.prasanna.1pbilling); eastasia · AKS cluster extension type for managed cluster capabilities (microsoft.test.prasanna.1pbilling2); and 35 more.

Azure AI models: newer models/versions rolling out (69 signals; 69 net-new regional availabilities). SRE impact: new regional model/version options for latency, residency, and model selection. Coverage now ranges from 9 to 31 of 64 monitored regions. The noisiest affected signal was unavailable 100.0% of prior observations. Expansion pattern: first observed in Africa; first observed in Asia; first observed in Middle East; first observed in Oceania; first observed in South America; regional expansion of an existing signal. Examples: australiaeast · Azure AI model/version catalog entry for model selection (cohere.cohere-parse-v5.1); brazilsouth · Azure AI model/version catalog entry for model selection (cohere.cohere-parse-v5.1); canadacentral · Azure AI model/version catalog entry for model selection (cohere.cohere-parse-v5.1); canadaeast · Azure AI model/version catalog entry for model selection (cohere.cohere-parse-v5.1); and 65 more.

What this means for Azure users: review placement and fallback plans using these catalog/list signals before changing production deployments.

Engineering context

  • westeurope vmSkus.basic.a0 available → unavailable recurring disappearance
    unavailable 103/105 prior days (98.1%)1 prior disappearancecoverage 1/64 monitored regions (1.6%, -1 region)coverage removed from 50.0% of prior regions
    Still available in indonesiacentral. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • westeurope vmSkus.basic.a1 available → unavailable recurring disappearance
    unavailable 103/105 prior days (98.1%)1 prior disappearancecoverage 1/64 monitored regions (1.6%, -1 region)coverage removed from 50.0% of prior regions
    Still available in indonesiacentral. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • westeurope vmSkus.basic.a2 available → unavailable recurring disappearance
    unavailable 103/105 prior days (98.1%)1 prior disappearancecoverage 1/64 monitored regions (1.6%, -1 region)coverage removed from 50.0% of prior regions
    Still available in indonesiacentral. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • westeurope vmSkus.basic.a3 available → unavailable recurring disappearance
    unavailable 103/105 prior days (98.1%)1 prior disappearancecoverage 1/64 monitored regions (1.6%, -1 region)coverage removed from 50.0% of prior regions
    Still available in indonesiacentral. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • westeurope vmSkus.basic.a4 available → unavailable recurring disappearance
    unavailable 103/105 prior days (98.1%)1 prior disappearancecoverage 1/64 monitored regions (1.6%, -1 region)coverage removed from 50.0% of prior regions
    Still available in indonesiacentral. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • westeurope vmSkus.standard.a0 available → unavailable recurring disappearance
    unavailable 103/105 prior days (98.1%)1 prior disappearancecoverage 1/64 monitored regions (1.6%, -1 region)coverage removed from 50.0% of prior regions
    Still available in indonesiacentral. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • westeurope vmSkus.standard.a1 available → unavailable recurring disappearance
    unavailable 103/105 prior days (98.1%)1 prior disappearancecoverage 1/64 monitored regions (1.6%, -1 region)coverage removed from 50.0% of prior regions
    Still available in indonesiacentral. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • westeurope vmSkus.standard.a10 available → unavailable recurring disappearance
    unavailable 103/105 prior days (98.1%)1 prior disappearancecoverage 1/64 monitored regions (1.6%, -1 region)coverage removed from 50.0% of prior regions
    Still available in indonesiacentral. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • westeurope vmSkus.standard.a11 available → unavailable recurring disappearance
    unavailable 103/105 prior days (98.1%)1 prior disappearancecoverage 1/64 monitored regions (1.6%, -1 region)coverage removed from 50.0% of prior regions
    Still available in indonesiacentral. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • westeurope vmSkus.standard.a2 available → unavailable recurring disappearance
    unavailable 103/105 prior days (98.1%)1 prior disappearancecoverage 1/64 monitored regions (1.6%, -1 region)coverage removed from 50.0% of prior regions
    Still available in indonesiacentral. 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.