Skip to content

Commit f53bc54

Browse files
authored
Update msv2-mdsv2-isolated-retirement.md
1 parent d3bc17b commit f53bc54

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/virtual-machines/msv2-mdsv2-isolated-retirement.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ From now to March 31, 2027, you can continue to use the VMs listed without disru
3131

3232
#### Migrate workloads to Mv3 Medium Memory Series VMs 
3333

34-
The [Msv3 and Mdsv3 Medium Memory Series](/azure/virtual-machines/msv3-mdsv3-medium-series), powered by 4th generation Intel® Xeon® Scalable processors, are the next generation of memory-optimized VM sizes delivering faster performance, lower total cost of ownership and improved resilience to failures compared to previous generation Mv2 VMs. The Mv3 MM series offers VM sizes of up to 4TB of memory and 4,000 MBps throughout to remote storage and provides up to 25% networking performance improvements over previous generations. 
34+
The [Msv3 and Mdsv3 Medium Memory Series](/azure/virtual-machines/msv3-mdsv3-medium-series), powered by 4th generation Intel® Xeon® Scalable processors, are the next generation of memory-optimized VM sizes delivers faster performance, lower total cost of ownership and improved resilience to failures compared to previous generation Mv2 VMs. The Mv3 MM series offers VM sizes of up to 4TB of memory and 4,000 MBps throughout to remote storage and provides up to 25% networking performance improvements over previous generations. 
3535

3636
Follow the instructions listed to migrate your [M192i(d)(m)s VM](/azure/virtual-machines/msv2-mdsv2-series) to your chosen [Msv3 and Mdsv3 Medium Memory Series](/azure/virtual-machines/msv3-mdsv3-medium-series) replacement. 
3737

@@ -41,7 +41,7 @@ Follow the instructions listed to migrate your [M192i(d)(m)s VM](/azure/virtual-
4141

4242
2. [Get quota for the target VM series](/azure/quotas/per-vm-quota-requests)
4343

44-
3. Check whether the existing M192i(d)(m)s_v2 VM is part of an [Availability Set](/azure/virtual-machines/availability-set-overview) or [Proximity Placement Group](/azure/virtual-machines/co-location). This can be verified in Azure Portal in the VM properties. 
44+
3. Check whether the existing M192i(d)(m)s_v2 VM is part of an [Availability Set](/azure/virtual-machines/availability-set-overview) or [Proximity Placement Group](/azure/virtual-machines/co-location), which canverified in Azure Portal in the VM properties. 
4545

4646
4. If the VM is not part of an Availability Set nor a Proximity Placement Group, [it can be resized](/azure/virtual-machines/resize-vm?tabs=portal).   
4747

0 commit comments

Comments
 (0)