Azure regional changes

At a glance — since 2026-10-22Daily regional evidence

26 VM sizes gained new regions · nothing dropped

What this proves: read-only catalog/list or measurement evidence; not quota, capacity, successful deployment, outage, or confirmed retirement. Methodology

VM SKUs

▲ 26 VM sizes +101 new listings

New regions: +9 regionsBrazil South, Central US, East US, East US 2, Italy North, South Central US, Spain Central, UK South, West US

  • Lv5-series · storage optimized 11 VM sizes: L128as, L160ias, L16as, L2as, L32as … +6 Gained: +7 regionsBrazil South, Central US, East US, East US 2, Italy North, UK South, West US5 → 12 regionsfirst in South America
    • Standard L128as V5 VM size Storage optimized, 128 vCPUs, AMD-based, premium SSD capable, v5 +7 regionsBrazil South, Central US, East US, East US 2, Italy North, UK South, West US5 → 12 regionsfirst in South AmericaLasv5 size series
    • Standard L160ias V5 VM size Storage optimized, 160 vCPUs, isolated, AMD-based, premium SSD capable, v5 +7 regionsBrazil South, Central US, East US, East US 2, Italy North, UK South, West US5 → 12 regionsfirst in South AmericaLearn
    • Standard L16as V5 VM size Storage optimized, 16 vCPUs, AMD-based, premium SSD capable, v5 +7 regionsBrazil South, Central US, East US, East US 2, Italy North, UK South, West US5 → 12 regionsfirst in South AmericaLasv5 size series
    • Standard L2as V5 VM size Storage optimized, 2 vCPUs, AMD-based, premium SSD capable, v5 +7 regionsBrazil South, Central US, East US, East US 2, Italy North, UK South, West US5 → 12 regionsfirst in South AmericaLasv5 size series
    • Standard L32as V5 VM size Storage optimized, 32 vCPUs, AMD-based, premium SSD capable, v5 +7 regionsBrazil South, Central US, East US, East US 2, Italy North, UK South, West US5 → 12 regionsfirst in South AmericaLasv5 size series
    • Standard L48as V5 VM size Storage optimized, 48 vCPUs, AMD-based, premium SSD capable, v5 +7 regionsBrazil South, Central US, East US, East US 2, Italy North, UK South, West US5 → 12 regionsfirst in South AmericaLasv5 size series
    • Standard L4as V5 VM size Storage optimized, 4 vCPUs, AMD-based, premium SSD capable, v5 +7 regionsBrazil South, Central US, East US, East US 2, Italy North, UK South, West US5 → 12 regionsfirst in South AmericaLasv5 size series
    • Standard L64as V5 VM size Storage optimized, 64 vCPUs, AMD-based, premium SSD capable, v5 +7 regionsBrazil South, Central US, East US, East US 2, Italy North, UK South, West US5 → 12 regionsfirst in South AmericaLasv5 size series
    • Standard L80as V5 VM size Storage optimized, 80 vCPUs, AMD-based, premium SSD capable, v5 +7 regionsBrazil South, Central US, East US, East US 2, Italy North, UK South, West US5 → 12 regionsfirst in South AmericaLasv5 size series
    • Standard L8as V5 VM size Storage optimized, 8 vCPUs, AMD-based, premium SSD capable, v5 +7 regionsBrazil South, Central US, East US, East US 2, Italy North, UK South, West US5 → 12 regionsfirst in South AmericaLasv5 size series
    • Standard L96as V5 VM size Storage optimized, 96 vCPUs, AMD-based, premium SSD capable, v5 +7 regionsBrazil South, Central US, East US, East US 2, Italy North, UK South, West US5 → 12 regionsfirst in South AmericaLasv5 size series
  • NCv6-series · gpu compute optimized 9 VM sizes: Nc144ds Xl Rtxpro6000bse, Nc144lds Xl Rtxpro6000bse, Nc24lds Xl Rtxpro6000bse, Nc288ds Xl Rtxpro6000bse, Nc288lds Xl Rtxpro6000bse … +4 Gained: + South Central US+ Spain Central2 → 4 regionsfirst in Europe
    • Standard Nc144ds Xl Rtxpro6000bse V6 VM size GPU compute optimized, 144 vCPUs, local temp disk, premium SSD capable, XL, RTXPRO6000BSE, v6 + South Central US+ Spain Central2 → 4 regionsfirst in EuropeLearn
    • Standard Nc144lds Xl Rtxpro6000bse V6 VM size GPU compute optimized, 144 vCPUs, low memory, local temp disk, Premium SSD, XL, RTXPRO6000BSE, v6 + South Central US+ Spain Central2 → 4 regionsfirst in EuropeLearn
    • Standard Nc24lds Xl Rtxpro6000bse V6 VM size GPU compute optimized, 24 vCPUs, low memory, local temp disk, Premium SSD, XL, RTXPRO6000BSE, v6 + South Central US+ Spain Central2 → 4 regionsfirst in EuropeLearn
    • Standard Nc288ds Xl Rtxpro6000bse V6 VM size GPU compute optimized, 288 vCPUs, local temp disk, premium SSD capable, XL, RTXPRO6000BSE, v6 + South Central US+ Spain Central2 → 4 regionsfirst in EuropeLearn
    • Standard Nc288lds Xl Rtxpro6000bse V6 VM size GPU compute optimized, 288 vCPUs, low memory, local temp disk, Premium SSD, XL, RTXPRO6000BSE, v6 + South Central US+ Spain Central2 → 4 regionsfirst in EuropeLearn
    • Standard Nc36ds Xl Rtxpro6000bse V6 VM size GPU compute optimized, 36 vCPUs, local temp disk, premium SSD capable, XL, RTXPRO6000BSE, v6 + South Central US+ Spain Central2 → 4 regionsfirst in EuropeLearn
    • Standard Nc36lds Xl Rtxpro6000bse V6 VM size GPU compute optimized, 36 vCPUs, low memory, local temp disk, Premium SSD, XL, RTXPRO6000BSE, v6 + South Central US+ Spain Central2 → 4 regionsfirst in EuropeLearn
    • Standard Nc72ds Xl Rtxpro6000bse V6 VM size GPU compute optimized, 72 vCPUs, local temp disk, premium SSD capable, XL, RTXPRO6000BSE, v6 + South Central US+ Spain Central2 → 4 regionsfirst in EuropeLearn
    • Standard Nc72lds Xl Rtxpro6000bse V6 VM size GPU compute optimized, 72 vCPUs, low memory, local temp disk, Premium SSD, XL, RTXPRO6000BSE, v6 + South Central US+ Spain Central2 → 4 regionsfirst in EuropeLearn
  • Dv7-series · general purpose 6 VM sizes: D248ds, D248lds, D248ls, D248s, D372ds … +1 Gained: + UK South13 → 14 regions
    • Standard D248ds V7 VM size General purpose, 248 vCPUs, local temp disk, premium SSD capable, v7 + UK South13 → 14 regionsDdsv7 sizes series
    • Standard D248lds V7 VM size General purpose, 248 vCPUs, low memory, local temp disk, premium SSD capable, v7 + UK South13 → 14 regionsDldsv7 sizes series
    • Standard D248ls V7 VM size General purpose, 248 vCPUs, low memory, premium SSD capable, v7 + UK South13 → 14 regionsDlsv7 sizes series
    • Standard D248s V7 VM size General purpose, 248 vCPUs, premium SSD capable, v7 + UK South13 → 14 regionsDsv7 sizes series
    • Standard D372ds V7 VM size General purpose, 372 vCPUs, local temp disk, premium SSD capable, v7 + UK South13 → 14 regionsDdsv7 sizes series
    • Standard D372s V7 VM size General purpose, 372 vCPUs, premium SSD capable, v7 + UK South13 → 14 regionsDsv7 sizes series
