NotAvailableForSubscription on all VM sizes, all regions - new Azure Plan subscription

Question

Hello everyone,

I'm hoping someone here has run into this before. I created a brand-new Azure Plan subscription (MCA billing, tied to an existing Microsoft 365 Business Premium tenant) to build an Azure Virtual Desktop (AVD) lab.

Every VM size I try to deploy (including the smallest possible) Standard_B1s fails with:

Quota is not the issue, "Get-AzQuota" confirms Standard BS Family has a Limit of 10 in North Europe, IsQuotaApplicable: True (same result from "Get-AzVMUsage").

I've tried multiple SKUs across generations: Standard_B2ms, Standard_D2s_v5, Standard_D2s_v3, Standard_DS1_v2, Standard_B1s but all are identically blocked.

Tried multiple regions:

1. West Europe rejected outright at VNet creation with "region not accepting new customers" (separate, already-understood issue, confirmed via a Microsoft-managed system policy, sys.blockwesteurope, found via Get-AzPolicyAssignment)
2. North Europe accepts VNet/host pool creation fine but blocks every VM size.

Resource providers are registered: Microsoft.Compute, Microsoft.Network, Microsoft.Storage, Microsoft.DesktopVirtualization all show Registered.

Payment method is on file at the billing profile level (MCA), so it's not a missing-payment-method issue.

No relevant Azure Policy restricting VM SKUs beyond the West Europe one noted above.

Tested a second brand-new subscription in the same billing account/tenant, identical NotAvailableForSubscription result, so this appears to be tied to the tenant/account level, not the individual subscription.

The built-in Deployment Guided Troubleshooter also fails, returning "Unable to retrieve the list of VM sizes."

Filed a Basic support ticket under Subscription Management and got an automated response saying this requires a paid technical support plan.

Has anyone seen this resolve on its own after a waiting period or found a free path to get Microsoft to lift a subscription-level SKU restriction like this? Any pointers appreciated.

Thank you.

Radu

Answer 1

Hi @Radu Bogdan

Thak you for reaching out to Microsoft Q&A.

Based on the documentation, NotAvailableForSubscription is a distinct restriction reason from quota that means the SKU is blocked at the subscription/tenant eligibility or datacenter-capacity level, not that you're missing an allocation. That's why Get-AzQuota and Get-AzVMUsage can show a healthy limit while every size still fails: Resolve errors for SKU not available confirms this is what Get-AzComputeResourceSku reports for SKUs restricted for the current subscription, and that the official resolution is to "submit a SKU request to Azure Support" when this happens.

Since it's reproducing across every SKU/generation you've tried and even on a second brand-new subscription in the same billing account/tenant, this points to something at the tenant or billing-account level rather than a per-subscription gap.

The free (no paid support plan required) path to escalate this is the quota/subscription-limit request flow, not a general technical ticket:

1. In the Azure Portal, go to Help + support → Create a new support request.
2. Set Issue type to "Service and subscription Limit (quotas)".
3. Set Quota type to "Compute-VM (core-vCPUs) subscription limit increases" (or "Other Requests" for broader region/SKU access).

This process is described in Azure region access request process. It's worth checking whether your earlier "Basic support ticket under Subscription Management" was filed under this specific quota issue type — the auto-response about needing a paid technical support plan suggests it may have been routed as a general technical issue instead, which does require a paid plan, whereas quota/subscription-limit requests typically don't.

I don't have a documented explanation for why a brand-new tenant would be blocked on all VM SKUs tenant-wide — that root cause isn't public, only the escalation path is — so I'd treat the underlying cause as unconfirmed until Support responds to the quota-type request. For reference, other community threads describe similar "not available for subscription" behavior on Azure Plan subscriptions being resolved the same way, e.g. Azure Plan Subscription without access to VM sizes to create AKS Cluster.

---

Please 'Upvote' (thumbs-up) and 'Accept' as answer if this was helpful — it'll help other community members who run into the same issue.

Best regards,

Andrew S Taylor

Answer 2

Hi Radu,

For the Bv1 series VMs (Standard_B1s, Standard_B2ms, etc.) it isn't surprising that you are blocked, since those are scheduled for retirement and they have restricted some subscriptions from creating them.

In regards to the other sizes, some people have been blocked if a particular region/zone is tight on capacity, or they are using a more restrictive subscription type (e.g. Azure for Students, Azure Free). You have plenty of Quota available for these other sizes too, correct?

First I would suggest you re-register Microsoft.Compute, since occasionally there can be an issue with new subscriptions. Please navigate to your subscription, on left click Settings -- Resource providers. Next in filter box at top enter microsoft.compute, select it in the list, click Re-register, confirm. After doing this please wait 20 minutes, even though you will likely see message saying it has completed.

After waiting 20 minutes please try to deploy (in some different regions, say West US 3) a newer size such as the Standard_D2s_v5 you tried before. Of course you need to have available quota in each region, if you don't please navigate to Quotas and request small amount using automated method (pencil icon next to family).

Second if the above doesn't succeed I recommend you create a free Service and subscription limits (quotas) support request. This is the correct request type for requesting quota, region access, etc., which is what you need when there are subscription-level blocks on deploying certain VM sizes or services to certain regions.

You may start the process using link below:

https://portal.azure.com/#create/Microsoft.Support

Issue type: Service and subscription limits (quotas)

You may need to try different Quota types. For example, you can try Compute-VM (cores-vCPUs) subscription limit increases, which is most logical, but don't click on the Manage quota link to use automated method. Instead click Next and then Enter details on Additional details tab.

If you don't get a favorable (human) response through this method, try Issue type: Other Requests and then on Additional details tab explain the exact error (NotAvailableForSubscription) you are seeing, that this is new paid subscription, and you are unable to create even newer-generation VMs.

Thanks.

-TP