Retiring F, Fs, Fsv2, Lsv2, G, Gs, Av2, Amv2, and B-series Azure VMs November 15,2025

Question

Retiring F, Fs, Fsv2, Lsv2, G, Gs, Av2, Amv2, and B-series Azure VMs November 15,2025

Faisal Riaz 175

Hi We have 6 VMs in our two subscriptions. 5 of these VMs are Standard B2s ( Linux + Windows ) and 1 Standard B1s. I have following questions

Does these retiring VM include B2s series ?
How It will effect us if we do not update VM?
If yes what is closest possible available VM?
What is the migration plan for Dev and Prod VM?
Would it change IP/SSH Keys?
How would i retain all my disks Data in updated VMs?

0 comments

Answer accepted by question author

Stanislav Zhelyazkov 29,826 MVP Volunteer Moderator

Hi,

Does these retiring VM include B2s series ? No. Check migration guide where you can see you need to upgrade to Bv2 series from B.
How It will effect us if we do not update VM? - If you do not update after that date that might affect the availability of your VMs. At some point there might be even hareder deadline where your VM is shutdown completely.
If yes what is closest possible available VM? Bv2 series. Check migration guide link.
What is the migration plan for Dev and Prod VM? - This question is not clear. Requires more details. But if you have VMs that are part of your development and production environment it is best to migrate first your development VMs first, make sure all is good and you know how to process will go and what will be the downtime and continue to production VMs.
Would it change IP/SSH Keys? No.
How would i retain all my disks Data in updated VMs? Everything is retained. This is just changing the SKU of the VM which just requires short downtime until the SKU is changed. Does not affect the OS.

Please "Accept the answer" if the information helped you. This will help us and others in the community as well.

ChaoticCoder 20 Reputation points

2025-10-24T04:05:46.74+00:00

Hello,
No wonder so many questions are being raised on this topic because neither the email nor the migration guide you provided are clear.

For example, the migration guide is mum on B series under the FAQ question "Which Sizes Are Being Retired?". Doesn't this make one thing B series is unaffected?
Stanislav Zhelyazkov 29,826 Reputation points MVP Volunteer Moderator

2025-10-24T06:27:36.1633333+00:00

Yes, there are gaps in the announcement and the documentation in terms of not explaining well that B-series and Bv2-series are two different things and only B-series which are basically v1 are the only ones being retired. Note though that the migration guide says that you should migrate from B-series to Bv2-series.

Answer accepted by question author

Andreas Baumgarten 132.7K MVP Volunteer Moderator

Hi @Faisal Riaz ,

Does these retiring VM include B2s series ?

Yes. Based on the announcement the B-series will be retired in November 2028.

Please take a look at this announcement: Retirement: The F, Fs, Fsv2, Lsv2, G, Gs, Av2, Amv2, and B series VMs are retiring in 2028

How It will effect us if we do not update VM?

As far as I know VMs with a retired VM SKU will be deallocated after the retirement date.

If yes what is closest possible available VM?

Please take a look here to check the recommended VM SKUs: Recommended Replacement VM Series

What is the migration plan for Dev and Prod VM?

Here you can find a migration plan: Migration Steps

Would it change IP/SSH Keys?

No. Resizing an Azure VM should not affect the NIC (IP) attached to the VM. Same for SSH Keys.

How would i retain all my disks Data in updated VMs?

Before any migration I would recommend to take a backup. Resizing an Azure VM should not affect the managed disks attached to the VM.

