Moving Vm's to a new reservation

Question

Moving Vm's to a new reservation

pierre shiraziefard 85

Hello, this is what I have currently looking for a solution:

standard_B4ms North Central US

standard_B4ms South Central US (stopped currently)

both above on pay as you go subscription

B4ms is not available in Chicago North Central but a replacement Basv2 is available same specs.

Question, how do I move the existing B4ms to a new purchased reservation with a Basv2?

Do i have to load all software on a new VM or is there a way to transfer from one machine to another?

I am trying to eliminate a manual re-installation of our software components. I also want to make sure the new reserved VM I stand up will use 100% of the reserved resources.

Thanks.

Nikhil Duserla 9,940 Reputation points Microsoft External Staff Moderator

2026-07-10T14:24:18.2233333+00:00
Hello @pierre shiraziefard ,

Since Standard_B4ms and Standard_B4as_v2 belong to different VM size families, an existing Reserved VM Instance (RI) purchased for B4ms cannot be applied to a B4as_v2 VM.

To migrate your workload from B4ms to B4as_v2 while preserving the operating system and application configuration:

Create a managed image or snapshot of the existing B4ms VM.

Deploy a new Standard_B4as_v2 VM using the captured image.

The new VM will retain the same operating system, installed applications, and configuration as the source VM.

Reconfigure any networking components (public/private IP addresses, DNS records, Network Security Groups, Load Balancer backend pools, etc.) as required.

Validate application functionality and performance on the new VM.

After successful validation, decommission the original B4ms VM.

Also, Detach and reattach data disks: If application data resides on separate managed disks, attach those disks to the newly deployed VM after deployment.

Before purchasing the reservation and migrating the workload, verify that:

Standard_B4as_v2 is available in the North Central US region.

The CPU, memory, and performance characteristics of B4as_v2 meet your application's requirements.

Let me know if you have any further queries.
pierre shiraziefard 85 Reputation points

2026-07-10T14:32:44.73+00:00

OK thanks.

Your answer

Nikhil Duserla 9,940 Reputation points Microsoft External Staff Moderator

2026-07-10T14:24:18.2233333+00:00

Hello @pierre shiraziefard ,

Since Standard_B4ms and Standard_B4as_v2 belong to different VM size families, an existing Reserved VM Instance (RI) purchased for B4ms cannot be applied to a B4as_v2 VM.

To migrate your workload from B4ms to B4as_v2 while preserving the operating system and application configuration:

Create a managed image or snapshot of the existing B4ms VM.

Deploy a new Standard_B4as_v2 VM using the captured image.

The new VM will retain the same operating system, installed applications, and configuration as the source VM.

Reconfigure any networking components (public/private IP addresses, DNS records, Network Security Groups, Load Balancer backend pools, etc.) as required.

Validate application functionality and performance on the new VM.

After successful validation, decommission the original B4ms VM.

Also, Detach and reattach data disks: If application data resides on separate managed disks, attach those disks to the newly deployed VM after deployment.

Before purchasing the reservation and migrating the workload, verify that:

Standard_B4as_v2 is available in the North Central US region.

The CPU, memory, and performance characteristics of B4as_v2 meet your application's requirements.

Let me know if you have any further queries.
pierre shiraziefard 85 Reputation points

2026-07-10T14:32:44.73+00:00

OK thanks.