Cant create a VM

Question

Cant create a VM

Trevor Basta 0

Hi, I'm trying to create a virtual machine in Azure using my active Pay-As-You-Go subscription, but every VM size is unavailable. I keep getting the error 'NotAvailableForSubscription' in every region. I've already checked my quotas, registered Microsoft.Compute, and tried multiple regions.

it seems that creating a ticket is useless its not helping me at all especially because idk the real reason of the issue if its the vm or the subsciption or what.

"This size is currently unavailable in eastus2 for this subscription: NotAvailableForSubscription. - full error message

0 comments

3 answers

Your answer

Answer 1

Hello @Trevor Basta,

When you see NotAvailableForSubscription in every region for every size, it's not a capacity issue and it's not quotas in the normal sense. It means Microsoft's risk system has not enabled VM families for your Pay-As-You-Go subscription yet. It happens a lot with:

Subscriptions < 14 days old
First Pay-As-You-Go on a new Microsoft Account
Credit card still in verification / $1 hold failed
Previous Free Trial / Student upgraded to Pay-As-You-Go

You can register Microsoft.Compute and have 100% quota free and it will still block you.

The actual fix - Request quota for the FAMILY

Even if it shows 0% used, you need to request it to trigger enablement.

Portal > Help + Support > Create a support request
Issue Type: Service and subscription limits (quotas)
Subscription: your Pay-As-You-Go
Quota Type: Compute - VM (cores-vCPUs) subscription limit increases
Click Next, then Enter details > Location: East US (or any) > Standard DSv3 Family vCPUs = 10, Standard D Family = 10, Standard BS Family = 10
Submit

Try creating from CLI to bypass portal validation:

az vm create -g myRG -n testVM --image Ubuntu2204 --size Standard_B1s --location centralus

If this answers your query, do click Accept Answer and Up-Vote for the same. And, if you have any further query do let us know.

Answer 2

Hi Trevor,

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.

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

Answer 3

NotAvailableForSubscription means the VM SKU is not available for that subscription in the selected region. In Azure, this is typically a subscription-level or regional restriction, not a Microsoft.Compute registration issue.

Based on the scenario described:

Stop retrying the same VM size in the same region. If the error is NotAvailableForSubscription, that size is blocked for that subscription in that region.
Check which VM SKUs are actually available to the subscription. In Azure PowerShell, use:
```
   Get-AzComputeResourceSku | Where-Object { $_.Locations -contains "eastus2" }
```
SKUs that are unavailable for the current subscription are listed as NotAvailableForSubscription. To check VM sizes that support availability zones in a region:
```
   Get-AzComputeResourceSku | Where-Object { $_.Locations -contains "eastus2" -and $_.LocationInfo.Zones -ne $null -and $_.ResourceType -eq "virtualmachines" }
```
In the Azure portal, verify available sizes before deploying. Go to VM creation, open the Size drop-down, and select See all sizes. The portal shows the sizes available for the selected region without needing to complete deployment.
Try a different region or a different VM size. The documented resolutions for unavailable SKUs are:
- choose a region where the desired VM size is available
- select a VM size that is available in the desired region
If every VM size fails across multiple regions, the issue is not the individual VM definition alone. That points to subscription eligibility or subscription-level SKU restrictions rather than a single VM configuration problem.
Capacity can also be a factor. Azure can fail allocation when a region or zone lacks capacity for the requested VM size, location, and quantity. In that case, retry later or change the VM size, location, or quantity.
Capacity Reservation is not available for all subscription types. Reservations are only available to paid Azure customers. Sponsored accounts such as Free Trial and Azure for Students are not eligible. Since the subscription is Pay-As-You-Go, that specific restriction should not apply, but standard SKU availability and regional capacity restrictions still can.

The practical conclusion is:

If only some sizes fail, it is a VM SKU availability issue.
If all sizes fail in all tested regions after quota checks and provider registration, it is most consistent with a subscription-level regional/SKU eligibility restriction.

References: