Missing quota for B2pts v2 and B1s

Question

Hello,

I am currently using a Student Subscription and have encountered the following issues while trying to create a virtual machine:

1. Standard_B2pts_v2

Even though I selected ARM architecture, the Standard_B2pts_v2 size does not appear in the list.

I also checked using "See all sizes," but the size is not available there either.

Standard_B1s

When attempting to create a VM, I receive the following error: → "This size is currently unavailable in koreacentral for this subscription: NotAvailableForSubscription"

To verify whether this is region-specific, I tried multiple other regions, but the same issue occurs in all of them.

Additional Information

These VM sizes were previously available under the same subscription, but they have suddenly become unavailable.

Could you please confirm whether this is due to subscription limitations, policy changes, or a temporary issue?

Thank you.Hello,

I am currently using a Student Subscription and have encountered the following issues while trying to create a virtual machine:

Standard_B2pts_v2

• Even though I selected ARM architecture, the Standard_B2pts_v2 size does not appear in the list.
• I also checked using "See all sizes," but the size is not available there either.

Standard_B1s

• When attempting to create a VM, I receive the following error:
  → "This size is currently unavailable in koreacentral for this subscription: NotAvailableForSubscription"
• To verify whether this is region-specific, I tried multiple other regions, but the same issue occurs in all of them.

Additional Information

These VM sizes were previously available under the same subscription, but they have suddenly become unavailable.

Could you please confirm whether this is due to subscription limitations, policy changes, or a temporary issue?

Thank you.

Answer 1

Hello

You’re absolutely right that B-series sizes like B1s and B2pts are mentioned in the documentation for Student subscriptions. However, in Azure, there’s an important difference between what is supported in general and what is currently available for a specific subscription.

Based on the behavior you’re seeing, here’s what’s most likely happening:

• For Standard_B2pts_v2, since it does not appear at all (even under “See all sizes”), this usually means the SKU is not currently enabled for your subscription. This is typically due to backend restrictions tied to the subscription offer type, rather than anything on the portal side.
• For Standard_B1s, the fact that it shows up but fails with “NotAvailableForSubscription” across multiple regions suggests that the size is recognized, but new deployments are currently blocked for your subscription. Because this is happening in all regions, it points more to a subscription-level restriction rather than a regional capacity issue.

Regarding your concern about these sizes being available previously, this can occur due to changes over time in Azure’s platform behavior. VM SKUs may be gradually restricted, rebalanced, or deprioritized for certain subscription types (such as Student subscriptions) based on capacity demand, lifecycle updates, or internal policy adjustments. In such cases, existing resources may continue to run, but new deployments of the same SKU may no longer be permitted.

However, Azure does reserve the right to adjust availability based on capacity and subscription type, which can result in scenarios like the one you are experiencing.

Recommended next steps:

Consider selecting an alternative VM size that is currently available for your subscription.

• Optionally, you can verify available SKUs using Azure CLI:

    az vm list-skus --location <region> --output table
  

I hope this provides clarity on the behavior you are seeing. Please let me know if you have any queries in comments.

Answer 2

...........

Answer 3

Both symptoms are consistent with SKU availability and quota behavior, not with a portal bug on the VM creation blade.

For both Standard_B2pts_v2 and Standard_B1s, there are three main causes covered in the documentation:

1. SKU not available in the region or for the subscription
   When a VM is deployed for a size that isn’t available, Azure returns errors such as SkuNotAvailable or NotAvailableForSubscription. The guidance is to either:
   • Choose another VM size, or
   • Deploy in a different region where that size is available.
   This applies even if the size previously worked. Capacity or policy can change over time, and some SKUs can be restricted or retired in specific datacenters or for specific offer types.
2. Subscription/offer‑type and quota restrictions
   Azure subscriptions have per‑region core quotas and SKU restrictions. If a SKU is restricted for a subscription or region, it won’t appear in the size list or will fail validation with a not available error. For student or other special offers, some SKUs can be blocked or limited. The documentation notes that:
   • Some products and VM sizes are simply not available for purchase or deployment in all regions or for all subscriptions.
   • Azure can place capacity restrictions on specific VM sizes in certain regions when demand is high or when a size is being retired.
3. Region‑specific capacity or retirement decisions
   Azure may stop offering a VM size in a given region or for certain subscriptions due to capacity or retirement plans. Even if the size is still documented for the series, it might be:
   • Temporarily unavailable because capacity is exhausted in that region, or
   • Intentionally blocked for new deployments while existing VMs continue to run.

Given the behavior:

• Standard_B2pts_v2 not showing at all in the size picker strongly indicates that this SKU is not currently offered to that subscription in the selected regions.
• Standard_B1s showing but failing with NotAvailableForSubscription indicates the SKU is visible but blocked for new allocations for that subscription/region combination.

From the available guidance, the supported actions are:

1. Try a different VM size in the same family or another general‑purpose size that is available in the region. For B‑series, the Bv1 sizes list (for example Standard_B1s, Standard_B1ms, Standard_B2s, Standard_B2ms, etc.) shows alternatives, but availability still depends on region and subscription.
2. Try another region where the desired size is available and not restricted for the subscription.
3. Check SKU availability programmatically using az vm list-skus --location <region> --output table to see which sizes are available to the subscription in each region.
4. If a specific size is required and not available in any region for the subscription, the only documented path is to open a support request and ask whether an exception or quota adjustment is possible. The documentation also notes that exceptions are not always granted.

The documentation does not state that this behavior is a transient platform issue; it attributes such errors to SKU availability, capacity, or quota/subscription restrictions. So the most likely explanation is a combination of subscription offer limits and regional capacity/policy changes, not a temporary bug.

---

References:

• Resolve errors for SKU not available
• Virtual machine (VM) sizes, generations, and features for Azure Kubernetes Service (AKS)
• Bv1 sizes series
• Common issues: Unavailable virtual machine SKU
• Troubleshoot reservation type not available