Learn Editor: Update msv2-mdsv2-migration-guide.md

Author: iamwilliew

articles/virtual-machines/msv2-mdsv2-migration-guide.md

@@ -15,3 +15,65 @@ ms.date:     01/10/2024
 
 # Msv2 and Mdsv2 Migration Guide
 
+On March 31, 2027, Azure will retire the Msv2 and Mdsv2-series Medium Memory virtual machines (VM) listed below: 
+
+- Msv2 Medium Memory Diskless 
+
+   - Standard_M192is_v2  
+
+      - Standard_M192ims_v2 
+
+- Mdsv2 Medium Memory with Disk 
+
+   - Standard_M192ids_v2 
+
+      - Standard_M192idms_v2 
+
+From now to March 31, 2027, you can continue to use the VMs listed above without disruption. On March 31, 2027, the remaining VMs with these specific sizes on your subscription will be set to a deallocated state. These VMs will be stopped and removed from the host. These VMs will no longer be billed in the deallocated state. To avoid service disruptions, please follow our instructions below to migrate to your selected Mv3 replacement size by March 31, 2027.   
+
+#### Migrate workloads to Mv3 Medium Memory Series VMs 
+
+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. 
+
+Follow the instructions below 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. 
+
+### Migration Steps 
+
+Choose a [series and size](/azure/virtual-machines/msv3-mdsv3-medium-series) for migration. Leverage the [pricing calculator](https://azure.microsoft.com/en-us/pricing/calculator/) for further insights. 
+
+[Get quota for the target VM series](/azure/quotas/per-vm-quota-requests). 
+
+Check whether the existing M192i(d)(m)s VM is part of an [Availability Set](/azure/virtual-machines/availability-set-overview) or [Proximity Placement Group](/azure/virtual-machines/co-location). You can check in Azure Portal in the VM properties. 
+
+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).   
+
+If the VM is part of an Availability Set, check your records to determine whether you asked Microsoft to pin the Availability Set to a specific M-series compute cluster for proximity purposes (e.g. to collocate with services like NFS shares hosted on Azure NetApp Files). If you are not sure about pinning having taken place, open an [Azure Support Request](https://ms.portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/newsupportrequest) to confirm. 
+
+If your VM is part of a non-pinned Availability Set, you need to shut down all VMs in that particular Availability Set and go through the [resize procedure](/azure/virtual-machines/resize-vm?tabs=portal) for every single VM of the Availability Set. 
+
+If the VM or Availability Set is part of a Proximity Placement Group, it is recommended to switch availability options to [zonal deployment](/azure/reliability/availability-zones-overview?toc=%2Fazure%2Fvirtual-machines%2Ftoc.json&tabs=azure-cli) using the script linked below or setting up Database Replication (e.g. HANA System Replication, SQL Server AlwaysOn). Zonal deployments significantly reduce the possibility of allocation failure.  
+
+[How to Migrate a Highly Available SAP System in Azure from Availability Set to Availability Zone](https://github.com/Azure/SAP-on-Azure-Scripts-and-Utilities/tree/main/Move-VM-from-AvSet-to-AvZone/Move-Regional-SAP-HA-To-Zonal-SAP-HA-WhitePaper) 
+
+If your VM is part of a pinned Availability set or if you cannot switch your availability option to Availability Zone (as recommended in step 5 above), open an Azure Support request to assist with resizing.   
+
+### Help and support 
+
+If you have questions, ask community experts in [Microsoft Q&A](/answers/topics/azure-virtual-machines.html). If you have a support plan and need technical help, create a support request: 
+
+In the [Help + support page](https://ms.portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/newsupportrequest), select Create a support request. Follow the New support request page instructions. Use the following values: 
+
+For Issue type, select Technical. 
+
+For Service, select My services. 
+
+For Service type, select Virtual Machine running Windows/Linux or Virtual Machine running SAP in case you run SAP application workloads. 
+
+For Resource, select your VM. 
+
+For Problem type, select Assistance with resizing my VM. 
+
+For Problem subtype, select the option that applies to you. 
+
+Follow instructions in the Solutions and Details tabs, as applicable, and then Review + create. 
+