Unable to launch a VM with b2ms instance type in MCPP subscription for EAST US.

Question

Unable to launch a VM with b2ms instance type in MCPP subscription for EAST US.

Krunal Patel 0

Hello Team,

I want to create a VM from disk created from snapshot of another subscription. But, under new MCPP subscription, I am not able to create VM with size b2ms in east us region. Kindly provide clarification on this.
User's image

User's image

If it is restricted, then how can I utilize my credits in this subscription ? Does MS team mentioned about this restriction in their documentation ?

Pranitha Sika 0 Reputation points Microsoft External Staff Moderator

2026-08-18T09:25:21.86+00:00

Hello Krunal Patel

In addition to the information above, please note that Microsoft has published guidance regarding capacity growth restrictions for previous-generation VM series starting July 2026. Standard_B2ms belongs to the impacted B-series. According to the documentation, new subscriptions cannot deploy affected SKUs, which aligns with the NotAvailableForSubscription behavior. Existing subscriptions may continue deploying these SKUs within previously approved quota, subject to capacity availability. For new deployments, Microsoft recommends considering newer-generation VM series such as Dv5/Dv6/Dv7 or Ev5/Ev6/Ev7 based on workload requirements. Can review the following guidance for more information: Previous-generation VM size series capacity growth restrictions and migration guidance.
https://learn.microsoft.com/en-us/azure/virtual-machines/migration/sizes/previous-gen-series-capacity-limitations

Can you please update us if the action plan provided was helpful?

Should there be any follow-up questions or concerns, please let us know and we shall try to address them.

If these answer your question, click "Upvote" which may be beneficial to other community members reading this thread.

1 answer

Your answer

Pranitha Sika 0 Reputation points Microsoft External Staff Moderator

2026-08-18T09:25:21.86+00:00

Hello Krunal Patel

In addition to the information above, please note that Microsoft has published guidance regarding capacity growth restrictions for previous-generation VM series starting July 2026. Standard_B2ms belongs to the impacted B-series. According to the documentation, new subscriptions cannot deploy affected SKUs, which aligns with the NotAvailableForSubscription behavior. Existing subscriptions may continue deploying these SKUs within previously approved quota, subject to capacity availability. For new deployments, Microsoft recommends considering newer-generation VM series such as Dv5/Dv6/Dv7 or Ev5/Ev6/Ev7 based on workload requirements. Can review the following guidance for more information: Previous-generation VM size series capacity growth restrictions and migration guidance.
https://learn.microsoft.com/en-us/azure/virtual-machines/migration/sizes/previous-gen-series-capacity-limitations

Can you please update us if the action plan provided was helpful?

Should there be any follow-up questions or concerns, please let us know and we shall try to address them.

If these answer your question, click "Upvote" which may be beneficial to other community members reading this thread.

Answer 1

TP 162.1K Volunteer Moderator

Hi,

Have you tried to create v5 or v6 or v7 VM in various different regions? For example, Dv5 / Dv6 / Dv7 or Ev5 / Ev6 / Ev7

Due to capacity issues they have recently restricted new deployments of many v1 - v4 VM sizes (B2ms is one that is restricted).

Below is excerpt from relevant Azure Health Advisory TRV3-YHG:

Starting 31 July 2026, Azure will implement capacity growth restrictions for the v1- v4 VM series as part of ongoing investments in newer-generation infrastructure. As a result, new deployments, capacity expansion requests, and quota increase requests for impacted VM series will not be approved. Quota already approved in existing subscriptions for these VM series will not be affected.

Impacted VM series

VM series set to retire in 31 July 2028 and subject to growth controls::

Compute optimized: F, Fs, Fsv2

General purpose: D, Ds, Dv2, Dsv2, Av2, Amv2, B, Bs

Memory optimized: G, Gs

Storage optimized: Ls, Lsv2

VM series subject to growth controls

General purpose: Dv3, Dsv3, Dv4, Dsv4, Ddv4, Ddsv4, Dav4, Dasv4

