Azure regional changes — 2026-08-18

· Auto summary
78 new238 regressions0 parked
Daily executive summary

Compared with the 2026-08-17 snapshot, the 2026-08-18 scan recorded 78 new listings, 238 regressions, and 0 parked unknown transitions.

Where it changed: VM SKUs: 77 new listings, 238 regressions; AKS extensions: 1 new listing, 0 regressions.

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

What changed: 238 recurring disappearances, 78 net-new regional listings.

What this means: Review the 238 regressions against existing regional targets and fallbacks first; treat the 78 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-12 to 2026-08-18): across 7 recorded scans, there were 1,841 new listings and 1,032 regressions. New listings led on 4 scans; regressions led on 3.

Archived commentary and representative evidence

Latest scan: 78 new availability signals and 238 regressions across 5 regions.

VM SKUs: VM sizes withdrawn (238 signals; 238 recurring disappearances, up to 3 prior disappearances). SRE impact: capacity planning and SKU fallback lists should be rechecked. Coverage now ranges from 1 to 25 of 64 monitored regions. The noisiest affected signal was unavailable 73.2% of prior observations. Examples: centralus · basic.a0; centralus · basic.a1; centralus · basic.a2; centralus · basic.a3; and 234 more.

AKS extensions: extension types now listed (1 signal; 1 net-new regional availability). 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 51.5% of prior observations. Expansion pattern: regional expansion of an existing signal. Examples: uaecentral · microsoft.azuremonitor.appmonitoring.

VM SKUs: VM sizes now offered (77 signals; 77 net-new regional availabilities). SRE impact: more compute shapes for right-sizing, performance, and cost tuning. Coverage now ranges from 17 to 32 of 64 monitored regions. The noisiest affected signal was unavailable 100.0% of prior observations. Expansion pattern: regional expansion of an existing signal. Examples: chilecentral · m128.64bds.3.v3; chilecentral · m128.64bds.v3; chilecentral · m128.64bs.v3; chilecentral · m128bds.3.v3; and 73 more.

Engineering context

  • centralus vmSkus.basic.a0 available → unavailable recurring disappearance
    unavailable 71/97 prior days (73.2%)2 prior disappearancescoverage 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
  • centralus vmSkus.basic.a1 available → unavailable recurring disappearance
    unavailable 71/97 prior days (73.2%)2 prior disappearancescoverage 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
  • centralus vmSkus.basic.a2 available → unavailable recurring disappearance
    unavailable 71/97 prior days (73.2%)2 prior disappearancescoverage 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
  • centralus vmSkus.basic.a3 available → unavailable recurring disappearance
    unavailable 71/97 prior days (73.2%)2 prior disappearancescoverage 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
  • centralus vmSkus.basic.a4 available → unavailable recurring disappearance
    unavailable 71/97 prior days (73.2%)2 prior disappearancescoverage 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
  • centralus vmSkus.standard.a0 available → unavailable recurring disappearance
    unavailable 71/97 prior days (73.2%)2 prior disappearancescoverage 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
  • centralus vmSkus.standard.a1 available → unavailable recurring disappearance
    unavailable 71/97 prior days (73.2%)2 prior disappearancescoverage 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
  • centralus vmSkus.standard.a10 available → unavailable recurring disappearance
    unavailable 71/97 prior days (73.2%)2 prior disappearancescoverage 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
  • centralus vmSkus.standard.a11 available → unavailable recurring disappearance
    unavailable 71/97 prior days (73.2%)2 prior disappearancescoverage 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
  • centralus vmSkus.standard.a2 available → unavailable recurring disappearance
    unavailable 71/97 prior days (73.2%)2 prior disappearancescoverage 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.