Azure regional changes — 2026-08-29

· Auto summary
91 new0 regressions0 parked
Daily executive summary

Compared with the 2026-08-28 snapshot, the 2026-08-29 scan recorded 91 new listings, 0 regressions, and 0 parked unknown transitions.

Where it changed: VM SKUs: 54 new listings, 0 regressions; Azure AI models: 37 new listings, 0 regressions.

Representative changes: Kimi K3 model from Moonshot AI (version 2026-07-29) was newly listed in 31 regions; Standard D128nds V6 VM size was newly listed in eastus2; Standard D128nlds V6 VM size was newly listed in eastus2.

What changed: 85 net-new regional listings, 6 restored regional listings.

What this means: The 91 new listings expand the set of regional 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-23 to 2026-08-29): across 6 recorded scans, there were 984 new listings and 195 regressions. New listings led on 5 scans; regressions led on 1.

Archived commentary and representative evidence

Latest scan: 91 new availability signals and 0 regressions across 32 regions.

Azure AI models: newer models/versions rolling out (37 signals; 31 net-new regional availabilities, 6 restored availabilities, up to 1 prior disappearance). SRE impact: new regional model/version options for latency, residency, and model selection. Coverage now ranges from 29 to 31 of 64 monitored regions. The noisiest affected signal was unavailable 100.0% of prior observations. Expansion pattern: first observed anywhere in the monitored regions; restored regional signal. Examples: australiaeast · Azure AI model/version catalog entry for model selection (moonshotai.kimi-k3.2026-07-29); brazilsouth · Azure AI model/version catalog entry for model selection (moonshotai.kimi-k3.2026-07-29); canadacentral · Azure AI model/version catalog entry for model selection (moonshotai.kimi-k3.2026-07-29); canadaeast · Azure AI model/version catalog entry for model selection (moonshotai.kimi-k3.2026-07-29); and 33 more.

VM SKUs: VM sizes now offered (54 signals; 54 net-new regional availabilities). SRE impact: more compute shapes for right-sizing, performance, and cost tuning. Coverage now ranges from 29 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: eastus2 · Azure virtual-machine size for right-sizing compute (d128nds.v6); eastus2 · Azure virtual-machine size for right-sizing compute (d128nlds.v6); eastus2 · Azure virtual-machine size for right-sizing compute (d128nls.v6); eastus2 · Azure virtual-machine size for right-sizing compute (d128ns.v6); and 50 more.

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

Engineering context

  • australiaeast aiModels.moonshotai.kimi-k3.2026-07-29 None → available net-new regional availability
    unavailable 107/107 prior days (100.0%)coverage 31/64 monitored regions (48.4%, +31 regions)Oceania: 1 current, 0 priorfirst observed anywhere in the monitored regions
    Also newly available in australiaeast, brazilsouth, canadacentral, canadaeast, centralus, eastus, and 25 more. Use this to evaluate model capabilities, regional deployment options, latency, and data residency. Azure OpenAI model availability
  • brazilsouth aiModels.moonshotai.kimi-k3.2026-07-29 None → available net-new regional availability
    unavailable 107/107 prior days (100.0%)coverage 31/64 monitored regions (48.4%, +31 regions)South America: 1 current, 0 priorfirst observed anywhere in the monitored regions
    Also newly available in australiaeast, brazilsouth, canadacentral, canadaeast, centralus, eastus, and 25 more. Use this to evaluate model capabilities, regional deployment options, latency, and data residency. Azure OpenAI model availability
  • canadacentral aiModels.moonshotai.kimi-k3.2026-07-29 None → available net-new regional availability
    unavailable 107/107 prior days (100.0%)coverage 31/64 monitored regions (48.4%, +31 regions)North America: 11 current, 0 priorfirst observed anywhere in the monitored regions
    Also newly available in australiaeast, brazilsouth, canadacentral, canadaeast, centralus, eastus, and 25 more. Use this to evaluate model capabilities, regional deployment options, latency, and data residency. Azure OpenAI model availability
  • canadaeast aiModels.moonshotai.kimi-k3.2026-07-29 None → available net-new regional availability
    unavailable 107/107 prior days (100.0%)coverage 31/64 monitored regions (48.4%, +31 regions)North America: 11 current, 0 priorfirst observed anywhere in the monitored regions
    Also newly available in australiaeast, brazilsouth, canadacentral, canadaeast, centralus, eastus, and 25 more. Use this to evaluate model capabilities, regional deployment options, latency, and data residency. Azure OpenAI model availability
  • centralus aiModels.moonshotai.kimi-k3.2026-07-29 None → available net-new regional availability
    unavailable 107/107 prior days (100.0%)coverage 31/64 monitored regions (48.4%, +31 regions)North America: 11 current, 0 priorfirst observed anywhere in the monitored regions
    Also newly available in australiaeast, brazilsouth, canadacentral, canadaeast, centralus, eastus, and 25 more. Use this to evaluate model capabilities, regional deployment options, latency, and data residency. Azure OpenAI model availability
  • eastus aiModels.moonshotai.kimi-k3.2026-07-29 None → available net-new regional availability
    unavailable 107/107 prior days (100.0%)coverage 31/64 monitored regions (48.4%, +31 regions)North America: 11 current, 0 priorfirst observed anywhere in the monitored regions
    Also newly available in australiaeast, brazilsouth, canadacentral, canadaeast, centralus, eastus, and 25 more. Use this to evaluate model capabilities, regional deployment options, latency, and data residency. Azure OpenAI model availability
  • eastus2 aiModels.moonshotai.kimi-k3.2026-07-29 None → available net-new regional availability
    unavailable 107/107 prior days (100.0%)coverage 31/64 monitored regions (48.4%, +31 regions)North America: 11 current, 0 priorfirst observed anywhere in the monitored regions
    Also newly available in australiaeast, brazilsouth, canadacentral, canadaeast, centralus, eastus, and 25 more. Use this to evaluate model capabilities, regional deployment options, latency, and data residency. Azure OpenAI model availability
  • eastus2 vmSkus.standard.d128nds.v6 unavailable → available net-new regional availability
    unavailable 107/107 prior days (100.0%)coverage 29/64 monitored regions (45.3%, +1 region)North America: 11 current, 10 priorregional expansion of an existing signal
    Also newly available in eastus2. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • eastus2 vmSkus.standard.d128nlds.v6 unavailable → available net-new regional availability
    unavailable 107/107 prior days (100.0%)coverage 29/64 monitored regions (45.3%, +1 region)North America: 11 current, 10 priorregional expansion of an existing signal
    Also newly available in eastus2. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • eastus2 vmSkus.standard.d128nls.v6 unavailable → available net-new regional availability
    unavailable 107/107 prior days (100.0%)coverage 32/64 monitored regions (50.0%, +1 region)North America: 11 current, 10 priorregional expansion of an existing signal
    Also newly available in eastus2. 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.