Unable to deploy VM sizes despite approved quota

Dear Kamran,

This is not a quota problem

It is a regional capacity/backend allocation constraint in East US

Microsoft guidance is to change zone, size, or region, or use capacity reservations

For more details and troubleshooting use link:

https://docs.azure.cn/en-us/azure-resource-manager/troubleshooting/error-sku-not-available?tabs=azure-cli

Hello Kamran,

Thank you for reaching out to Q/A and for sharing the details regarding the VM deployment issue in the East US region.

We understand that despite having the required quota approved for Bsv2, Easv5, and Easv6 VM families, you are still encountering “Size not available” and “Request quota” messages during VM creation. We acknowledge the impact and will assist you in isolating the underlying cause.

At this point, in order to determine whether this behavior is related to regional capacity constraints, zonal limitations, or a potential portal-level mismatch, we would need to gather a few additional details from your environment.

Could you please share a screenshot of the quota section visible during the VM creation process, specifically the area where the VM size selection and quota availability are displayed? This will help us validate how the SKU availability is being presented from the portal perspective.

Additionally, we would request you to run the following Azure CLI command from your environment and share the output, which will help us validate SKU availability and any backend restrictions:

az vm list-skus --location eastus --size Standard_Easv5 --output table

To further validate SKU availability across regions and identify any restrictions, you may also use the following command:

az vm list-skus \
 --resource-type virtualMachines \
 --all \
 --query "[?name=='Standard_Bsv2'].{
     Name: name,
     Locations: locations,
     Restrictions: restrictions
 }" \
 --output json

In the output, if you see ReasonCode: "NotAvailableForSubscription" then you won't be able to create VM in region

If you observe ReasonCode: "NotAvailableForSubscription" in the output, it generally indicates that the VM SKU is currently not available for deployment in that region for the subscription, which may be due to subscription-level enablement, regional constraints, or backend capacity restrictions.

Additionally, to further isolate the issue, we recommend checking whether the behavior is specific to a zone by attempting deployments across different availability zones (Zone 1, Zone 2, and Zone 3), as capacity may vary across zones within the same region.

It would also be helpful to confirm whether the same issue is reproducible in alternative regions such as East US 2 or Central US, which will help determine whether this is a region-specific capacity constraint.