Memory optimized: Ev3, Esv3, Ev4, Esv4, Edv4, Edsv4, Eav4, Easv4

Customers currently using any of the above VM series may experience restrictions when requesting additional quota or deploying new workloads on the impacted VM series.

This change affects:

New VM deployments

VM scale-out activities requiring additional capacity

Quota increase requests

Future growth plans on impacted VM series

This change does not affect:

Existing deployments operating within Capacity currently allocated

Customers can continue running their existing workloads without interruption.

Customers planning future growth, expansion, or new deployments should evaluate migration to newer-generation VM series that provide improved performance, enhanced security, broader availability, and longer-term platform support.

Recommended VM series include:

Dv5, Dv6, and Dv7 series or variants (Dl/Dd) for general purpose workloads

Ev5, Ev6, and Ev7 or variants (Ed) series for memory intensive workloads

Previous-generation VM size series capacity limitations and migration guidance

https://learn.microsoft.com/en-us/azure/virtual-machines/migration/sizes/previous-gen-series-capacity-limitations

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

Thanks.

-TP

Pranitha Sika 0 Reputation points Microsoft External Staff Moderator

2026-08-10T16:31:11.0766667+00:00
Hello Krunal Patel

Based on the screenshot and CLI output, this appears to be a VM** SKU availability **restriction rather than an issue with the disk or snapshot itself.

The command output shows:

NotAvailableForSubscription

For Standard_B2ms in the East** **US region. This indicates that the VM size is currently unavailable for this subscription in the selected region and availability zones. The Azure portal error showing that the size is not available in Zone 1 is consistent with this behavior.

Since the VM is being created from an existing managed disk, the source snapshot or disk migration process is not the blocking factor. The deployment is failing during VM size validation due to SKU availability restrictions.

You can try the following:

Deploy the VM using a different VM size in East US.

Deploy the same VM size in another Azure region.

Verify whether other B-series SKUs are available in the subscription.

If Standard_B2ms** in East **US is a requirement, open an Azure Support request to verify SKU availability and subscription eligibility for that region.

Regarding credits, having Azure credits available does not guarantee that every VM SKU is available in every region or for every subscription. When Azure returns NotAvailableForSubscription, the deployment may be blocked regardless of available credits.

For Additional Reference:

Azure Resource Manager: SKU not available errors. https://learn.microsoft.com/en-us/azure/azure-resource-manager/troubleshooting/error-sku-not-available?tabs=azure-cli

Resolve location ineligible errors. [Resolve lo...soft Learn | Learn.Microsoft.com] Can you please update us if the action plan provided was helpful? Should there be any follow-up questions or concerns, please let us know and we shall try to address them. If these answer your question, click "Upvote" which may be beneficial to other community members reading this thread.
Krunal Patel 0 Reputation points

2026-08-11T13:38:54.44+00:00

Hello Team,

No we do not want to use higher series as we are running with limited budget. Do we have any other option of VM which cost below $70/Month ?
TP 162.1K Reputation points Volunteer Moderator

2026-08-11T14:28:41.97+00:00
@Krunal Patel You may try B v2 Series. For example, Standard_B2as_v2 or Standard_B2s_v2. These are not part of the new restrictions detailed above.

You need to have available quota for it. The required quota families are:

Standard Basv2 Family vCPUs

Standard Bsv2 Family vCPUs

In the portal you need to navigate to Quotas, click on Region filter at top, unselect All and select East US, Apply. There will be a delay while list populates. Once list has populated, enter standard b in search box in upper left to filter list. Next click pencil icon to the right of the VM Size family you want to request quota for.

NOTE: Your request for quota for Standard Basv2 Family vCPUs or Standard Bsv2 Family vCPUs may not be approved, due to capacity issues. In that case you may try other regions.
TP 162.1K Reputation points Volunteer Moderator

2026-08-12T15:59:06.8466667+00:00

@Krunal Patel Any luck with Standard_B2as_v2 or Standard_B2s_v2?