Azure regional changes — 2026-07-25

· Auto summary
348 new294 regressions0 parked
Daily executive summary

Compared with the 2026-07-24 snapshot, the 2026-07-25 scan recorded 348 new listings, 294 regressions, and 0 parked unknown transitions.

Where it changed: VM SKUs: 348 new listings, 293 regressions; Azure AI models: 0 new listings, 1 regression.

Representative changes: GPT-5 1 model from OpenAI (version 2025-11-13) was no longer listed in eastasia; Basic A0 VM size was no longer listed in westus3; Basic A1 VM size was no longer listed in westus3.

What changed: 11 first recorded disappearances, 283 recurring disappearances, 114 net-new regional listings, 234 restored regional listings.

What this means: Review the 294 regressions against existing regional targets and fallbacks first; treat the 348 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-07-19 to 2026-07-25): across 7 recorded scans, there were 1,829 new listings and 831 regressions. New listings led on 6 scans; regressions led on 1.

Archived commentary and representative evidence

Latest scan: 348 new availability signals and 294 regressions across 6 regions.

Azure AI models: models/versions delisted (likely deprecation) (1 signal; 1 deprecation candidate). SRE impact: review model deployment targets and fallback model/version choices. Coverage now ranges from 31 to 31 of 64 monitored regions. Examples: eastasia · openai.gpt-5-1.2025-11-13.

VM SKUs: VM sizes withdrawn (293 signals; 10 deprecation candidates, 283 recurring disappearances, up to 3 prior disappearances). SRE impact: capacity planning and SKU fallback lists should be rechecked. Coverage now ranges from 1 to 39 of 64 monitored regions. The noisiest affected signal was unavailable 82.4% of prior observations. Examples: westus3 · basic.a0; westus3 · basic.a1; westus3 · basic.a2; westus3 · basic.a3; and 289 more.

VM SKUs: VM sizes now offered (348 signals; 114 net-new regional availabilities, 234 restored availabilities, up to 1 prior disappearance). SRE impact: more compute shapes for right-sizing, performance, and cost tuning. Coverage now ranges from 1 to 25 of 64 monitored regions. The noisiest affected signal was unavailable 100.0% of prior observations. Expansion pattern: first observed in South America; regional expansion of an existing signal; restored regional signal. Examples: brazilsouth · e128.32ads.v7; brazilsouth · e128.32as.v7; brazilsouth · e128.64ads.v7; brazilsouth · e128.64as.v7; and 344 more.

Engineering context

  • eastasia aiModels.openai.gpt-5-1.2025-11-13 available → unavailable deprecation candidate
    unavailable 0/74 prior days (0.0%)coverage 31/64 monitored regions (48.4%, -1 region)coverage removed from 3.1% of prior regionsAsia: 5 current, 6 prior
    Still available in australiaeast, brazilsouth, canadacentral, canadaeast, centralindia, centralus, and 25 more. Use this to evaluate model capabilities, regional deployment options, latency, and data residency. Azure OpenAI model availability
  • westus3 vmSkus.basic.a0 available → unavailable recurring disappearance
    unavailable 60/74 prior days (81.1%)1 prior disappearancecoverage 1/64 monitored regions (1.6%)North America: 1 current, 1 prior
    Also newly available in centralus. Still available in centralus. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • westus3 vmSkus.basic.a1 available → unavailable recurring disappearance
    unavailable 60/74 prior days (81.1%)1 prior disappearancecoverage 1/64 monitored regions (1.6%)North America: 1 current, 1 prior
    Also newly available in centralus. Still available in centralus. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • westus3 vmSkus.basic.a2 available → unavailable recurring disappearance
    unavailable 60/74 prior days (81.1%)1 prior disappearancecoverage 1/64 monitored regions (1.6%)North America: 1 current, 1 prior
    Also newly available in centralus. Still available in centralus. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • westus3 vmSkus.basic.a3 available → unavailable recurring disappearance
    unavailable 60/74 prior days (81.1%)1 prior disappearancecoverage 1/64 monitored regions (1.6%)North America: 1 current, 1 prior
    Also newly available in centralus. Still available in centralus. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • westus3 vmSkus.basic.a4 available → unavailable recurring disappearance
    unavailable 60/74 prior days (81.1%)1 prior disappearancecoverage 1/64 monitored regions (1.6%)North America: 1 current, 1 prior
    Also newly available in centralus. Still available in centralus. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • westus3 vmSkus.standard.a0 available → unavailable recurring disappearance
    unavailable 60/74 prior days (81.1%)1 prior disappearancecoverage 1/64 monitored regions (1.6%)North America: 1 current, 1 prior
    Also newly available in centralus. Still available in centralus. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • westus3 vmSkus.standard.a1 available → unavailable recurring disappearance
    unavailable 60/74 prior days (81.1%)1 prior disappearancecoverage 1/64 monitored regions (1.6%)North America: 1 current, 1 prior
    Also newly available in centralus. Still available in centralus. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • westus3 vmSkus.standard.a10 available → unavailable recurring disappearance
    unavailable 60/74 prior days (81.1%)1 prior disappearancecoverage 1/64 monitored regions (1.6%)North America: 1 current, 1 prior
    Also newly available in centralus. Still available in centralus. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • westus3 vmSkus.standard.a11 available → unavailable recurring disappearance
    unavailable 60/74 prior days (81.1%)1 prior disappearancecoverage 1/64 monitored regions (1.6%)North America: 1 current, 1 prior
    Also newly available in centralus. Still available in centralus. 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.