Skip to content

Commit e999261

Browse files
learn-build-service-prod[bot]learn-build-service-prod[bot]
authored
Merge pull request #2303 from MicrosoftDocs/main
Auto Publish – main to live - 2025-09-20 05:00 UTC
2 parents 51c92ab + 66ca6ad commit e999261

File tree

4 files changed

+144
-2
lines changed

4 files changed

+144
-2
lines changed

‎articles/virtual-machine-scale-sets/virtual-machine-scale-sets-upgrade-policy.md‎

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,6 @@ Each Virtual Machine Scale Set has an **upgrade policy mode** which determines h
2424
- Add/ remove a data disk
2525
- Add/ remove extensions
2626
- Adding availability zones
27-
- Changing fault domain information
2827

2928
Additionally, there can be situations where you might want specific instances in your scale set to be treated differently from the rest. For example, certain instances in the scale set could be needed to perform different tasks than the other members of the scale set. In these situations, [Instance Protection](virtual-machine-scale-sets-instance-protection.md) or [custom metrics for rolling upgrade policy (preview)](virtual-machine-scale-sets-rolling-upgrade-custom-metrics.md) provide the controls needed to protect these instances from being upgraded along side the other instances.
3029

@@ -67,7 +66,6 @@ Some upgrades require a virtual machine restart while others can be completed wi
6766
- Image Reference updates
6867
- Virtual machine size changes
6968
- Adding Availability Zones
70-
- Fault Domain changes
7169
- Proximity Placement Group changes
7270

7371
> [!NOTE]

‎articles/virtual-machines/TOC.yml‎

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -575,8 +575,12 @@
575575
href: nv-series-migration-guide.md
576576
- name: NVv3 series
577577
href: ./sizes/gpu-accelerated/nvv3-series.md
578+
- name: NVv3 series retirement
579+
href: ./sizes/gpu-accelerated/nvv3-series-retirement.md
578580
- name: NVv4 series
579581
href: ./sizes/gpu-accelerated/nvv4-series.md
582+
- name: NVv4 series retirement
583+
href: ./sizes/gpu-accelerated/nvv4-retirement.md
580584
- name: NVadsA10_v5 series
581585
href: ./sizes/gpu-accelerated/nvadsa10v5-series.md
582586
- name: Nvads V710 v5-series

‎articles/virtual-machines/sizes/gpu-accelerated/nvv3-series-retirement.md‎

