Retirement: D-series, Ds-series, Dv2-series, Dsv2-series, and Ls-series Virtual Machines for Azure Batch pools
What the source says
Azure Compute will retire the following Virtual Machine series on May 1, 2028, impacting Azure Batch pools that rely on them: D-series, Ds-series Dv2-series, Dsv2-series Ls-series After this date: New Batch pools using these VM series cannot be created Existing pools cannot scale out Pools may be forcibly resized to zero nodes Remaining VMs will be stopped/deallocated and no longer covered by SLA Timeline Now – May 1, 2028: Existing pools continue to run; migration is recommended May 1, 2028: Full retirement; affected pools may become unusable Required action Migrate your Batch pools to supported VM families before the retirement date to avoid disruption. Recommended replacements: For general-purpose pools (D/Ds/Dv2/Dsv2): Dsv5/Ddsv5 or Dasv5/Dadsv5; or Dsv6/Ddsv6 / Dasv6/Dadsv6 for NVMe workloads For storage-optimized pools (Ls): Lsv3/Lasv3 or Lsv4/Lasv4 Migration options: Scale pool to zero and update VM size using Batch API (2024-07-01 or later) Create a new pool with supported VM sizes and migrate workloads Note: VM pricing may change after migration. Refer to Azure VM pricing for details.
Who is affected: The audience described by the Microsoft update is represented by: Retirement: D-series, Ds-series, Dv2-series, Dsv2-series, and Ls-series Virtual Machines for Azure Batch pools Azure Compute will retire the following Virtual Machine series on May 1, 2028, impacting Azure Batch pools that rely on them: D-series, Ds-series Dv2-series, Dsv2-series Ls-series After this date: New Batch pools using these VM series cannot be created Existing pools cannot scale out Pools may be forcibly resized to zero nodes Remaining VMs will be stopped/deallocated and no longer cove
Why it matters: The change matters because the official source describes: Retirement: D-series, Ds-series, Dv2-series, Dsv2-series, and Ls-series Virtual Machines for Azure Batch pools Azure Compute will retire the following Virtual Machine series on May 1, 2028, impacting Azure Batch pools that rely on them: D-series, Ds-series Dv2-series, Dsv2-series Ls-series After this date: New Batch pools using these VM series cannot be created Existing pools cannot scale out Pools may be forcibly resized to zero nodes Remaining VMs will be stopped/deallocated and no longer cove
Urgency: Monitor
Next action: Review affected accounts with the customer using the official announcement.
Commercial opportunities
Use the verified change to open a scoped customer conversation.
Technical actions
Assess whether the documented change intersects the customer's current stack.
Questions to ask the customer
Does this documented change affect a product or workload in scope?
Risks and objections
The official source does not establish facts beyond the quoted material.
Points to confirm
The operational scope for this persona must be confirmed before action.
Reading for it_manager_dsi
Who is affected: The audience described by the Microsoft update is represented by: Retirement: D-series, Ds-series, Dv2-series, Dsv2-series, and Ls-series Virtual Machines for Azure Batch pools Azure Compute will retire the following Virtual Machine series on May 1, 2028, impacting Azure Batch pools that rely on them: D-series, Ds-series Dv2-series, Dsv2-series Ls-series After this date: New Batch pools using these VM series cannot be created Existing pools cannot scale out Pools may be forcibly resized to zero nodes Remaining VMs will be stopped/deallocated and no longer cove
Why it matters: The change matters because the official source describes: Retirement: D-series, Ds-series, Dv2-series, Dsv2-series, and Ls-series Virtual Machines for Azure Batch pools Azure Compute will retire the following Virtual Machine series on May 1, 2028, impacting Azure Batch pools that rely on them: D-series, Ds-series Dv2-series, Dsv2-series Ls-series After this date: New Batch pools using these VM series cannot be created Existing pools cannot scale out Pools may be forcibly resized to zero nodes Remaining VMs will be stopped/deallocated and no longer cove
Urgency: Monitor
Next action: Assess technical dependencies and ownership against the official update.
Commercial opportunities
Offer a scoped technical-readiness assessment if the customer confirms impact.
Technical actions
Assess whether the documented change intersects the customer's current stack.
Questions to ask the customer
Does this documented change affect a product or workload in scope?
Risks and objections
The official source does not establish facts beyond the quoted material.
Points to confirm
The operational scope for this persona must be confirmed before action.
Reading for partner_channel
Who is affected: The audience described by the Microsoft update is represented by: Retirement: D-series, Ds-series, Dv2-series, Dsv2-series, and Ls-series Virtual Machines for Azure Batch pools Azure Compute will retire the following Virtual Machine series on May 1, 2028, impacting Azure Batch pools that rely on them: D-series, Ds-series Dv2-series, Dsv2-series Ls-series After this date: New Batch pools using these VM series cannot be created Existing pools cannot scale out Pools may be forcibly resized to zero nodes Remaining VMs will be stopped/deallocated and no longer cove
Why it matters: The change matters because the official source describes: Retirement: D-series, Ds-series, Dv2-series, Dsv2-series, and Ls-series Virtual Machines for Azure Batch pools Azure Compute will retire the following Virtual Machine series on May 1, 2028, impacting Azure Batch pools that rely on them: D-series, Ds-series Dv2-series, Dsv2-series Ls-series After this date: New Batch pools using these VM series cannot be created Existing pools cannot scale out Pools may be forcibly resized to zero nodes Remaining VMs will be stopped/deallocated and no longer cove
Urgency: Monitor
Next action: Prepare a source-backed customer conversation and confirm the affected estate.
Commercial opportunities
Qualify a partner-led assessment only after customer scope is confirmed.
Technical actions
Assess whether the documented change intersects the customer's current stack.
Questions to ask the customer
Does this documented change affect a product or workload in scope?
Risks and objections
The official source does not establish facts beyond the quoted material.
Points to confirm
The operational scope for this persona must be confirmed before action.
Reading for sales_manager
Who is affected: The audience described by the Microsoft update is represented by: Retirement: D-series, Ds-series, Dv2-series, Dsv2-series, and Ls-series Virtual Machines for Azure Batch pools Azure Compute will retire the following Virtual Machine series on May 1, 2028, impacting Azure Batch pools that rely on them: D-series, Ds-series Dv2-series, Dsv2-series Ls-series After this date: New Batch pools using these VM series cannot be created Existing pools cannot scale out Pools may be forcibly resized to zero nodes Remaining VMs will be stopped/deallocated and no longer cove
Why it matters: The change matters because the official source describes: Retirement: D-series, Ds-series, Dv2-series, Dsv2-series, and Ls-series Virtual Machines for Azure Batch pools Azure Compute will retire the following Virtual Machine series on May 1, 2028, impacting Azure Batch pools that rely on them: D-series, Ds-series Dv2-series, Dsv2-series Ls-series After this date: New Batch pools using these VM series cannot be created Existing pools cannot scale out Pools may be forcibly resized to zero nodes Remaining VMs will be stopped/deallocated and no longer cove
Urgency: Monitor
Next action: Review portfolio exposure with account owners using the official source.
Commercial opportunities
Prioritize accounts that confirm affected products or workloads.
Technical actions
Assess whether the documented change intersects the customer's current stack.
Questions to ask the customer
Does this documented change affect a product or workload in scope?
Risks and objections
The official source does not establish facts beyond the quoted material.
Points to confirm
The operational scope for this persona must be confirmed before action.
Evidence and traceability
Each excerpt is linked to the primary source. Current raw version: 475.
Raw capture : 2026-08-26T14:18:57.653130+00:00 — hash 58aa2024e43124ec…
Event
Retirement: D-series, Ds-series, Dv2-series, Dsv2-series, and Ls-series Virtual Machines for Azure Batch pools Azure Compute will retire the following Virtual Machine series on May 1, 2028, impacting Azure Batch pools that rely on them: D-series, Ds-series Dv2-series, Dsv2-series Ls-series After this date: New Batch pools using these VM series cannot be created Existing pools cannot scale out Pools may be forcibly resized to zero nodes Remaining VMs will be stopped/deallocated and no longer covered by SLA Timeline Now – May 1, 2028: Existing pools continue to run; migration is recommended May 1, 2028: Full retirement; affected pools may become unusable Required action Migrate your Batch pools to supported VM families before the retirement date to avoid disruption. Recommended replacements: For general-purpose pools (D/Ds/Dv2/Dsv2): Dsv5/Ddsv5 or Dasv5/Dadsv5; or Dsv6/Ddsv6 / Dasv6/Dadsv6 for NVMe workloads For storage-optimized pools (Ls): Lsv3/Lasv3 or Lsv4/Lasv4 Migration options: Scale pool to zero and update VM size using Batch API (2024-07-01 or later) Create a new pool with supported VM sizes and migrate workloads Note: VM pricing may change after migration. Refer to Azure VM pricing for details.
Retirement: D-series, Ds-series, Dv2-series, Dsv2-series, and Ls-series Virtual Machines for Azure Batch pools Azure Compute will retire the following Virtual Machine series on May 1, 2028, impacting Azure Batch pools that rely on them: D-series, Ds-series Dv2-series, Dsv2-series Ls-series After this date: New Batch pools using these VM series cannot be created Existing pools cannot scale out Pools may be forcibly resized to zero nodes Remaining VMs will be stopped/deallocated and no longer covered by SLA Timeline Now – May 1, 2028: Existing pools continue to run; migration is recommended May 1, 2028: Full retirement; affected pools may become unusable Required action Migrate your Batch pools to supported VM families before the retirement date to avoid disruption. Recommended replacements: For general-purpose pools (D/Ds/Dv2/Dsv2): Dsv5/Ddsv5 or Dasv5/Dadsv5; or Dsv6/Ddsv6 / Dasv6/Dadsv6 for NVMe workloads For storage-optimized pools (Ls): Lsv3/Lasv3 or Lsv4/Lasv4 Migration options: Scale pool to zero and update VM size using Batch API (2024-07-01 or later) Create a new pool with supported VM sizes and migrate workloads Note: VM pricing may change after migration. Refer to Azure VM pricing for details.
Retirement: D-series, Ds-series, Dv2-series, Dsv2-series, and Ls-series Virtual Machines for Azure Batch pools Azure Compute will retire the following Virtual Machine series on May 1, 2028, impacting Azure Batch pools that rely on them: D-series, Ds-series Dv2-series, Dsv2-series Ls-series After this date: New Batch pools using these VM series cannot be created Existing pools cannot scale out Pools may be forcibly resized to zero nodes Remaining VMs will be stopped/deallocated and no longer covered by SLA Timeline Now – May 1, 2028: Existing pools continue to run; migration is recommended May 1, 2028: Full retirement; affected pools may become unusable Required action Migrate your Batch pools to supported VM families before the retirement date to avoid disruption. Recommended replacements: For general-purpose pools (D/Ds/Dv2/Dsv2): Dsv5/Ddsv5 or Dasv5/Dadsv5; or Dsv6/Ddsv6 / Dasv6/Dadsv6 for NVMe workloads For storage-optimized pools (Ls): Lsv3/Lasv3 or Lsv4/Lasv4 Migration options: Scale pool to zero and update VM size using Batch API (2024-07-01 or later) Create a new pool with supported VM sizes and migrate workloads Note: VM pricing may change after migration. Refer to Azure VM
Retirement: D-series, Ds-series, Dv2-series, Dsv2-series, and Ls-series Virtual Machines for Azure Batch pools Azure Compute will retire the following Virtual Machine series on May 1, 2028, impacting Azure Batch pools that rely on them: D-series, Ds-series Dv2-series, Dsv2-series Ls-series After this date: New Batch pools using these VM series cannot be created Existing pools cannot scale out Pools may be forcibly resized to zero nodes Remaining VMs will be stopped/deallocated and no longer covered by SLA Timeline Now – May 1, 2028: Existing pools continue to run; migration is recommended May 1, 2028: Full retirement; affected pools may become unusable Required action Migrate your Batch pools to supported VM families before the retirement date to avoid disruption. Recommended replacements: For general-purpose pools (D/Ds/Dv2/Dsv2): Dsv5/Ddsv5 or Dasv5/Dadsv5; or Dsv6/Ddsv6 / Dasv6/Dadsv6 for NVMe workloads For storage-optimized pools (Ls): Lsv3/Lasv3 or Lsv4/Lasv4 Migration options: Scale pool to zero and update VM size using Batch API (2024-07-01 or later) Create a new pool with supported VM sizes and migrate workloads Note: VM pricing may change after migration. Refer to Azure VM
Retirement: D-series, Ds-series, Dv2-series, Dsv2-series, and Ls-series Virtual Machines for Azure Batch pools Azure Compute will retire the following Virtual Machine series on May 1, 2028, impacting Azure Batch pools that rely on them: D-series, Ds-series Dv2-series, Dsv2-series Ls-series After this date: New Batch pools using these VM series cannot be created Existing pools cannot scale out Pools may be forcibly resized to zero nodes Remaining VMs will be stopped/deallocated and no longer covered by SLA Timeline Now – May 1, 2028: Existing pools continue to run; migration is recommended May 1, 2028: Full retirement; affected pools may become unusable Required action Migrate your Batch pools to supported VM families before the retirement date to avoid disruption. Recommended replacements: For general-purpose pools (D/Ds/Dv2/Dsv2): Dsv5/Ddsv5 or Dasv5/Dadsv5; or Dsv6/Ddsv6 / Dasv6/Dadsv6 for NVMe workloads For storage-optimized pools (Ls): Lsv3/Lasv3 or Lsv4/Lasv4 Migration options: Scale pool to zero and update VM size using Batch API (2024-07-01 or later) Create a new pool with supported VM sizes and migrate workloads Note: VM pricing may change after migration. Refer to Azure VM
Retirement: D-series, Ds-series, Dv2-series, Dsv2-series, and Ls-series Virtual Machines for Azure Batch pools Azure Compute will retire the following Virtual Machine series on May 1, 2028, impacting Azure Batch pools that rely on them: D-series, Ds-series Dv2-series, Dsv2-series Ls-series After this date: New Batch pools using these VM series cannot be created Existing pools cannot scale out Pools may be forcibly resized to zero nodes Remaining VMs will be stopped/deallocated and no longer covered by SLA Timeline Now – May 1, 2028: Existing pools continue to run; migration is recommended May 1, 2028: Full retirement; affected pools may become unusable Required action Migrate your Batch pools to supported VM families before the retirement date to avoid disruption. Recommended replacements: For general-purpose pools (D/Ds/Dv2/Dsv2): Dsv5/Ddsv5 or Dasv5/Dadsv5; or Dsv6/Ddsv6 / Dasv6/Dadsv6 for NVMe workloads For storage-optimized pools (Ls): Lsv3/Lasv3 or Lsv4/Lasv4 Migration options: Scale pool to zero and update VM size using Batch API (2024-07-01 or later) Create a new pool with supported VM sizes and migrate workloads Note: VM pricing may change after migration. Refer to Azure VM