Unable to deploy any Windows Server 2019 or 2022 Datacenter VMs in East US. All tested sizes (Standard_D4s_v3, D2s_v3, E2s_v3, D8s_v3) fail with NotAvailableForSubscription – Capacity Restrictions. Requesting capacity review or guidance on supported al

Question

Unable to deploy any Windows Server 2019 or 2022 Datacenter VMs in East US. 
All tested sizes (Standard_D4s_v3, D2s_v3, E2s_v3, D8s_v3) fail with 
NotAvailableForSubscription – Capacity Restrictions. 
Requesting capacity review or guidance on supported alternatives/regions.

Answer 1

Hi @Jannisar shah ,

since the beginning of July 2026, Azure VM SKU series v1 through v4 have been subject to certain capacity or availability restrictions.

Please take a look here: Previous-generation VM size series capacity limitations and migration guidance

Instead of using v1 - v4 Azure VM SKU series it is recommended to select v5, v6, and v7 VM series: Migration recommendations

---

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

Regards

Andreas Baumgarten

Answer 2

Hello Jannisar shah

NotAvailableForSubscription means that the selected VM SKUs are currently restricted for your specific subscription in East US. This is different from a normal vCPU quota error and is unlikely to be related to the Windows Server 2019 or 2022 image.

First, confirm the restrictions from Azure Cloud Shell:

az account set --subscription "<subscription-id>"

az vm list-skus \
  --location eastus \
  --resource-type virtualMachines \
  --size Standard_D \
  --all \
  --output table

az vm list-skus \
  --location eastus \
  --resource-type virtualMachines \
  --size Standard_E \
  --all \
  --output table

The --all option includes SKUs that are unavailable to the current subscription. Check the Restrictions column. If it shows NotAvailableForSubscription, the SKU cannot currently be deployed by that subscription in the listed region or zones.

Also verify that this is not a separate quota issue:

az vm list-usage --location eastus --output table

Check both:

• Total Regional vCPUs

Standard DSv3 Family vCPUs

Standard ESv3 Family vCPUs

Azure checks quota and physical capacity separately, so sufficient quota does not remove a SKU restriction.

As an immediate workaround:

Run the SKU command without --all to display sizes currently available to the subscription:

az vm list-skus \
  --location eastus \
  --resource-type virtualMachines \
  --output table

Consider a currently unrestricted newer family with similar CPU and memory, such as Dsv5, Dasv5, Esv5 or Easv5.

Test another availability zone, remove explicit zone pinning so Azure can select capacity, or test another suitable region such as East US 2. Availability is dynamic and subscription-specific, so verify each candidate with az vm list-skus.

If East US is mandatory, open an Azure Support request:

Azure portal → Help + support → Create a support request → Service and subscription limits (quotas) → Compute-VM subscription limits