Azure regional changes

Since the previous scan Scan-wide briefing

54 VM sizes gained listings across 2 regions

2026-09-08 to 2026-09-09

New changes across services: East US, South East Asia

108New listings
0New delistings
0Known restorations
0Tracked absences
0Evidence gaps

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

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

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

54 VM sizes

108 feature-region records

New listings

108 feature-region records

East US, South East Asia

Example: Standard D128nds V6 VM size. Listing coverage: 49 → 51 regions.

New regional listing of an already observed feature.

Documented feature

Standard_D128nds_v6 - network-optimized general-purpose VM

Dndsv6 is a network-optimized general-purpose VM series using Intel Xeon Platinum 8573C processors.

  • 128 vCPUs and 512 GiB RAM, from the documented size table.
  • General-purpose configuration with 4 GiB per vCPU.

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

Read more: Dndsv6 series specifications · VM size suffix meanings

Planning compute here? Compare the listed sizes with your workload requirements.

Observation history and comparison coverage

0 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-09-08T08:21:39.929634+00:00
Current snapshot: 2026-09-09T03:48:53.553965+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.

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.