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:
- 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" }
- 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.
- 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.
- 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.