Recurring VM SKU Instability in West US 2, Major Azure Functions Expansion in Austria East

· AI summary
125 new4 regressions1 parked
Daily executive summary

Compared with the 2026-07-07 snapshot, the 2026-07-08 scan recorded 125 new listings, 4 regressions, and 1 parked unknown transition.

Representative changes: Standard Dc1s V2 VM size was no longer listed in westus2; Standard Dc2s V2 VM size was no longer listed in westus2; Standard Dc4s V2 VM size was no longer listed in westus2.

What changed: 4 recurring disappearances, 125 net-new regional listings.

What this means: Review the 4 regressions against existing regional targets and fallbacks first; treat the 125 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-02 to 2026-07-08): across 7 recorded scans, there were 2,607 new listings and 852 regressions. New listings led on 6 scans; regressions led on 1.

Archived commentary and representative evidence

West US 2 has again dropped support for four Standard DCv2 VM SKUs: dc1s, dc2s, dc4s, and dc8. This marks the third disappearance in 57 days, with these SKUs missing for 2 days (3.5% unavailable_pct). Coverage for these confidential compute SKUs has fallen from 10 to 9 regions (14.1%), and North America now has only 3 regions offering them, down from 4. Prior disappearances signal ongoing catalog instability rather than a clean deprecation. SREs should revisit capacity planning and update SKU fallback lists, especially for right-sizing and performance-sensitive workloads. For more, see the VM size overview: https://learn.microsoft.com/azure/virtual-machines/sizes/overview.

Meanwhile, Austria East sees a substantial regional expansion for Azure Functions Flex Consumption hosting and runtime options. This includes net-new support for Flex Consumption plans and a wide array of .NET, Java, Node, Powershell, and Python runtime versions. The region joins 49 others, raising feature coverage from 71.9% to 78.1% across monitored regions, with Europe now at 16 regions for these features. This unlocks more serverless placement choices, private networking, memory sizing, and rapid scale-out options, reducing operational overhead and improving burst scaling flexibility. Details: https://learn.microsoft.com/azure/azure-functions/flex-consumption-plan.

Additionally, new Azure OpenAI model versions (gpt-realtime-2-1-mini and gpt-realtime-2-1) are now first observed in six regions: Canada Central, Central US, East US 2, France Central, South India, and Sweden Central. This is a net-new signal, expanding model selection and regional deployment options for latency and data residency. East US 2 also sees the first appearance of gpt-chat-latest.2026-06-24 in five regions. These rollouts provide fresh targets for AI workload placement and evaluation. More info: https://learn.microsoft.com/azure/ai-foundry/openai/concepts/models.

In summary, SREs should note recurring VM SKU instability in West US 2, plan for expanded serverless and AI model options in Austria East and several other regions, and adjust placement and fallback strategies accordingly.

Engineering context

  • westus2 vmSkus.standard.dc1s.v2 available → unavailable recurring disappearance
    unavailable 2/57 prior days (3.5%)2 prior disappearancescoverage 9/64 monitored regions (14.1%, -1 region)coverage removed from 10.0% of prior regionsNorth America: 3 current, 4 prior
    Still available in australiaeast, australiasoutheast, eastus, northcentralus, northeurope, uksouth, and 3 more. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • westus2 vmSkus.standard.dc2s.v2 available → unavailable recurring disappearance
    unavailable 2/57 prior days (3.5%)2 prior disappearancescoverage 9/64 monitored regions (14.1%, -1 region)coverage removed from 10.0% of prior regionsNorth America: 3 current, 4 prior
    Still available in australiaeast, australiasoutheast, eastus, northcentralus, northeurope, uksouth, and 3 more. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • westus2 vmSkus.standard.dc4s.v2 available → unavailable recurring disappearance
    unavailable 2/57 prior days (3.5%)2 prior disappearancescoverage 9/64 monitored regions (14.1%, -1 region)coverage removed from 10.0% of prior regionsNorth America: 3 current, 4 prior
    Still available in australiaeast, australiasoutheast, eastus, northcentralus, northeurope, uksouth, and 3 more. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • westus2 vmSkus.standard.dc8.v2 available → unavailable recurring disappearance
    unavailable 2/57 prior days (3.5%)2 prior disappearancescoverage 9/64 monitored regions (14.1%, -1 region)coverage removed from 10.0% of prior regionsNorth America: 3 current, 4 prior
    Still available in australiaeast, australiasoutheast, eastus, northcentralus, northeurope, uksouth, and 3 more. VM size availability affects right-sizing, performance, cost, and capacity fallback choices. Azure VM sizes
  • austriaeast hostingPlans.flexConsumption unavailable → available net-new regional availability
    unavailable 57/57 prior days (100.0%)coverage 50/64 monitored regions (78.1%, +4 regions)Europe: 16 current, 15 priorregional expansion of an existing signal
    Also newly available in austriaeast, jioindiawest, koreasouth, uaecentral. Flex Consumption adds serverless scale with private networking, memory sizing, and fast scale-out options. Azure Functions Flex Consumption plan
  • austriaeast runtimes.dotnet-isolated.10 unavailable → available net-new regional availability
    unavailable 57/57 prior days (100.0%)coverage 50/64 monitored regions (78.1%, +4 regions)Europe: 16 current, 15 priorregional expansion of an existing signal
    Also newly available in austriaeast, jioindiawest, koreasouth, uaecentral. Flex Consumption adds serverless scale with private networking, memory sizing, and fast scale-out options. Azure Functions Flex Consumption plan
  • austriaeast runtimes.dotnet-isolated.6 unavailable → available net-new regional availability
    unavailable 57/57 prior days (100.0%)coverage 50/64 monitored regions (78.1%, +4 regions)Europe: 16 current, 15 priorregional expansion of an existing signal
    Also newly available in austriaeast, jioindiawest, koreasouth, uaecentral. Flex Consumption adds serverless scale with private networking, memory sizing, and fast scale-out options. Azure Functions Flex Consumption plan
  • austriaeast runtimes.dotnet-isolated.7 unavailable → available net-new regional availability
    unavailable 57/57 prior days (100.0%)coverage 50/64 monitored regions (78.1%, +4 regions)Europe: 16 current, 15 priorregional expansion of an existing signal
    Also newly available in austriaeast, jioindiawest, koreasouth, uaecentral. Flex Consumption adds serverless scale with private networking, memory sizing, and fast scale-out options. Azure Functions Flex Consumption plan
  • austriaeast runtimes.dotnet-isolated.8 unavailable → available net-new regional availability
    unavailable 57/57 prior days (100.0%)coverage 50/64 monitored regions (78.1%, +4 regions)Europe: 16 current, 15 priorregional expansion of an existing signal
    Also newly available in austriaeast, jioindiawest, koreasouth, uaecentral. Flex Consumption adds serverless scale with private networking, memory sizing, and fast scale-out options. Azure Functions Flex Consumption plan
  • austriaeast runtimes.dotnet-isolated.9 unavailable → available net-new regional availability
    unavailable 57/57 prior days (100.0%)coverage 50/64 monitored regions (78.1%, +4 regions)Europe: 16 current, 15 priorregional expansion of an existing signal
    Also newly available in austriaeast, jioindiawest, koreasouth, uaecentral. Flex Consumption adds serverless scale with private networking, memory sizing, and fast scale-out options. Azure Functions Flex Consumption plan

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.