Azure regional changes

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

44 VM sizes dropped regions · 2 AKS extensions and 9 VM sizes gained new regions

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

AKS extensions

▲ 2 AKS extensions +118 new listings

New regions: +59 regionsAustralia Central, Australia Central 2, Australia East, Australia South East, Austria East, Belgium Central, Brazil South, Brazil South East, Canada Central, Canada East, Central India, Central US, Chile Central, Denmark East, East Asia, East US, East US 2, France Central, France South, Germany North, Germany West Central, India South Central, Indonesia Central, Israel Central, Italy North, Japan East, Japan West, Jio India Central, Jio India West, Korea Central, Korea South, Malaysia West, Mexico Central, New Zealand North, North Central US, North Europe, Norway East, Norway West, Poland Central, Qatar Central, South Africa North, South Africa West, South Central US, South East Asia, South India, Spain Central, Sweden Central, Switzerland North, Switzerland West, UAE Central, UAE North, UK South, UK West, West Central US, West Europe, West India, West US, West US 2, West US 3

  • nethouseconsulting.documentgeneratortest AKS extension Third-party AKS extension type from publisher nethouseconsulting +59 regionsAustralia Central, Australia Central 2, Australia East, Australia South East, Austria East, Belgium Central, Brazil South, Brazil South East, Canada Central, Canada East, Central India, Central US, Chile Central, Denmark East, East Asia, East US, East US 2, France Central, France South, Germany North, Germany West Central, India South Central, Indonesia Central, Israel Central, Italy North, Japan East, Japan West, Jio India Central, Jio India West, Korea Central, Korea South, Malaysia West, Mexico Central, New Zealand North, North Central US, North Europe, Norway East, Norway West, Poland Central, Qatar Central, South Africa North, South Africa West, South Central US, South East Asia, South India, Spain Central, Sweden Central, Switzerland North, Switzerland West, UAE Central, UAE North, UK South, UK West, West Central US, West Europe, West India, West US, West US 2, West US 30 → 59 regionsfirst listing · 7 geographies
  • swaransoft.consivaai AKS extension Third-party AKS extension type from publisher swaransoft +59 regionsAustralia Central, Australia Central 2, Australia East, Australia South East, Austria East, Belgium Central, Brazil South, Brazil South East, Canada Central, Canada East, Central India, Central US, Chile Central, Denmark East, East Asia, East US, East US 2, France Central, France South, Germany North, Germany West Central, India South Central, Indonesia Central, Israel Central, Italy North, Japan East, Japan West, Jio India Central, Jio India West, Korea Central, Korea South, Malaysia West, Mexico Central, New Zealand North, North Central US, North Europe, Norway East, Norway West, Poland Central, Qatar Central, South Africa North, South Africa West, South Central US, South East Asia, South India, Spain Central, Sweden Central, Switzerland North, Switzerland West, UAE Central, UAE North, UK South, UK West, West Central US, West Europe, West India, West US, West US 2, West US 30 → 59 regionsfirst listing · 7 geographies

VM SKUs

▲ 9 VM sizes +9 new listings▼ 44 VM sizes −44 listings