(If the reply was helpful please don't forget to upvote and/or accept as answer, thank you)

Regards

Andreas Baumgarten

ChaoticCoder 20 Reputation points

2025-10-24T04:08:35.11+00:00

Can this get any more confusing? @Stanislav Zhelyazkov is saying No to the question of "is B2s being retired?". 9 minutes later @Andreas Baumgarten is saying Yes to the same pointed question. Who is correct?
Andreas Baumgarten 132.7K Reputation points MVP Volunteer Moderator

2025-10-24T05:32:34.84+00:00

Hi @ChaoticCoder ,

i think the confusion is caused by a renaming of the old "B-Series" in "B v1 Series" by Microsoft. This happens after Microsoft introduced the new "B-Series v2".

To be more clear:
B Series -> now renamed as B-Series v1 -> will be retired November 2028

B-Series v2 -> still named B-Series v2 -> will not be retired November 2028

Hope this is more clear now.

Sorry for the confusion.

(If the reply was helpful please don't forget to upvote and/or accept as answer, thank you)

Regards

Andreas Baumgarten
Stanislav Zhelyazkov 29,826 Reputation points MVP Volunteer Moderator

2025-10-24T06:34:14.7333333+00:00

As Andreas says the confusion is caused solely by Microsoft of not marking B-series as Bv1-series or B-series v1 when B-series v2 were announced. That is causing the message on the retirement to be confusing. The migration guide tries to correct it a little bit because it ask you to migrate from v1 size to v2 size for B-series but when there are two contradicting messages that brings more confusion.

3 additional answers

Your answer

ChaoticCoder 20 Reputation points

2025-10-24T04:05:46.74+00:00

Hello,
No wonder so many questions are being raised on this topic because neither the email nor the migration guide you provided are clear.

For example, the migration guide is mum on B series under the FAQ question "Which Sizes Are Being Retired?". Doesn't this make one thing B series is unaffected?
Stanislav Zhelyazkov 29,826 Reputation points MVP Volunteer Moderator

2025-10-24T06:27:36.1633333+00:00

Yes, there are gaps in the announcement and the documentation in terms of not explaining well that B-series and Bv2-series are two different things and only B-series which are basically v1 are the only ones being retired. Note though that the migration guide says that you should migrate from B-series to Bv2-series.
ChaoticCoder 20 Reputation points

2025-10-24T04:08:35.11+00:00

Can this get any more confusing? @Stanislav Zhelyazkov is saying No to the question of "is B2s being retired?". 9 minutes later @Andreas Baumgarten is saying Yes to the same pointed question. Who is correct?
Andreas Baumgarten 132.7K Reputation points MVP Volunteer Moderator

2025-10-24T05:32:34.84+00:00

Hi @ChaoticCoder ,

i think the confusion is caused by a renaming of the old "B-Series" in "B v1 Series" by Microsoft. This happens after Microsoft introduced the new "B-Series v2".

To be more clear:
B Series -> now renamed as B-Series v1 -> will be retired November 2028

B-Series v2 -> still named B-Series v2 -> will not be retired November 2028

Hope this is more clear now.

Sorry for the confusion.

(If the reply was helpful please don't forget to upvote and/or accept as answer, thank you)

Regards

Andreas Baumgarten
Stanislav Zhelyazkov 29,826 Reputation points MVP Volunteer Moderator

2025-10-24T06:34:14.7333333+00:00

As Andreas says the confusion is caused solely by Microsoft of not marking B-series as Bv1-series or B-series v1 when B-series v2 were announced. That is causing the message on the retirement to be confusing. The migration guide tries to correct it a little bit because it ask you to migrate from v1 size to v2 size for B-series but when there are two contradicting messages that brings more confusion.

Answer 1

Anonymous

Faisal Riaz

Welcome to Microsoft Q&A Platform. Thank you for reaching out & hope you are doing well.

B-series (Standard B1s, B2s, etc.) has not yet been announced for retirement as of October 2025. However, there is already a long-term roadmap indicating the B-series will retire on November 15, 2028, based on Azure retirement notices shared in community and support documentation

https://learn.microsoft.com/en-us/azure/virtual-machines/sizes/retirement/retired-sizes-list

If a VM series reaches its retirement date and you do not migrate or resize, Microsoft will automatically deallocate those VMs. Once deallocated:

You cannot restart them and stop incurring billing. however data disks remain intact, but the VM won’t run until it is moved to a supported size.

Virtual machine series details : https://azure.microsoft.com/en-us/pricing/details/virtual-machines/series/

Migration guide is designed for users of Azure General Purpose virtual machines (VMs), which are scheduled for retirement: https://learn.microsoft.com/en-us/azure/virtual-machines/migration/sizes/d-ds-dv2-dsv2-ls-series-migration-guide#recommended-replacement-vm-series

And if you use a static Public or Private IP (associated via Azure NIC), it will remain unchanged after resizing.A dynamic IP however, may change IP's.

Attached disks remain attached during a size change or migration within the same region and resource group.

Let us know if the suggested steps helps or you need further assistance on this issue.

Regards

Himanshu

Gupta1, Sachin 0 Reputation points

2025-10-19T20:56:50.3866667+00:00

Hi,

What all series includes under B-series ? does it include b2ms ,etc.
Stanislav Zhelyazkov 29,826 Reputation points MVP Volunteer Moderator

2025-10-20T05:22:17.5633333+00:00

B2 are not included. That was already provided in the answers that are accepted. There are B v1 and B v2 series. Only the B1 v1 are being retired. Because initially only B v1 were available they were named without the v1 at the end.
Gupta1, Sachin 0 Reputation points

2025-10-20T08:53:35.6066667+00:00

Can considered that the following B series SKUs will not be retired as part of the recent announcement?
Stanislav Zhelyazkov 29,826 Reputation points MVP Volunteer Moderator

2025-10-20T08:59:08.89+00:00

In green not retired. In red to be retired.
Nenad Novosel 0 Reputation points

2025-10-20T10:16:37.2233333+00:00

Currently I'm unable to choose any B series v2 to create/migrate VM. I'm on WestEU region, and need Win server.
Stanislav Zhelyazkov 29,826 Reputation points MVP Volunteer Moderator

2025-10-20T10:21:08.8866667+00:00

@Nenad Novosel you have to open support ticket for these kind of things. Usually not all sizes are available for all subscription types and might require quota increase for that size family in order to use them.

Answer 2

Hello @Faisal Riaz

The retiring VM series includes the B2s series. Failure to update will result in service interruption. The closest replacement is the Bv2 series.

Does these retiring VM include B2s series? Yes
How It will effect us if we do not update VM? VMs will stop working after the retirement date.
What is the migration plan for Dev and Prod VM? Migrate Dev first, then Prod with a maintenance window and rollback plan.
Would it change IP/SSH Keys? IP addresses likely to change, SSH keys on OS disk will be retained.
How would i retain all my disks Data in updated VMs? Reuse the existing managed disks.

If the Answer is helpful, please click Accept Answer and Up-Vote, so that it can help others in the community looking for help on similar topics.

Answer 3

Nenad Novosel 0

Hi,

@Himanshu Shekhar kindly explain.

When I try to create new virtual machine, with Windows OS, I only see B2s machines, no "new" ones like Bsv2. Why there is no Bsv2, as this is sugessted to be VM to migrate from B

User's image

I'm currently using B2ms (WinOS+SQL, WestEu), and only D2s_v3 looks like viable options, however my cost will go up 100%.

User's image

Anonymous

2025-10-17T05:24:03.8166667+00:00

@Nenad Novosel - we have reached for additional details via private messages
Nenad Novosel 0 Reputation points

2025-10-17T06:16:38.6666667+00:00

sorry, I didn't get any private message
Anonymous

2025-10-20T11:53:10.62+00:00

Not all VM sizes or generations are available in every Azure region, including West Europe. Microsoft limits new SKUs based on capacity planning, hardware supply, or rollout schedules. Additionally, also check for Bsv2 availability in nearby regions as well.
Mohd Hamzani Bin Mohamad Ali 0 Reputation points

2026-08-10T04:05:10.61+00:00
B2ms (v1) has a temporary/resource disk attached, while the Bsv2/Basv2 (v2) series don't. That's why you won't see Bv2 sizes offered when resizing directly in the portal, and why a direct resize via PowerShell/CLI also fails — Azure blocks in-place resize between a VM size with a resource disk and one without (you'll typically see something like OperationNotAllowed: resource disk to non-resource disk).

So this isn't a simple resize — it needs to be handled as a redeploy:

Snapshot the OS disk and any data disk(s) on the existing B2ms VM.

Create new managed disks from those snapshots (this avoids carrying over the old size's disk-architecture metadata — attaching the original disks directly to a new VM of the target size fails with the same error, even though it's not technically a "resize").

Deallocate the old VM. You don't need to detach or delete anything on it — its disks and NIC can stay exactly as they are. This also means the old VM remains available as an instant rollback the whole time you're working on the new one.

Deploy a new VM directly on the target Bsv2/Basv2 size, attaching the new snapshot-derived OS and data disk(s) together in the same az vm create (or ARM/Bicep) call, along with a new NIC. Attaching the disks in one step matters if you're running SQL Server or similar — attaching the OS disk first can let services start before the data disk is present, which can cause database recovery issues.

If you need to keep the same static IP: while the old VM is deallocated, update its NIC's IP configuration to a different, unused address (this works even while the NIC stays attached — no detach needed). This frees the production IP, which you then assign directly to the new VM's new NIC in step 4.