Unable to create vm for my region and other regions

Obiajuru Okafor 0 Reputation points
2026-09-22T15:31:06.93+00:00

I have upgraded to pay-as-you-go, confirmed Active status, confirmed provider registration, confirmed quota exists (0 of 10 for B-series in UK South), and still get NotAvailableForSubscription on every size/region/availability zone tried. which includes east us, west us and central us

Azure Virtual Machines
Azure Virtual Machines

An Azure service that is used to provision Windows and Linux virtual machines.

0 comments No comments

2 answers

Sort by: Oldest
  1. AI answer

    2026-09-22T15:31:24.4633333+00:00

    NotAvailableForSubscription means the VM SKU is blocked for the subscription in that region or zone, even when quota exists. Quota and SKU availability are separate checks, so seeing 0 of 10 for B-series in UK South does not guarantee deployment will succeed.

    Since this is happening on every size, region, and availability zone tried, the issue is likely a subscription-level or regional eligibility restriction rather than provider registration or quota.

    Recommended path:

    1. Verify which VM SKUs are actually available to the subscription.
      • In PowerShell, use Get-AzComputeResourceSku and filter by location.
      • SKUs blocked for the subscription appear as NotAvailableForSubscription.
      Example:
         Get-AzComputeResourceSku | Where-Object { $_.Locations -contains "centralus" }
      
      For zonal VM sizes:
         Get-AzComputeResourceSku | Where-Object { $_.Locations -contains "centralus" -and $_.LocationInfo.Zones -ne $null -and $_.ResourceType -eq "virtualmachines" }
      
    2. Check available sizes in the Azure portal.
      • Go to VM creation in the portal.
      • Open the Size drop-down.
      • Select See all sizes.
      • Only sizes shown there are currently available for that subscription and region.
    3. If all sizes remain unavailable across multiple regions, submit a support request for region/SKU access using the quota or subscription-limits path.
      • Community guidance in similar cases shows this is the correct escalation path when the subscription is restricted from VM creation in certain regions or for certain SKUs.
    4. As a temporary workaround, try a different VM size, region, or zone only if Get-AzComputeResourceSku or the portal confirms availability.
      • If Azure returns NotAvailableForSubscription for the SKU, that size cannot be deployed in that region for the current subscription.

    If the failure changes from NotAvailableForSubscription to AllocationFailed or ZonalAllocationFailed, that indicates a capacity issue instead. In that case, retry later, resize the VM, or change the region or zone.


    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

  2. Andreas Baumgarten 132.9K Reputation points MVP Volunteer Moderator
    2026-09-22T16:15:52.5+00:00

    Hi @Obiajuru Okafor ,

    please check if the B v2 VM series VM SKUs are available for you.

    User's image


    User's image

    As the B series (version 1/v1) is being retired in a lot of Azure regions the B2 v2 series might be the preferred VM SKU.

    More details: https://learn.microsoft.com/en-us/azure/virtual-machines/sizes/general-purpose/bsv2-series?tabs=sizebasic#sizes-in-series


    (If the reply was helpful please don't forget to upvote and/or accept as answer, thank you)

    Regards

    Andreas Baumgarten

    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.