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

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