---
slug: "azure-batch-hbv2-hc-np-series-vm-retirement"
title: "Azure Batch: HBv2, HC and NP-series VM retirement"
summary: "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."
cloud: "azure"
service: "Azure Batch"
service_slug: "batch"
category: "compute_sku"
type: "retirement"
announced_date: "2026-04-15"
effective_date: "2027-05-31"
effective_precision: "day"
replacement: "HBv3-series or HBv4-series for HBv2; HX-series for HC; no direct replacement for NP"
affected_versions: []
source_url: "https://azure.microsoft.com/updates?id=559751"
extra_source_urls: []
vendor_ref: "559751"
last_checked_at: "2026-11-12T09:55:19.345Z"
created_at: "2026-11-13T13:36:44.208Z"
updated_at: "2026-11-13T13:36:44.208Z"
url: "https://eolwatch.dev/items/azure-batch-hbv2-hc-np-series-vm-retirement"
short_url: "https://eolwatch.dev/i/66"
markdown_url: "https://eolwatch.dev/items/azure-batch-hbv2-hc-np-series-vm-retirement.md"
json_url: "https://eolwatch.dev/items/azure-batch-hbv2-hc-np-series-vm-retirement.json"
source_note: null
---

# 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.

- Effective date: 31 May 2027
- Cloud: [Azure](https://eolwatch.dev/cloud/azure.md)
- Service: [Azure Batch](https://eolwatch.dev/services/azure/batch.md)
- Type: Retirement
- Category: [Compute SKU](https://eolwatch.dev/categories/compute-skus.md)
- Replacement: HBv3-series or HBv4-series for HBv2; HX-series for HC; no direct replacement for NP
- Announced: 15 Apr 2026
- Official source: [azure.microsoft.com](https://azure.microsoft.com/updates?id=559751)
- Last checked: 12 Nov 2026

## 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

## 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

- [Official source](https://azure.microsoft.com/updates?id=559751) (azure.microsoft.com, Official)

Last checked against this source on 12 Nov 2026.

Page: https://eolwatch.dev/items/azure-batch-hbv2-hc-np-series-vm-retirement | JSON: https://eolwatch.dev/items/azure-batch-hbv2-hc-np-series-vm-retirement.json

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.