Azure regional changes — 2026-08-06

· Auto summary
59 new72 regressions0 parked
Daily executive summary

Compared with the 2026-08-05 snapshot, the 2026-08-06 scan recorded 59 new listings, 72 regressions, and 0 parked unknown transitions.

Where it changed: VM SKUs: 0 new listings, 68 regressions; AKS extensions: 59 new listings, 0 regressions; Azure AI models: 0 new listings, 4 regressions.

Representative changes: GPT-5 2 codex model from OpenAI (version 2026-01-14) was no longer listed in 2 regions; GPT-5 3 codex model from OpenAI (version 2026-02-24) was no longer listed in 2 regions; Standard D1 VM size was no longer listed in 2 regions.

What changed: 38 first recorded disappearances, 34 recurring disappearances, 59 net-new regional listings.

What this means: Review the 72 regressions against existing regional targets and fallbacks first; treat the 59 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-31 to 2026-08-06): across 7 recorded scans, there were 1,374 new listings and 1,060 regressions. New listings led on 2 scans; regressions led on 3.

Archived commentary and representative evidence

Latest scan: 59 new availability signals and 72 regressions across 59 regions.

Azure AI models: models/versions delisted (likely deprecation) (4 signals; 4 deprecation candidates). SRE impact: review model deployment targets and fallback model/version choices. Coverage now ranges from 29 to 29 of 64 monitored regions. Examples: centralindia · openai.gpt-5-2-codex.2026-01-14; centralindia · openai.gpt-5-3-codex.2026-02-24; qatarcentral · openai.gpt-5-2-codex.2026-01-14; qatarcentral · openai.gpt-5-3-codex.2026-02-24.

VM SKUs: VM sizes withdrawn (68 signals; 34 deprecation candidates, 34 recurring disappearances). SRE impact: capacity planning and SKU fallback lists should be rechecked. Coverage now ranges from 37 to 38 of 64 monitored regions. The noisiest affected signal was unavailable 92.9% of prior observations. Examples: switzerlandwest · d1; switzerlandwest · d11; switzerlandwest · d12; switzerlandwest · d13; and 64 more.

AKS extensions: extension types now listed (59 signals; 59 net-new regional availabilities). 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 100.0% of prior observations. Expansion pattern: first observed anywhere in the monitored regions. Examples: australiacentral · haevek.falconbyol; australiacentral2 · haevek.falconbyol; australiaeast · haevek.falconbyol; australiasoutheast · haevek.falconbyol; and 55 more.

Engineering context

  • centralindia aiModels.openai.gpt-5-2-codex.2026-01-14 available → unavailable deprecation candidate
    unavailable 0/85 prior days (0.0%)coverage 29/64 monitored regions (45.3%, -2 regions)coverage removed from 6.5% of prior regionsAsia: 4 current, 5 prior
    Still available in australiaeast, brazilsouth, canadacentral, canadaeast, centralus, eastus, and 23 more. Use this to evaluate model capabilities, regional deployment options, latency, and data residency. Azure OpenAI model availability
  • centralindia aiModels.openai.gpt-5-3-codex.2026-02-24 available → unavailable deprecation candidate
    unavailable 0/85 prior days (0.0%)coverage 29/64 monitored regions (45.3%, -2 regions)coverage removed from 6.5% of prior regionsAsia: 4 current, 5 prior
    Still available in australiaeast, brazilsouth, canadacentral, canadaeast, centralus, eastus, and 23 more. Use this to evaluate model capabilities, regional deployment options, latency, and data residency. Azure OpenAI model availability
  • qatarcentral aiModels.openai.gpt-5-2-codex.2026-01-14 available → unavailable deprecation candidate
    unavailable 0/85 prior days (0.0%)coverage 29/64 monitored regions (45.3%, -2 regions)coverage removed from 6.5% of prior regionsMiddle East: 1 current, 2 prior
    Still available in australiaeast, brazilsouth, canadacentral, canadaeast, centralus, eastus, and 23 more. Use this to evaluate model capabilities, regional deployment options, latency, and data residency. Azure OpenAI model availability
  • qatarcentral aiModels.openai.gpt-5-3-codex.2026-02-24 available → unavailable deprecation candidate
    unavailable 0/85 prior days (0.0%)coverage 29/64 monitored regions (45.3%, -2 regions)coverage removed from 6.5% of prior regionsMiddle East: 1 current, 2 prior
    Still available in australiaeast, brazilsouth, canadacentral, canadaeast, centralus, eastus, and 23 more. Use this to evaluate model capabilities, regional deployment options, latency, and data residency. Azure OpenAI model availability
  • switzerlandwest vmSkus.standard.d1 available → unavailable recurring disappearance
    unavailable 23/85 prior days (27.1%)coverage 38/64 monitored regions (59.4%, -2 regions)coverage removed from 5.0% of prior regionsEurope: 9 current, 10 prior
    Still available in australiacentral, australiacentral2, australiaeast, australiasoutheast, brazilsouth, canadacentral, and 32 more. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • switzerlandwest vmSkus.standard.d11 available → unavailable recurring disappearance
    unavailable 23/85 prior days (27.1%)coverage 38/64 monitored regions (59.4%, -2 regions)coverage removed from 5.0% of prior regionsEurope: 9 current, 10 prior
    Still available in australiacentral, australiacentral2, australiaeast, australiasoutheast, brazilsouth, canadacentral, and 32 more. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • switzerlandwest vmSkus.standard.d12 available → unavailable recurring disappearance
    unavailable 23/85 prior days (27.1%)coverage 38/64 monitored regions (59.4%, -2 regions)coverage removed from 5.0% of prior regionsEurope: 9 current, 10 prior
    Still available in australiacentral, australiacentral2, australiaeast, australiasoutheast, brazilsouth, canadacentral, and 32 more. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • switzerlandwest vmSkus.standard.d13 available → unavailable recurring disappearance
    unavailable 23/85 prior days (27.1%)coverage 38/64 monitored regions (59.4%, -2 regions)coverage removed from 5.0% of prior regionsEurope: 9 current, 10 prior
    Still available in australiacentral, australiacentral2, australiaeast, australiasoutheast, brazilsouth, canadacentral, and 32 more. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • switzerlandwest vmSkus.standard.d14 available → unavailable recurring disappearance
    unavailable 23/85 prior days (27.1%)coverage 38/64 monitored regions (59.4%, -2 regions)coverage removed from 5.0% of prior regionsEurope: 9 current, 10 prior
    Still available in australiacentral, australiacentral2, australiaeast, australiasoutheast, brazilsouth, canadacentral, and 32 more. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • switzerlandwest vmSkus.standard.d2 available → unavailable recurring disappearance
    unavailable 23/85 prior days (27.1%)coverage 38/64 monitored regions (59.4%, -2 regions)coverage removed from 5.0% of prior regionsEurope: 9 current, 10 prior
    Still available in australiacentral, australiacentral2, australiaeast, australiasoutheast, brazilsouth, canadacentral, and 32 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.