Edit

Msv2 and Mdsv2 isolated sizes retirement

  • Article

On March 31, 2027, Azure will retire the Msv2 and Mdsv2-series Medium Memory virtual machines (VM) listed: 

  • 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 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 are stopped and removed from the host. These VMs won't be billed in the deallocated state. To avoid service disruptions, refer to the instructions listed 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, 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 improvement 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 listed to migrate your M192i(d)(m)s VM to your chosen Msv3 and Mdsv3 Medium Memory Series replacement. 

Migration steps 

  1. Choose a series and size for migration. Use the pricing calculator for further insights. 

  2. Get quota for the target VM series. 

  3. Check whether the existing M192i(d)(m)s_v2 VM is part of an Availability Set or Proximity Placement Group, which can be verified in Azure portal in the VM properties. 

  4. If the VM isn't part of an Availability Set nor a Proximity Placement Group, it can be resized.   

  5. If the VM isn't part of an Availability Set, but is part of a Proximity Placement Group, you need to shut down all VMs in the PPG, resize then restart the M192i(d)(m)s_v2 VMs, then restart the other VMs in the PPG. 

  6. If the VM is part of an Availability Set, check your records to determine if the Availability Set is pinned to a specific M-series compute cluster for proximity purposes (for example, to collocate with services like NFS that shares hosted on Azure NetApp Files). If you aren't sure about pinning having taken place, open an Azure Support Request to confirm. 

  7. 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 for every VM of the Availability Set. 

  8. If the VM is part of a non-pinned Availability set and a Proximity Placement Group, you have two options: 

  9. If your VM is part of a pinned Availability set or if you can't switch your availability option to Availability Zone (as recommended above), open an Azure Support request to assist with resizing.   

Help and support 

If you have questions, ask community experts in Microsoft Q&A. If you have a support plan and need technical help, create a support request: 

In the Help + support page, select Create a support request. Follow the New support request page instructions. Use the following values: 

  1. For Issue type, select Technical. 

  2. For Service, select My services. 

  3. For Service type, select Virtual Machine running Windows/Linux or Virtual Machine running SAP in case you run SAP application workloads. 

  4. For Resource, select your VM. 

  5. For Problem type, select Assistance with resizing my VM. 

  6. For Problem subtype, select the option that applies to you. 

  7. Follow instructions in the Solutions and Details tabs, as applicable, and then Review + create.