Skip to content
EOL Watch
Search itemsOpen menu

AzureRetirement

Azure Batch: HBv2, HC and NP-series VM retirement

Retirement date for HBv2-series, HC-series and NP-series virtual machines in Azure Batch pools: 31 May 2027. After that date, new pools with these VM sizes cannot be created and existing pools are subject to forced resize to zero nodes.

Retires , 31 May 2027

What breaks

Microsoft retires support for HBv2-series, HC-series and NP-series VMs in Azure Batch pools on 31 May 2027. After that date, new Batch pools with these VM sizes cannot be created, and existing pools are subject to forced resize to zero nodes. Existing pools cannot be updated in place, so a new pool is required. The NP-series has no direct replacement.

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 sizes before 31 May 2027.
  2. Move HBv2-series pools to HBv3-series or HBv4-series, and HC-series pools to HX-series.
  3. For NP-series pools, evaluate GPU-based NC/ND-series VMs or partner FPGA solutions.
  4. Create a new pool, because existing pools cannot be updated in place.
  5. Microsoft refers to the Batch pool VM sizes documentation and the update pool properties guide for instructions.

Replacement

HBv3-series or HBv4-series for HBv2; HX-series for HC; no direct replacement for NP

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