Skip to content
EOL Watch
Search itemsOpen menu

AzureRetirement

Azure Batch: D, Ds, Dv2, Dsv2 and Ls-series VM retirement

Retirement date for the D, Ds, Dv2, Dsv2 and Ls virtual machine series in Azure Batch pools: 1 May 2028. After that date, pools on these series cannot be created or scaled out and may be resized to zero nodes.

Retires , 1 May 2028

What breaks

The retirement affects Azure Batch pools that rely on the D-series, Ds-series, Dv2-series, Dsv2-series and Ls-series. After the retirement date, new Batch pools using these VM series cannot be created, existing pools cannot scale out, and pools may be forcibly resized to zero nodes. Remaining VMs are stopped/deallocated and are no longer covered by the SLA. Affected pools may become unusable.

Who is affected

Matching resource types

  • microsoft.batch/batchaccounts/pools
  • azurerm_batch_pool

Fields the check reads

  • properties.vmsize
  • vm_size

Detected by the estate check from

  • Terraform state or plan (JSON)
  • ARM template

Check your estate for this

What to do

  1. Migrate Batch pools to supported VM families before the retirement date.
  2. For general-purpose pools (D, Ds, Dv2, Dsv2), use Dsv5/Ddsv5 or Dasv5/Dadsv5, or Dsv6/Ddsv6 or Dasv6/Dadsv6 for NVMe workloads.
  3. For storage-optimized pools (Ls), use Lsv3/Lasv3 or Lsv4/Lasv4.
  4. Either scale the pool to zero and update the VM size using the Batch API (2024-07-01 or later), or create a new pool with supported VM sizes and migrate the workloads.
  5. Check Azure VM pricing, because VM pricing may change after migration.

Replacement

Dsv5/Ddsv5 or Dasv5/Dadsv5 (Dsv6/Ddsv6 or Dasv6/Dadsv6 for NVMe workloads); Lsv3/Lasv3 or Lsv4/Lasv4 for Ls

Sources

Last checked against this source on .

Found an error? Report it

The text on this page is drafted with AI assistance from the vendor's text, checked against the official source and approved by a person before it is published. How items are written

Last checked · Added · Changelog for this item