New regions: + East US Dropped: − Chile Central− East US

  • Mv3-series · memory optimized 32 VM sizes: M128bds 3, M128bds, M128bs, M12ds, M12s … +27 Dropped: − Chile Central33 → 32 regions
    • Standard M128bds 3 V3 VM size Large-memory optimized, 128 vCPUs, remote storage bandwidth, local temp disk, Premium SSD, 3, v3 − Chile Central33 → 32 regionsLearn
    • Standard M128bds V3 VM size Large-memory optimized, 128 vCPUs, remote storage bandwidth, local temp disk, Premium SSD, v3 − Chile Central33 → 32 regionsMbdsv3 sizes series
    • Standard M128bs V3 VM size Large-memory optimized, 128 vCPUs, remote storage bandwidth optimized, premium SSD capable, v3 − Chile Central33 → 32 regionsMbsv3 sizes series
    • Standard M12ds V3 VM size Large-memory optimized, 12 vCPUs, local temp disk, premium SSD capable, v3 − Chile Central33 → 32 regionsMdsv3 Medium Memory sizes series
    • Standard M12s V3 VM size Large-memory optimized, 12 vCPUs, premium SSD capable, v3 − Chile Central33 → 32 regionsMsv3 Medium Memory sizes series
    • Standard M16bds V3 VM size Large-memory optimized, 16 vCPUs, remote storage bandwidth, local temp disk, premium SSD capable, v3 − Chile Central33 → 32 regionsMbdsv3 sizes series
    • Standard M16bs V3 VM size Large-memory optimized, 16 vCPUs, remote storage bandwidth optimized, premium SSD capable, v3 − Chile Central33 → 32 regionsMbsv3 sizes series
    • Standard M16s V3 VM size Large-memory optimized, 16 vCPUs, premium SSD capable, v3 − Chile Central33 → 32 regionsMsv3 Medium Memory sizes series
    • Standard M176bds 4 V3 VM size Large-memory optimized, 176 vCPUs, remote storage bandwidth, local temp disk, Premium SSD, 4, v3 − Chile Central33 → 32 regionsLearn
    • Standard M176bds V3 VM size Large-memory optimized, 176 vCPUs, remote storage bandwidth, local temp disk, Premium SSD, v3 − Chile Central33 → 32 regionsMbdsv3 sizes series
    • Standard M176bs V3 VM size Large-memory optimized, 176 vCPUs, remote storage bandwidth optimized, premium SSD capable, v3 − Chile Central33 → 32 regionsMbsv3 sizes series
    • Standard M176ds 3 V3 VM size Large-memory optimized, 176 vCPUs, local temp disk, premium SSD capable, 3, v3 − Chile Central33 → 32 regionsLearn
    • Standard M176s 3 V3 VM size Large-memory optimized, 176 vCPUs, premium SSD capable, 3, v3 − Chile Central33 → 32 regionsLearn
    • Standard M24ds V3 VM size Large-memory optimized, 24 vCPUs, local temp disk, premium SSD capable, v3 − Chile Central33 → 32 regionsMdsv3 Medium Memory sizes series
    • Standard M24s V3 VM size Large-memory optimized, 24 vCPUs, premium SSD capable, v3 − Chile Central33 → 32 regionsMsv3 Medium Memory sizes series
    • Standard M32bds V3 VM size Large-memory optimized, 32 vCPUs, remote storage bandwidth, local temp disk, premium SSD capable, v3 − Chile Central33 → 32 regionsMbdsv3 sizes series
    • Standard M32bs V3 VM size Large-memory optimized, 32 vCPUs, remote storage bandwidth optimized, premium SSD capable, v3 − Chile Central33 → 32 regionsMbsv3 sizes series
    • Standard M32ts V3 VM size Large-memory optimized, 32 vCPUs, tiny memory, premium SSD capable, v3 − Chile Central33 → 32 regionsLearn
    • Standard M48bds V3 VM size Large-memory optimized, 48 vCPUs, remote storage bandwidth, local temp disk, premium SSD capable, v3 − Chile Central33 → 32 regionsMbdsv3 sizes series
    • Standard M48bs V3 VM size Large-memory optimized, 48 vCPUs, remote storage bandwidth optimized, premium SSD capable, v3 − Chile Central33 → 32 regionsMbsv3 sizes series
    • Standard M48ds 1 V3 VM size Large-memory optimized, 48 vCPUs, local temp disk, premium SSD capable, 1, v3 − Chile Central33 → 32 regionsLearn
    • Standard M48s 1 V3 VM size Large-memory optimized, 48 vCPUs, premium SSD capable, 1, v3 − Chile Central33 → 32 regionsLearn
    • Standard M64bds 1 V3 VM size Large-memory optimized, 64 vCPUs, remote storage bandwidth, local temp disk, Premium SSD, 1, v3 − Chile Central33 → 32 regionsLearn
    • Standard M64bds V3 VM size Large-memory optimized, 64 vCPUs, remote storage bandwidth, local temp disk, premium SSD capable, v3 − Chile Central33 → 32 regionsMbdsv3 sizes series
    • Standard M64bs V3 VM size Large-memory optimized, 64 vCPUs, remote storage bandwidth optimized, premium SSD capable, v3 − Chile Central33 → 32 regionsMbsv3 sizes series
    • Standard M96bds 2 V3 VM size Large-memory optimized, 96 vCPUs, remote storage bandwidth, local temp disk, Premium SSD, 2, v3 − Chile Central33 → 32 regionsLearn
    • Standard M96bds V3 VM size Large-memory optimized, 96 vCPUs, remote storage bandwidth, local temp disk, premium SSD capable, v3 − Chile Central33 → 32 regionsMbdsv3 sizes series
    • Standard M96bs V3 VM size Large-memory optimized, 96 vCPUs, remote storage bandwidth optimized, premium SSD capable, v3 − Chile Central33 → 32 regionsMbsv3 sizes series
    • Standard M96ds 1 V3 VM size Large-memory optimized, 96 vCPUs, local temp disk, premium SSD capable, 1, v3 − Chile Central33 → 32 regionsLearn
    • Standard M96ds 2 V3 VM size Large-memory optimized, 96 vCPUs, local temp disk, premium SSD capable, 2, v3 − Chile Central33 → 32 regionsLearn
    • Standard M96s 1 V3 VM size Large-memory optimized, 96 vCPUs, premium SSD capable, 1, v3 − Chile Central33 → 32 regionsLearn
    • Standard M96s 2 V3 VM size Large-memory optimized, 96 vCPUs, premium SSD capable, 2, v3 − Chile Central33 → 32 regionsLearn
  • NCv3-series · gpu compute optimized 4 VM sizes: Nc12s, Nc24rs, Nc24s, Nc6s Dropped: − East US6 → 5 regions
    • Standard Nc12s V3 VM size GPU compute optimized, 12 vCPUs, premium SSD capable, v3 − East US6 → 5 regionsLearn
    • Standard Nc24rs V3 VM size GPU compute optimized, 24 vCPUs, RDMA, premium SSD capable, v3 − East US6 → 5 regionsLearn
    • Standard Nc24s V3 VM size GPU compute optimized, 24 vCPUs, premium SSD capable, v3 − East US6 → 5 regionsLearn
    • Standard Nc6s V3 VM size GPU compute optimized, 6 vCPUs, premium SSD capable, v3 − East US6 → 5 regionsLearn
  • Standard M128 64bds 3 V3 VM size VM catalog entry with exact specifications − Chile Central33 → 32 regions
  • Standard M128 64bds V3 VM size VM catalog entry with exact specifications − Chile Central33 → 32 regions
  • Standard M128 64bs V3 VM size VM catalog entry with exact specifications − Chile Central33 → 32 regions
  • Standard M176 88bds 4 V3 VM size VM catalog entry with exact specifications − Chile Central33 → 32 regions
