Skip to content
EOL Watch
Search itemsOpen menu

AzureRetirement

Azure Batch: NVv3 and NVv4-series VM retirement

Retirement date for NVv3-series and NVv4-series virtual machines in Azure Batch pools: 30 Sep 2026. After that date, new pools with these VM families cannot be created, and existing pools cannot scale out and are subject to forced resize to zero nodes.

Retired , 30 Sep 2026

What breaks

Azure Batch follows the Azure retirement dates for NVv3-series and NVv4-series VM support in Batch pools. After the retirement date, new Batch pools that specify the NVv3 or NVv4-series VM family cannot be created. Existing pools with NVv3 or NVv4-series VMs can no longer scale out and are subject to forced resize to zero nodes. The affected sizes are Standard_NV12s_v3, Standard_NV12hs_v3, Standard_NV24s_v3, Standard_NV24ms_v3, Standard_NV32ms_v3 and Standard_NV48s_v3 (NVv3), and Standard_NV4as_v4, Standard_NV4ahs_v4, Standard_NV8as_v4, Standard_NV8ahs_v4, Standard_NV16as_v4, Standard_NV16ahs_v4, Standard_NV32as_v4 and Standard_NV32ahs_v4 (NVv4).

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. Microsoft's notice says to migrate Batch pools to "a newer VM series in the same NC product line", or to a different Batch-supported VM size suitable for the workload.
  2. For the underlying VM retirements, see NVv3 series retirement and NVv4 series retirement.

Replacement

Not stated by vendor.

Sources

Last checked against the first source in this list 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