Msv2 and Mdsv2 isolated sizes retirement

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.

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: 

   • 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. 

   • Switch availability options to Availability Zone as described using the open source supported  script and procedure linked or setting up Database Replication (for example, HANA System Replication, SQL Server AlwaysOn).  

     • How to Migrate a Highly Available SAP System in Azure from Availability Set to Availability Zone 

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 

1. For Azure Subscription, select your subscription.
2. For Support type, select Technical.
3. For Service type, select Virtual Machine running Windows/Linux.
4. For Problem type, select one suitable option that applies to you. for example, Performance.
5. For Category, select one suitable option that applies to you. for example, Slow virtual machine.
6. For Issue title, enter a summary of your request. for example, Assistance with resizing my VM from <VM_old_size> to <VM_new_size>.
7. Select Next, and Next: Details + Submit.
8. Fill in the mandatory items in Get support page and submit your request.