Azure regional changes — 2026-09-04

· Auto summary
90 new0 regressions0 parked
Daily executive summary

Compared with the 2026-09-03 snapshot, the 2026-09-04 scan recorded 90 new listings, 0 regressions, and 0 parked unknown transitions.

Where it changed: VM SKUs: 64 new listings, 0 regressions; Azure AI models: 14 new listings, 0 regressions; Container Apps: 12 new listings, 0 regressions.

Representative changes: apps Container Apps capability was newly listed in 3 regions; daprComponents Container Apps capability was newly listed in 3 regions; jobs Container Apps capability was newly listed in 3 regions.

What changed: 80 net-new regional listings, 10 restored regional listings.

What this means: The 90 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-29 to 2026-09-04): across 7 recorded scans, there were 1,276 new listings and 1,070 regressions. New listings led on 5 scans; regressions led on 2.

Archived commentary and representative evidence

Latest scan: 90 new availability signals and 0 regressions across 12 regions.

Azure AI models: newer models/versions rolling out (14 signals; 14 net-new regional availabilities). SRE impact: new regional model/version options for latency, residency, and model selection. Coverage now ranges from 7 to 7 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: eastus · Azure AI model/version catalog entry for model selection (microsoft.mai-image-2-6-flash.2026-07-31); eastus · Azure AI model/version catalog entry for model selection (microsoft.mai-image-2-6.2026-07-31); southindia · Azure AI model/version catalog entry for model selection (microsoft.mai-image-2-6-flash.2026-07-31); southindia · Azure AI model/version catalog entry for model selection (microsoft.mai-image-2-6.2026-07-31); and 10 more.

Container Apps: Container Apps now advertised (12 signals; 12 net-new regional availabilities). SRE impact: new serverless container placement for event-driven scale and microservices. Coverage now ranges from 46 to 46 of 64 monitored regions. The noisiest affected signal was unavailable 100.0% of prior observations. Expansion pattern: regional expansion of an existing signal. Examples: austriaeast · Azure Container Apps provider capability for serverless container planning (containerApps.apps); austriaeast · Azure Container Apps provider capability for serverless container planning (containerApps.daprComponents); austriaeast · Azure Container Apps provider capability for serverless container planning (containerApps.jobs); austriaeast · Azure Container Apps provider capability for serverless container planning (containerApps.managedEnvironments); and 8 more.

VM SKUs: VM sizes now offered (64 signals; 54 net-new regional availabilities, 10 restored availabilities, up to 2 prior disappearances). SRE impact: more compute shapes for right-sizing, performance, and cost tuning. Coverage now ranges from 7 to 40 of 64 monitored regions. The noisiest affected signal was unavailable 100.0% of prior observations. Expansion pattern: regional expansion of an existing signal; restored regional signal. Examples: spaincentral · Azure virtual-machine size for right-sizing compute (d128nds.v6); spaincentral · Azure virtual-machine size for right-sizing compute (d128nlds.v6); spaincentral · Azure virtual-machine size for right-sizing compute (d128nls.v6); spaincentral · Azure virtual-machine size for right-sizing compute (d128ns.v6); and 60 more.

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

Engineering context

  • austriaeast containerApps.apps unavailable → available net-new regional availability
    unavailable 113/113 prior days (100.0%)coverage 46/64 monitored regions (71.9%, +3 regions)Europe: 16 current, 15 priorregional expansion of an existing signal
    Also newly available in austriaeast, mexicocentral, uaecentral.
  • austriaeast containerApps.daprComponents unavailable → available net-new regional availability
    unavailable 113/113 prior days (100.0%)coverage 46/64 monitored regions (71.9%, +3 regions)Europe: 16 current, 15 priorregional expansion of an existing signal
    Also newly available in austriaeast, mexicocentral, uaecentral.
  • austriaeast containerApps.jobs unavailable → available net-new regional availability
    unavailable 113/113 prior days (100.0%)coverage 46/64 monitored regions (71.9%, +3 regions)Europe: 16 current, 15 priorregional expansion of an existing signal
    Also newly available in austriaeast, mexicocentral, uaecentral.
  • austriaeast containerApps.managedEnvironments unavailable → available net-new regional availability
    unavailable 113/113 prior days (100.0%)coverage 46/64 monitored regions (71.9%, +3 regions)Europe: 16 current, 15 priorregional expansion of an existing signal
    Also newly available in austriaeast, mexicocentral, uaecentral.
  • eastus aiModels.microsoft.mai-image-2-6-flash.2026-07-31 None → available net-new regional availability
    unavailable 113/113 prior days (100.0%)coverage 7/64 monitored regions (10.9%, +7 regions)North America: 3 current, 0 priorfirst observed anywhere in the monitored regions
    Also newly available in eastus, southindia, swedencentral, uaenorth, westcentralus, westeurope, and 1 more. Use this to evaluate model capabilities, regional deployment options, latency, and data residency. Azure OpenAI model availability
  • eastus aiModels.microsoft.mai-image-2-6.2026-07-31 None → available net-new regional availability
    unavailable 113/113 prior days (100.0%)coverage 7/64 monitored regions (10.9%, +7 regions)North America: 3 current, 0 priorfirst observed anywhere in the monitored regions
    Also newly available in eastus, southindia, swedencentral, uaenorth, westcentralus, westeurope, and 1 more. Use this to evaluate model capabilities, regional deployment options, latency, and data residency. Azure OpenAI model availability
  • mexicocentral containerApps.apps unavailable → available net-new regional availability
    unavailable 113/113 prior days (100.0%)coverage 46/64 monitored regions (71.9%, +3 regions)North America: 12 current, 11 priorregional expansion of an existing signal
    Also newly available in austriaeast, mexicocentral, uaecentral.
  • mexicocentral containerApps.daprComponents unavailable → available net-new regional availability
    unavailable 113/113 prior days (100.0%)coverage 46/64 monitored regions (71.9%, +3 regions)North America: 12 current, 11 priorregional expansion of an existing signal
    Also newly available in austriaeast, mexicocentral, uaecentral.
  • mexicocentral containerApps.jobs unavailable → available net-new regional availability
    unavailable 113/113 prior days (100.0%)coverage 46/64 monitored regions (71.9%, +3 regions)North America: 12 current, 11 priorregional expansion of an existing signal
    Also newly available in austriaeast, mexicocentral, uaecentral.
  • mexicocentral containerApps.managedEnvironments unavailable → available net-new regional availability
    unavailable 113/113 prior days (100.0%)coverage 46/64 monitored regions (71.9%, +3 regions)North America: 12 current, 11 priorregional expansion of an existing signal
    Also newly available in austriaeast, mexicocentral, uaecentral.

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.