Current VM is being retired, how do you migrate

Question

I recieved a notice from MS that my Azure VM is being retired and I need to migrate. Is there a good guide on how to do this? I can't seem to find one.

Answer 1

Hi Brent,

First, you have a little over 3 years to migrate since the deadline is November 15, 2028, so you have plenty of time.

Second, which precise size (e.g. Standard_B2s) is your current VM? You can see this on Overview blade if you navigate to your VM in portal. Giving me exact size will help me make recommendation.

Third, to maintain same/similar pricing with similar specifications/performance you would migrate to B series V2. To do this you will need to deal with the fact that B series V2 VMs do not have temporary disk, so you will need to take snapshot of your existing VM, create new VM from it, and make any needed adjustments (like moving paging file) to account for not having temporary disk.

How do I migrate from a VM size with local temp disk to a VM size with no local temp disk?

https://learn.microsoft.com/en-us/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---

Additionally, you may need to request additional quota for Standard Bsv2 Family vCPUs. To do this you would navigate to Quotas in Azure portal using link below:

https://portal.azure.com/#view/Microsoft_Azure_Capacity/QuotaMenuBlade/~/myQuotas

In search box enter bsv2 , click on Region filter and select the region you need, then click the pencil icon to the right of the Standard Bsv2 Family vCPUs line to request increase.

Please click Accept Answer and upvote if the above was helpful.

Thanks.

-TP

Answer 2

Thanks for reaching out! I understand you’ve received a notice from Microsoft that your Azure VM is being retired. VM B-series retirement is on November 15, 2028,

According to the below Microsoft documentation:

https://learn.microsoft.com/en-us/azure/virtual-machines/sizes/resize-vm?tabs=portal#:~:text=and%20deployment%20region.-,Limitations,-You%20can%27t%20resize

Limitations**:**

You can't resize a VM size that has a local temp disk to a VM size with no local temp disk and vice versa. The only combinations allowed for resizing are:

• VM (with local temp disk) -> VM (with local temp disk); and
• VM (with no local temp disk) -> VM (with no local temp disk).

For a work-around, see How do I migrate from a VM size with local temp disk to a VM size with no local temp disk? 

Workaround/Solution:

What you can do is stop the VM, create snapshot of disk, create disk from snapshot, then create VM from disk, with selected Bv2 as size. Once you verify the new VM is working okay you can delete the old VM and its disk, network interface, snapshot, etc.

Below are instructions for the process I just described:

https://learn.microsoft.com/en-us/azure/virtual-machines/attach-os-disk?tabs=portal

To make sure I point you in the right direction, could you please share a bit more info first?

1. Which VM size or series are you currently using (for example, D-series, Fsv2, or something else)?
2. Which operating system is running on the VM, and in which Azure region is it deployed?
3. Do you have multiple VMs affected, or just one?
4. Are these production workloads, or more like dev/test environments?

This will help us figure out the best approach and tools for your migration.