SaaS · archived
Microsoft
Microsoft retired the Azure NVv3-series GPU virtual machines (Standard_NV12s_v3, NV12hs_v3, NV24s_v3, NV24ms_v3, NV32ms_v3, NV48s_v3) on 30 September 2026; any remaining NVv3 VMs are set to a deallocated state, stop working, lose SLA and support. Azure UAE North customers have an extension to 31 January 2027.
left 30 Sept 2026
Quick answers
- Is it true that Azure retired the NVv3-series GPU virtual machines on 30 September 2026 — remaining VMs are deallocated; migrate to NVadsA10 v5?
- Yes — and the date has already passed (30 Sept 2026). The NVv3-series were Azure's NVIDIA-GPU virtual machines for GPU-accelerated visualization, virtual desktops, and remote graphics workloads.
- 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 graphics and virtual-desktop workloads are the **NVadsA10 v5-series** (NVIDIA A10 GPUs), the line that superseded the NVv3/NVv4 generation (the retirement notice itself links to Microsoft's migration guidance rather than naming a target inline).
What this means for you
The NVv3-series were Azure's NVIDIA-GPU virtual machines for GPU-accelerated visualization, virtual desktops, and remote graphics workloads. As of **30 September 2026 they are retired**: Microsoft has set any remaining NVv3 VMs to a **deallocated** state, so they stop running, no longer incur billing, and are **no longer under SLA or supported**. The affected sizes are Standard_NV12s_v3, Standard_NV12hs_v3, Standard_NV24s_v3, Standard_NV24ms_v3, Standard_NV32ms_v3, and Standard_NV48s_v3. If any of these are still referenced in your ARM, Bicep, or Terraform templates, deployments of them will now fail and any that were running have been stopped — this is a hard cutover, not a deprecation warning. Reserved Instance purchases for the series had already ended on 2 November 2025. **One regional exception:** customers in the **Azure UAE North** region may keep using NVv3-series VMs past the general retirement date until an extension date of **31 January 2027**, by which point they must have migrated off.
Where to go
Azure's current-generation GPU VMs for graphics and virtual-desktop workloads are the **NVadsA10 v5-series** (NVIDIA A10 GPUs), the line that superseded the NVv3/NVv4 generation (the retirement notice itself 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_NV12s_v3, Standard_NV12hs_v3, Standard_NV24s_v3, Standard_NV24ms_v3, Standard_NV32ms_v3, Standard_NV48s_v3 — and repoint each to an equivalent NVadsA10 v5 SKU, then re-test GPU driver installation, display/encoding behavior, and licensing (GPU driver extensions and any NVIDIA GRID/vGPU entitlements differ between generations). Because the VMs are already deallocated, treat this as recovery work rather than planning: redeploy workloads on the new size, reattach or restore disks, and validate before resuming service. UAE North customers still have until 31 January 2027, but the same migration applies.
- Azure NVadsA10 v5-series (NVIDIA A10) — Azure's current-generation GPU VMs for visualization and virtual-desktop workloads
- Other Azure NV / NC GPU series sized to the workload (graphics vs. compute)
Microsoft has retired the Azure NVv3-series GPU virtual machines as of 30 September 2026. The official Azure retirement notice states that on that date Microsoft retired the Standard_NV12s_v3, Standard_NV12hs_v3, Standard_NV24s_v3, Standard_NV24ms_v3, Standard_NV32ms_v3, and Standard_NV48s_v3 sizes, and that any remaining NVv3 VMs are set to a deallocated state — they stop working, stop billing, and lose SLA and support.
What is gone
The NVv3-series were NVIDIA-GPU VMs aimed at GPU-accelerated visualization, remote workstations, and virtual-desktop graphics. This is a completed retirement, not a future deadline: deployments that reference the NVv3 sizes will now fail, and VMs that were still running have been stopped and deallocated. Reserved Instance purchases for the series had already ended on 2 November 2025.
The one exception — Azure UAE North
Microsoft carved out a single regional extension: customers running NVv3-series VMs in the Azure UAE North region may continue using them past the general retirement date, up to an extension date of 31 January 2027. Those customers must migrate off by then.
Where Microsoft points you
Azure’s current-generation GPU VMs for graphics and virtual-desktop workloads are the NVadsA10 v5-series (NVIDIA A10 GPUs) — the line 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 deployments for the six retired size strings, repoint each to an equivalent NVadsA10 v5 SKU, and re-test GPU driver installation, display/encoding, and any NVIDIA GRID/vGPU licensing — these differ across GPU generations. Because the VMs are already deallocated, this is recovery work: redeploy on the new size, reattach disks, validate, resume.
Entry changelog
- — last reviewed.
- — Entry created from Microsoft's official Azure Updates retirement notice (id 573414, 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 six affected sizes, the deallocation behavior, the 2 November 2025 Reserved-Instance end, and the Azure UAE North extension to 31 January 2027 were verified against Microsoft's server-rendered release-communications API (id 573414). Dates recorded exactly as stated; no inference. detect: fingerprints are the six concrete "Standard_NV*_v3" size identifiers named in the notice — literal strings an ARM/Bicep/Terraform template contains — and target only the retiring sizes, never the NVadsA10 v5 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-nvv3-series-vm-retirement)Spot an error or a changed date? Tell us and it’s corrected the same night.