Show all 11 groups
  • Standard M176 88bds V3 VM size VM catalog entry with exact specifications − Chile Central33 → 32 regions
  • Standard M176 88bs V3 VM size VM catalog entry with exact specifications − Chile Central33 → 32 regions
  • Standard M64 32bds 1 V3 VM size VM catalog entry with exact specifications − Chile Central33 → 32 regions
  • Standard M96 48bds 2 V3 VM size VM catalog entry with exact specifications − Chile Central33 → 32 regions
  • 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: + East US6 → 7 regions
    • Standard Nc144ds Xl Rtxpro6000bse V6 VM size GPU compute optimized, 144 vCPUs, local temp disk, premium SSD capable, XL, RTXPRO6000BSE, v6 + East US6 → 7 regionsLearn
    • Standard Nc144lds Xl Rtxpro6000bse V6 VM size GPU compute optimized, 144 vCPUs, low memory, local temp disk, Premium SSD, XL, RTXPRO6000BSE, v6 + East US6 → 7 regionsLearn
    • Standard Nc24lds Xl Rtxpro6000bse V6 VM size GPU compute optimized, 24 vCPUs, low memory, local temp disk, Premium SSD, XL, RTXPRO6000BSE, v6 + East US6 → 7 regionsLearn
    • Standard Nc288ds Xl Rtxpro6000bse V6 VM size GPU compute optimized, 288 vCPUs, local temp disk, premium SSD capable, XL, RTXPRO6000BSE, v6 + East US6 → 7 regionsLearn
    • Standard Nc288lds Xl Rtxpro6000bse V6 VM size GPU compute optimized, 288 vCPUs, low memory, local temp disk, Premium SSD, XL, RTXPRO6000BSE, v6 + East US6 → 7 regionsLearn
    • Standard Nc36ds Xl Rtxpro6000bse V6 VM size GPU compute optimized, 36 vCPUs, local temp disk, premium SSD capable, XL, RTXPRO6000BSE, v6 + East US6 → 7 regionsLearn
    • Standard Nc36lds Xl Rtxpro6000bse V6 VM size GPU compute optimized, 36 vCPUs, low memory, local temp disk, Premium SSD, XL, RTXPRO6000BSE, v6 + East US6 → 7 regionsLearn
    • Standard Nc72ds Xl Rtxpro6000bse V6 VM size GPU compute optimized, 72 vCPUs, local temp disk, premium SSD capable, XL, RTXPRO6000BSE, v6 + East US6 → 7 regionsLearn
    • Standard Nc72lds Xl Rtxpro6000bse V6 VM size GPU compute optimized, 72 vCPUs, low memory, local temp disk, Premium SSD, XL, RTXPRO6000BSE, v6 + East US6 → 7 regionsLearn
Full evidence, filters and history
63 regions with new changes or gaps

