Azure regional changes — 2026-08-05

· Auto summary
162 new578 regressions801 parked
Daily executive summary

Compared with the 2026-08-04 snapshot, the 2026-08-05 scan recorded 162 new listings, 578 regressions, and 801 parked unknown transitions.

Where it changed: VM SKUs: 162 new listings, 566 regressions; Azure AI models: 0 new listings, 12 regressions.

Representative changes: model router model from OpenAI (version 2025-05-19) was no longer listed in 4 regions; model router model from OpenAI (version 2025-08-07) was no longer listed in 4 regions; model router model from OpenAI (version 2025-11-18) was no longer listed in 4 regions.

What changed: 12 first recorded disappearances, 566 recurring disappearances, 66 net-new regional listings, 96 restored regional listings.

What this means: Review the 578 regressions against existing regional targets and fallbacks first; treat the 162 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-30 to 2026-08-05): across 7 recorded scans, there were 1,661 new listings and 1,058 regressions. New listings led on 3 scans; regressions led on 2.

Archived commentary and representative evidence

Latest scan: 162 new availability signals and 578 regressions across 9 regions.

Azure AI models: models/versions delisted (likely deprecation) (12 signals; 12 deprecation candidates). SRE impact: review model deployment targets and fallback model/version choices. Coverage now ranges from 25 to 25 of 64 monitored regions. The noisiest affected signal was unavailable 84.5% of prior observations. Examples: canadacentral · openai.model-router.2025-05-19; canadacentral · openai.model-router.2025-08-07; canadacentral · openai.model-router.2025-11-18; northeurope · openai.model-router.2025-05-19; and 8 more.

VM SKUs: VM sizes withdrawn (566 signals; 566 recurring disappearances, up to 2 prior disappearances). SRE impact: capacity planning and SKU fallback lists should be rechecked. Coverage now ranges from 0 to 25 of 64 monitored regions. The noisiest affected signal was unavailable 97.6% of prior observations. Examples: centralus · dc16ads.cc.v5; centralus · dc16ads.v5; centralus · dc16as.cc.v5; centralus · dc16as.v5; and 562 more.

VM SKUs: VM sizes now offered (162 signals; 66 net-new regional availabilities, 96 restored availabilities, up to 1 prior disappearance). SRE impact: more compute shapes for right-sizing, performance, and cost tuning. Coverage now ranges from 13 to 19 of 64 monitored regions. The noisiest affected signal was unavailable 96.4% of prior observations. Expansion pattern: regional expansion of an existing signal; restored regional signal. Examples: southindia · dc16ads.cc.v5; southindia · dc16ads.v5; southindia · dc16as.cc.v5; southindia · dc16as.v5; and 158 more.

Engineering context

  • canadacentral aiModels.openai.model-router.2025-05-19 available → unavailable deprecation candidate
    unavailable 71/84 prior days (84.5%)coverage 25/64 monitored regions (39.1%, -4 regions)coverage removed from 13.8% of prior regionsNorth America: 8 current, 9 prior
    Still available in australiaeast, brazilsouth, canadaeast, centralus, eastus, eastus2, and 19 more. Use this to evaluate model capabilities, regional deployment options, latency, and data residency. Azure OpenAI model availability
  • canadacentral aiModels.openai.model-router.2025-08-07 available → unavailable deprecation candidate
    unavailable 71/84 prior days (84.5%)coverage 25/64 monitored regions (39.1%, -4 regions)coverage removed from 13.8% of prior regionsNorth America: 8 current, 9 prior
    Still available in australiaeast, brazilsouth, canadaeast, centralus, eastus, eastus2, and 19 more. Use this to evaluate model capabilities, regional deployment options, latency, and data residency. Azure OpenAI model availability
  • canadacentral aiModels.openai.model-router.2025-11-18 available → unavailable deprecation candidate
    unavailable 71/84 prior days (84.5%)coverage 25/64 monitored regions (39.1%, -4 regions)coverage removed from 13.8% of prior regionsNorth America: 8 current, 9 prior
    Still available in australiaeast, brazilsouth, canadaeast, centralus, eastus, eastus2, and 19 more. Use this to evaluate model capabilities, regional deployment options, latency, and data residency. Azure OpenAI model availability
  • centralus vmSkus.standard.dc16ads.cc.v5 available → unavailable recurring disappearance
    unavailable 58/84 prior days (69.0%)2 prior disappearancescoverage 13/64 monitored regions (20.3%, +1 region)North America: 3 current, 5 prior
    Also newly available in southindia, switzerlandnorth, uksouth. Still available in centralindia, eastus, eastus2euap, italynorth, jioindiacentral, jioindiawest, and 7 more. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • centralus vmSkus.standard.dc16ads.v5 available → unavailable recurring disappearance
    unavailable 58/84 prior days (69.0%)2 prior disappearancescoverage 18/64 monitored regions (28.1%)North America: 4 current, 6 prior
    Also newly available in southindia, uksouth. Still available in centralindia, centraluseuap, eastasia, eastus, eastus2euap, germanywestcentral, and 12 more. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • centralus vmSkus.standard.dc16as.cc.v5 available → unavailable recurring disappearance
    unavailable 58/84 prior days (69.0%)2 prior disappearancescoverage 13/64 monitored regions (20.3%, +1 region)North America: 3 current, 5 prior
    Also newly available in southindia, switzerlandnorth, uksouth. Still available in centralindia, eastus, eastus2euap, italynorth, jioindiacentral, jioindiawest, and 7 more. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • centralus vmSkus.standard.dc16as.v5 available → unavailable recurring disappearance
    unavailable 58/84 prior days (69.0%)2 prior disappearancescoverage 19/64 monitored regions (29.7%)North America: 4 current, 6 prior
    Also newly available in southindia, uksouth. Still available in centralindia, centraluseuap, eastasia, eastus, eastus2euap, germanywestcentral, and 13 more. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • centralus vmSkus.standard.dc2ads.v5 available → unavailable recurring disappearance
    unavailable 58/84 prior days (69.0%)2 prior disappearancescoverage 18/64 monitored regions (28.1%)North America: 4 current, 6 prior
    Also newly available in southindia, uksouth. Still available in centralindia, centraluseuap, eastasia, eastus, eastus2euap, germanywestcentral, and 12 more. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • centralus vmSkus.standard.dc2as.v5 available → unavailable recurring disappearance
    unavailable 58/84 prior days (69.0%)2 prior disappearancescoverage 18/64 monitored regions (28.1%)North America: 4 current, 6 prior
    Also newly available in southindia, uksouth. Still available in centralindia, centraluseuap, eastasia, eastus, eastus2euap, germanywestcentral, and 12 more. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • centralus vmSkus.standard.dc32ads.cc.v5 available → unavailable recurring disappearance
    unavailable 58/84 prior days (69.0%)2 prior disappearancescoverage 13/64 monitored regions (20.3%, +1 region)North America: 3 current, 5 prior
    Also newly available in southindia, switzerlandnorth, uksouth. Still available in centralindia, eastus, eastus2euap, italynorth, jioindiacentral, jioindiawest, and 7 more. 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.