Cant create a VM

Question

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

Answer 1

Hi Trevor Basta,

Thank you for sharing the details.

Based on the error message “This** size is currently unavailable in eastus2 for this subscription: ****NotAvailableForSubscription”**, this does not appear to be an issue with the VM image, operating system, or Microsoft.Compute provider registration.

This error means that the selected VM size is currently not available for your subscription in the selected region or availability zone. This can happen even when the subscription is active and quota appears available, because Azure validates quota, SKU** availability, and regional/zonal **capacity separately.

To confirm which VM sizes are available for your subscription, please run the following Azure CLI command:

Shell az vm list-skus --location eastus2 --resource-type virtualMachines --all --output table

Please review the Restrictions column in the output. If a VM size shows NotAvailableForSubscription, that specific size is currently restricted for your subscription in that region or zone.

As a next step, please try deploying a newer-generation VM size, such as a v5, v6, or v7 series VM, in a region where it is available. Azure has introduced capacity limitations for several previous-generation VM series, so new deployments using older VM families may be restricted.

If the newer-generation VM sizes are also unavailable, please submit a VM-family vCPU quota/SKU availability request from the Azure portal:

1. Go to Azure** **portal
2. Search for Quotas
3. Select Compute
4. Choose the required subscription and region
5. Select a newer-generation VM family, such as Dv5, Dv6, Dv7, Ev5, Ev6, or Ev7, based on your workload requirement
6. Select New** Quota **Request and submit the request

Please note that available quota does not guarantee successful VM deployment if the SKU is restricted or if regional capacity is unavailable. If one VM family is restricted, selecting a newer-generation VM family or another region is the recommended path.

Microsoft documentation for reference:

• Resolve errors for SKU not available
• vCPU quotas for Azure Virtual Machines
• Increase VM-family vCPU quotas
• Previous-generation VM size series capacity limitations and migration guidance

Please try the above steps and share the CLI output if the issue persists, so we can review the exact SKU restriction and guide you on the next available VM family or region.

Thanks,

Manasa.

Answer 2

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.

1. Portal > Help + Support > Create a support request
2. Issue Type: Service and subscription limits (quotas)
3. Subscription: your Pay-As-You-Go
4. Quota Type: Compute - VM (cores-vCPUs) subscription limit increases
5. Click Next, then Enter details > Location: East US (or any) > Standard DSv3 Family vCPUs = 10, Standard D Family = 10, Standard BS Family = 10
6. 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 3

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 4

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:

1. 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.
2. 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" }
   

3. 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.
4. 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
5. 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.
6. 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.
7. 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:

• Resolve errors for SKU not available
• Common issues: Unavailable virtual machine SKU
• Can't create a Capacity Reservation
• Unable to create any Azure Virtual Machine in any region with a new Azure subscription - Microsoft Q&A