Full evidence, filters and history
32 regions with new changes or gaps

Australia East, Brazil South, Canada Central, Central India, Central US, Central US EUAP, East US, East US 2, East US 2 EUAP, France Central, Germany West Central, India South Central, Italy North, Japan East, Korea Central, North Central US, North Europe, Norway East, Norway West, Poland Central, South Africa North, South Central US, South East Asia, Spain Central, Sweden Central, Switzerland North, UAE North, UK South, West Europe, West US, West US 2, West US 3

101New listings
0New delistings
0Known restorations
3,010Tracked absences
0Evidence gaps

Absence tracking starts at 2026-09-05; older disappearances may not be included.

Changes relevant to you

One listing = one feature in one region

All regions and services. Groups below separate new changes from continuing observations.

VM SKUs

833 VM sizes

2,429 feature-region records

New listings

101 feature-region records

Brazil South, Central US, East US, East US 2, Italy North, South Central US, Spain Central, UK South, West US

Example: Standard L128as V5 VM size. Listing coverage: 5 → 12 regions.

New regional listing of an already observed feature.

Documented family

Standard_L128as_v5 - Storage optimized VM size

Standard_L128as_v5 is a storage optimized VM size decoded from Azure's naming convention.

  • The name encodes 128 vCPUs.
  • a = AMD-based in the documented naming convention.

Naming-convention decoding does not verify memory, CPU model, GPU model, disk throughput, network bandwidth, quota, capacity, price, successful deployment, or measured performance.

Read more: Azure VM sizes naming conventions · Storage optimized family overview

Catalog/list evidence only; verify exact requirements before changing regional plans.

Tracked absences

2,328 feature-region records

Australia East, Brazil South, Canada Central, Central India, Central US, Central US EUAP, East US, East US 2, East US 2 EUAP, France Central, Germany West Central, India South Central, Italy North, Japan East, Korea Central, North Central US, North Europe, Norway East, Norway West, Poland Central, South Africa North, South Central US, South East Asia, Spain Central, Sweden Central, Switzerland North, UAE North, UK South, West Europe, West US, West US 2, West US 3

Example: Standard Nv16as V4 VM size. Listing coverage: 9 → 9 regions.

Documented family

Standard_NV16as_v4 - GPU visualization optimized VM size

Standard_NV16as_v4 is a gpu visualization optimized VM size decoded from Azure's naming convention.

  • The name encodes 16 vCPUs.
  • a = AMD-based in the documented naming convention.

Naming-convention decoding does not verify memory, CPU model, GPU model, disk throughput, network bandwidth, quota, capacity, price, successful deployment, or measured performance.

Read more: Azure VM sizes naming conventions · GPU visualization optimized family overview

Previously tracked delistings remain absent. No new delistings does not mean recovery.

Azure AI models

27 AI models

682 feature-region records

Tracked absences

682 feature-region records

Australia East, Brazil South, Canada Central, Canada East, Central India, Central US, East Asia, East US, East US 2, France Central, Germany West Central, Italy North, Japan East, Japan West, Korea Central, North Central US, North Europe, Norway East, Poland Central, South Africa North, South Central US, South East Asia, South India, Spain Central, Sweden Central, Switzerland North, Switzerland West, UAE North, UK South, UK West, West Central US, West Europe, West US, West US 2, West US 3

Example: deepseek r1 0528 model from deepseek (version 1). Listing coverage: 0 → 0 regions.

Category context

deepseek r1 0528 (catalog version 1) - deepseek

A model identifier observed by this modality; exact capabilities are not verified.

  • Catalog presence identifies a provider/model/version candidate, not its tested abilities.
  • Context limits, input/output modalities, licensing, and tool support need exact-model review.

No exact model capability or version is verified. The source provides category context only. Regional model-catalog evidence does not establish quota, account approval, deployment type, inference access, content filtering, performance, or data residency.

Read more: deepseek model catalog (category only) · Search Microsoft Learn for this exact identifier (not verified)

Previously tracked delistings remain absent. No new delistings does not mean recovery.

Observation history and comparison coverage

3,010 tracked listings remain absent. Zero new delistings does not mean previous absences recovered. Absence tracking starts at 2026-09-05; older disappearances may not be included.

Previous snapshot: 2026-10-22T03:52:36.299725+00:00
Current snapshot: 2026-10-23T03:45:59.088384+00:00

Snapshot timestamps do not establish freshness of every carried-forward modality. The monitor does not assess your running workloads.

Added check records: 0; removed check records: 0. Changes to the observation set do not establish provider intent.

Exact changes and supporting evidence

Grouped by feature. Coverage counts are scan-wide; region and service filters limit the listed records.

Open to load the complete records, without rerunning probes.

Download complete daily evidence

Optional: take a 15-second reading check For deliberate reader testing. For everyday feedback, use the floating feedback buttons.

Share: LinkedIn Twitter

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.