Lines changed: 69 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,69 @@
1+
---
2+
# Required metadata
3+
# For more information, see https://learn.microsoft.com/en-us/help/platform/learn-editor-add-metadata
4+
# For valid values of ms.service, ms.prod, and ms.topic, see https://learn.microsoft.com/en-us/help/platform/metadata-taxonomies
5+
6+
title: NVv3 series retirement
7+
description: 'This article contains the details of the NVv3-series retirement. '
8+
author: yangnicole-ml # GitHub alias
9+
ms.author: yangnicole
10+
ms.service: azure-virtual-machines
11+
ms.topic: article
12+
ms.date: 06/13/2025
13+
---
14+
15+
# Migrate your NVv3-series virtual machines by September 30, 2026
16+
> [!NOTE]
17+
> 1-year and 3-year RI purchases for the NVv3-series will end September 30, 2025.
18+
19+
On September 30, 2026, Microsoft Azure will retire the Standard_NV12s_v3, Standard_NV24s_v3, Standard_NV24ms_v3, Standard_NV32ms_v3, and Standard_NV48s_v3 virtual machines (VMs) in the NVv3-series virtual machines (VMs). To avoid any disruptions to your service, we recommend that you change the VM sizing for your workloads from the current NVv3-series VMs to the newer VM series in the same NV product line.
20+
21+
Microsoft is recommending the Azure [NVadsA10_v5-series](/azure/virtual-machines/sizes/gpu-accelerated/nvadsa10v5-series?tabs=sizebasic) VMs, which offer greater GPU memory bandwidth per GPU. With the NVadsA10_v5-series VMs, Azure introduces VMs with partial NVIDIA GPUs and each VM instance comes with a GRID license. This license gives you the flexibility to use an NV instance as a virtual workstation for a single user or 25 concurrent users can connect to the VM for a virtual application scenario. These VMs are targeted for GPU accelerated graphics applications, virtual desktops, visualizations, or small AI workloads.
22+
23+
Depending on the workload being run, regional affinity, and cost preferences, other VMs that may be migrated to from the NVv3-series VMs include [NCasT4_v3](/azure/virtual-machines/sizes/gpu-accelerated/ncast4v3-series?tabs=sizebasic) and [NVadsV710_v5](/azure/virtual-machines/sizes/gpu-accelerated/nvadsv710-v5-series?tabs=sizebasic):
24+
25+
|Workload|Recommended SKU to Migrate to|
26+
| -------- | -------- |
27+
|GPU accelerated graphics applications, virtual desktops, visualizations, or small AI workloads. |NVadsA10_v5|
28+
|Offline inferencing workloads where latency is not a primary concern, and there is an interest in purchasing smaller VM SKUs or reducing costs. |NCasT4_v3|
29+
|Graphics, visualization, or small AI workloads such as SLM inferencing and semantic search where optimal performance is not a priority or there is an interest in reducing costs.|NVadsV710_v5|
30+
31+
## How does the retirement of the NVv3-series virtual machines affect me?
32+
33+
**After September 30th, 2026, any remaining NVv3-series virtual machines (VMs) subscriptions will be set to a deallocated state. They'll stop working and no longer incur billing charges. NVv3 will no longer be under SLA or have support included.**
34+
35+
> [!NOTE]
36+
> This retirement only impacts the virtual machine sizes in the NVv3-series powered by NVIDIA Tesla M60 GPUs. For NVv4-series virtual machines, please refer to the NVv4-series virtual machines retirement guide. This retirement announcement does not apply to NVadsA10_v5 or NVadsV710_v5 series virtual machines.
37+
38+
## What action do I need to take before the retirement date?
39+
40+
You need to resize or deallocate your NVv3-series VMs. We recommend that you change VM sizes for these workloads from the original NVv3-series VMs to the NVadsA10_v5-series VMs (or an alternative).
41+
42+
The [NVadsA10_v5-series](/azure/virtual-machines/sizes/gpu-accelerated/nvadsa10v5-series?tabs=sizebasic) is powered by NVIDIA A10 GPUs and AMD EPYC™ 74F3V(Milan) processors. The VMs feature up to 2 NVIDIA A10 GPUs with 24GB memory each, up to 72 non-multithreaded AMD EPYC 74F3V processor cores and 880 GiB of system memory. Check [Azure Regions by Product page](https://azure.microsoft.com/explore/global-infrastructure/products-by-region/) for region availability. Visit the [Azure Virtual Machine pricing page](https://azure.microsoft.com/pricing/details/virtual-machines/) for pricing information.
43+
44+
## Steps to change VM size
45+
46+
1. Choose a series and size. Refer to the above tables for Microsoft’s recommendation. You can also file a support request if more assistance is needed.
47+
48+
1. [Request quota for the new target VM](/azure/azure-portal/supportability/per-vm-quota-requests).
49+
50+
1. You can [resize the virtual machine](/azure/virtual-machines/resize-vm).
51+
52+
## Help and support
53+
54+
If you have a support plan and you need technical help, create a [support request](https://portal.azure.com/).
55+
56+
1. Under *Issue type*, select **Technical**.
57+
58+
1. Under *Subscription*, select your subscription.
59+
60+
1. Under *Service*, click **My services**.
61+
62+
1. Under *Service type*, select **Virtual Machine running Windows/Linux**.
63+
64+
1. Under *Summary*, enter the summary of your request.
65+
66+
1. Under *Problem type*, select **Assistance with resizing my VM.**
67+
68+
1. Under *Problem subtype*, select the option that applies to you.
69+

‎articles/virtual-machines/sizes/gpu-accelerated/nvv4-retirement.md‎

Lines changed: 71 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,71 @@
1+
---
2+
# Required metadata
3+
# For more information, see https://learn.microsoft.com/en-us/help/platform/learn-editor-add-metadata
4+
# For valid values of ms.service, ms.prod, and ms.topic, see https://learn.microsoft.com/en-us/help/platform/metadata-taxonomies
5+
6+
title: NVv4 series retirement
7+
description: 'This article contains the details of the NVv4-series retirement. '
8+
author: yangnicole-ml # GitHub alias
9+
ms.author: yangnicole
10+
ms.service: azure-virtual-machines
11+
ms.topic: article
12+
ms.date: 06/13/2025
13+
---
14+
15+
# Migrate your NVv4-series virtual machines by September 30, 2026
16+
> [!NOTE]
17+
> There is a known resize operation error that occurs when migrating from the NVv4-series to the NVads_V710_v5-series. Microsoft is working on a fix that will be implemented in April 2026. In the meantime, we suggest that you follow this [workaround](/azure/virtual-machines/azure-vms-no-temp-disk#how-do-i-migrate-from-a-vm-size-with-local-temp-disk-to-a-vm-size-with-no-local-temp-disk---).
18+
19+
> [!NOTE]
20+
> 1-year and 3-year RI purchases for the NVv4-series will end September 30, 2025.
21+
22+
On September 30, 2026, Microsoft Azure will retire the Standard_NV4as_v4, Standard_NV8as_v4, Standard_NV16as_v4, and Standard_NV32as_v4 virtual machines (VMs) in NVv4-series virtual machines (VMs). To avoid any disruption to your service, we recommend that you change the VM sizing for your workloads from the current NVv4-series VMs to the newer VM series in the same NV product line.
23+
24+
Microsoft is recommending the Azure [NVads_V710_v5-series](/azure/virtual-machines/sizes/gpu-accelerated/nvadsv710-v5-series?tabs=sizebasic) VMs, which offer greater GPU memory bandwidth per GPU. The NVads_V710_v5-series VMs take advantage of the AMD Simultaneous Multithreading technology to assign dedicated vCPU threads to each VM and support NVMe for ephemeral local storage capability.
25+
26+
The NVads_V710_v5-series enables right-sizing for demanding GPU-accelerated graphics applications and cloud-based virtual desktops to provide a seamless end user experience while providing a cost-effective choice for a full range of graphics-enabled virtual desktop experiences. The VMs are also sized to deliver high-quality, interactive gaming experiences in the cloud, optimized for rendering and streaming complex graphics. In addition, the NVads_V710_v5-series supports small AI inference workloads such as Small Language Model (SLMs), recommendation systems, and semantic indexing, by taking advantage of the computational IP blocks in the Radeon Pro V710 GPUs.
27+
28+
|Workload|Recommended SKU to Migrate to|
29+
| -------- | -------- |
30+
|Small AI workloads such as SLM inferencing and semantic search where optimal performance is not a priority or there is an interest in reducing costs.|NVads_V710_v5|
31+
|GPU accelerated graphics applications, virtual desktops, and visualizations.|NVads_V710_v5|
32+
33+
## How does the retirement of the NVv4-series virtual machines affect me?
34+
35+
__After__ __September 30th, 2026, any remaining__ __NVv4-series virtual machines (VMs) subscriptions will be set to a deallocated state. They'll stop working and no longer incur billing charges. NVv4 will no longer be under SLA or have support included.__
36+
37+
> [!NOTE]
38+
> This retirement only impacts the virtual machine sizes in the NVv4-series powered by AMD Radeon Instinct MI25 GPUs. For NVv3-series virtual machines, please refer to the NVv3-series virtual machines retirement guide. This retirement announcement does not apply to NVadsA10_v5 or NVads_V710_v5 series virtual machines.
39+
40+
## What action do I need to take before the retirement date?
41+
42+
You need to resize or deallocate your NVv4-series VMs. We recommend that you change VM sizes for these workloads from the original NVv4-series VMs to the NVads_V710_v5-series VMs (or an alternative).
43+
44+
The [NVads_V710_v5-series](/azure/virtual-machines/sizes/gpu-accelerated/nvadsv710-v5-series?tabs=sizebasic) is powered by AMD Radeon™ Pro V710 GPUs and AMD EPYC™ 9V64 F (Genoa) processors. The VMs feature up to 1 AMD Radeon™ Pro V710 GPU with 24GB memory each, up to 28 multithreaded AMD EPYC 9V64 F processor cores and 160 GiB of system memory. Check [Azure Regions by Product page](https://azure.microsoft.com/explore/global-infrastructure/products-by-region/) for region availability. Visit the [Azure Virtual Machine pricing page](https://azure.microsoft.com/pricing/details/virtual-machines/) for pricing information.
45+
46+
## Steps to change VM size
47+
48+
1. Choose a series and size. Refer to the above tables for Microsoft’s recommendation. You can also file a support request if more assistance is needed.
49+
50+
1. [Request quota for the new target VM](/azure/azure-portal/supportability/per-vm-quota-requests).
51+
52+
1. You can [resize the virtual machine](/azure/virtual-machines/resize-vm).
53+
54+
## Help and support
55+
56+
If you have a support plan and you need technical help, create a [support request](https://portal.azure.com/).
57+
58+
1. Under _Issue type_, select __Technical__.
59+
60+
1. Under _Subscription_, select your subscription.
61+
62+
1. Under _Service_, click __My services__.
63+
64+
1. Under _Service type_, select __Virtual Machine running Windows/Linux__.
65+
66+
1. Under _Summary_, enter the summary of your request.
67+
68+
1. Under _Problem type_, select __Assistance with resizing my VM.__
69+
70+
1. Under _Problem subtype_, select the option that applies to you.
71+

0 commit comments

Comments
 (0)