Australia Central, Australia Central 2, Australia East, Australia South East, Austria East, Belgium Central, Brazil South, Brazil South East, Canada Central, Canada East, Central India, Central US, Central US EUAP, Chile Central, Denmark East, East Asia, East US, East US 2, East US 2 EUAP, East US STG, France Central, France South, Germany North, Germany West Central, India South Central, Indonesia Central, Israel Central, Italy North, Japan East, Japan West, Jio India Central, Jio India West, Korea Central, Korea South, Malaysia West, Mexico Central, New Zealand North, North Central US, North Europe, Norway East, Norway West, Poland Central, Qatar Central, South Africa North, South Africa West, South Central US, South Central US STG, South East Asia, South India, Spain Central, Sweden Central, Switzerland North, Switzerland West, UAE Central, UAE North, UK South, UK West, West Central US, West Europe, West India, West US, West US 2, West US 3

127New listings
44New delistings
0Known restorations
3,030Tracked 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

860 VM sizes

2,411 feature-region records

New listings

9 feature-region records

East US

Example: Standard Nc144ds Xl Rtxpro6000bse V6 VM size. Listing coverage: 6 → 7 regions.

New regional listing of an already observed feature.

Documented family

Standard_NC144ds_XL_RTXPRO6000BSE_v6 - GPU compute optimized VM size

Standard_NC144ds_XL_RTXPRO6000BSE_v6 is a gpu compute optimized VM size decoded from Azure's naming convention.

  • The name encodes 144 vCPUs.
  • d = local temp disk 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 compute optimized family overview

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

New delistings

44 feature-region records

Chile Central, East US

Example: Standard M128 64bds 3 V3 VM size. Listing coverage: 33 → 32 regions.

Exact capability unverified

Standard M128 64bds 3 V3 VM size

VM catalog entry with unverified exact specifications.

  • This signal represents a name in the regional VM size catalog, not a running VM.
  • Exact CPU, memory, disk, and network specifications are not verified for this identifier.

Exact SKU specifications have not been verified. A regional SKU listing does not establish quota, capacity, price, successful deployment, or measured performance. Temporary disks are not durable application storage.

Read more: Search Microsoft Learn for this exact identifier (not verified) · Azure VM sizes

If this matches a planned regional target, verify it with the provider. This is not an outage or retirement notice.

Tracked absences

2,358 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.

AKS extensions

4 AKS extensions

126 feature-region records

New listings

118 feature-region records

Australia Central, Australia Central 2, Australia East, Australia South East, Austria East, Belgium Central, Brazil South, Brazil South East, Canada Central, Canada East, Central India, Central US, Chile Central, Denmark East, East Asia, East US, East US 2, France Central, France South, Germany North, Germany West Central, India South Central, Indonesia Central, Israel Central, Italy North, Japan East, Japan West, Jio India Central, Jio India West, Korea Central, Korea South, Malaysia West, Mexico Central, New Zealand North, North Central US, North Europe, Norway East, Norway West, Poland Central, Qatar Central, South Africa North, South Africa West, South Central US, South East Asia, South India, Spain Central, Sweden Central, Switzerland North, Switzerland West, UAE Central, UAE North, UK South, UK West, West Central US, West Europe, West India, West US, West US 2, West US 3

Example: nethouseconsulting.documentgeneratortest AKS extension. Listing coverage: 0 → 59 regions.

First observed in retained monitoring history; not a confirmed product launch.

Exact capability unverified

nethouseconsulting.documentgeneratortest - unverified extension identity

A regional extension catalog identifier without a verified exact product mapping.

  • The probe observes a regional extension-type catalog, not installed cluster software.
  • The exact extension's purpose and cluster requirements have not been verified.

Exact extension identity is unverified. Extension-type catalog evidence is not installation, configuration, cluster compatibility, or successful execution evidence.

Read more: Search Microsoft Learn for this exact identifier (not verified) · AKS cluster extension platform

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

Other status changes

8 feature-region records

Central US EUAP, East US 2 EUAP, East US STG, South Central US STG

Example: nethouseconsulting.documentgeneratortest AKS extension. Listing coverage: 0 → 59 regions.

Exact capability unverified

nethouseconsulting.documentgeneratortest - unverified extension identity

A regional extension catalog identifier without a verified exact product mapping.

  • The probe observes a regional extension-type catalog, not installed cluster software.
  • The exact extension's purpose and cluster requirements have not been verified.

Exact extension identity is unverified. Extension-type catalog evidence is not installation, configuration, cluster compatibility, or successful execution evidence.

Read more: Search Microsoft Learn for this exact identifier (not verified) · AKS cluster extension platform

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

Azure AI models

26 AI models

672 feature-region records

Tracked absences

672 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,030 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-27T03:54:41.919113+00:00
Current snapshot: 2026-10-28T03:42:25.394187+00:00

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

Added check records: 126; 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.