SaaS · archived
Microsoft
Microsoft retired the Azure NVv4-series GPU virtual machines (Standard_NV4as_v4, NV4ahs_v4, NV8as_v4, NV8ahs_v4, NV16as_v4, NV16ahs_v4, NV32as_v4, NV32ahs_v4) on 30 September 2026; any remaining NVv4 VMs are set to a deallocated state, stop working, and lose SLA and support.
left 30 Sept 2026
Quick answers
- Is it true that Azure retired the NVv4-series GPU virtual machines on 30 September 2026 — remaining VMs are deallocated; move to a current GPU series?
- Yes — and the date has already passed (30 Sept 2026). The NVv4-series were Azure's AMD-GPU virtual machines, built around partitionable GPUs for virtual-desktop and light GPU-graphics workloads — the series that let you rent a fraction of a GPU.
- When did it take effect?
- 30 Sept 2026 (already passed). Verified against the vendor's own announcement.
- What should I use instead?
- Azure's current-generation GPU VMs for virtual-desktop and graphics workloads are the **NVadsA10 v5-series** (NVIDIA A10) and, for AMD-GPU partitioned workloads like NVv4's, the **NVads V710 v5-series** (AMD Radeon PRO V710) — the lines that superseded this generation (the retirement notice links to Microsoft's migration guidance rather than naming a target inline).
What this means for you
The NVv4-series were Azure's AMD-GPU virtual machines, built around partitionable GPUs for virtual-desktop and light GPU-graphics workloads — the series that let you rent a fraction of a GPU. As of **30 September 2026 they are retired**: Microsoft has set any remaining NVv4 VMs to a **deallocated** state, so they stop running, no longer bill, and are **no longer under SLA or supported**. The affected sizes are 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. If any of these are still in your ARM, Bicep, or Terraform templates, deployments of them will now fail and any that were running have been stopped — a hard cutover, not a deprecation warning. The commercial wind-down came first: Reserved Instance purchases for the series ended on 2 November 2025, and all Compute Pre-Purchase (CPP) sales ended on 2 June 2026.
Where to go
Azure's current-generation GPU VMs for virtual-desktop and graphics workloads are the **NVadsA10 v5-series** (NVIDIA A10) and, for AMD-GPU partitioned workloads like NVv4's, the **NVads V710 v5-series** (AMD Radeon PRO V710) — the lines that superseded this generation (the retirement notice links to Microsoft's migration guidance rather than naming a target inline). Search your infrastructure-as-code and running deployments for the retired size strings — Standard_NV4as_v4, Standard_NV4ahs_v4, Standard_NV8as_v4, Standard_NV8ahs_v4, Standard_NV16as_v4, Standard_NV16ahs_v4, Standard_NV32as_v4, Standard_NV32ahs_v4 — and repoint each to an equivalent current-generation GPU SKU, then re-test GPU driver installation, display/encoding behavior, and any GPU licensing/partitioning settings, which differ across GPU generations and vendors. Because the VMs are already deallocated, this is recovery work rather than planning: redeploy workloads on the new size, reattach or restore disks, and validate before resuming service.
- Azure NVads V710 v5-series (AMD Radeon PRO V710) — Azure's current-generation AMD-GPU VMs with GPU partitioning, the closest analog to NVv4
- Azure NVadsA10 v5-series (NVIDIA A10) — current-generation GPU VMs for visualization and virtual-desktop workloads
Microsoft has retired the Azure NVv4-series GPU virtual machines as of 30 September 2026. The official Azure retirement notice states that on that date Microsoft retired the 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 sizes, and that any remaining NVv4 VMs are set to a deallocated state — they stop working, stop billing, and lose SLA and support.
What is gone
The NVv4-series were AMD-GPU VMs with partitionable GPUs — the series that let you rent a slice of a GPU for virtual desktops and lighter GPU-graphics workloads. This is a completed retirement, not a future deadline: deployments that reference the NVv4 sizes will now fail, and VMs that were still running have been stopped and deallocated.
The commercial wind-down already happened
Buying into NVv4 was closed off well before the retirement: Reserved Instance purchases ended on 2 November 2025, and all Compute Pre-Purchase (CPP) sales ended on 2 June 2026. By the retirement date there was no supported way to commit to new NVv4 capacity.
Where to go next
Azure’s current-generation GPU VMs for these workloads are the NVads V710 v5-series (AMD Radeon PRO V710, the closest analog to NVv4’s partitioned AMD GPUs) and the NVadsA10 v5-series (NVIDIA A10). The retirement notice links to Microsoft’s migration guidance rather than naming a target inline. Search your infrastructure-as-code for the eight retired size strings, repoint each to an equivalent current-generation SKU, and re-test GPU drivers, display/encoding, and partitioning/licensing — these differ across GPU generations and vendors. Since the VMs are already deallocated, treat this as recovery: redeploy on the new size, reattach disks, validate, resume.
Entry changelog
- — last reviewed.
- — Entry created from Microsoft's official Azure Updates retirement notice (id 573415, published 30 September 2026). The Azure Updates page is JavaScript-rendered and does not fetch server-side, so the retirement date (30 September 2026), the eight affected sizes, the deallocation behavior, the 2 November 2025 Reserved-Instance end, and the 2 June 2026 Compute Pre-Purchase end were verified against Microsoft's server-rendered release-communications API (id 573415). Dates recorded exactly as stated; no inference. The notice links to migration guidance rather than naming a successor inline, so the NVads V710 v5 / NVadsA10 v5 targets are described as Azure's current GPU-VM generation, not quoted from this notice. detect: fingerprints are the eight concrete "Standard_NV*_v4" identifiers named in the notice — literal strings an IaC template contains — and target only the retiring sizes, never a successor (SOURCING §6).
Put this countdown in your README
Building on Microsoft? Drop this badge into a project’s README or docs — it shows the days left and
refreshes on its own every night from this page. 
[](https://lastcall.dev/entries/azure-nvv4-series-vm-retirement)Spot an error or a changed date? Tell us and it’s corrected the same night.