This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(249.60000000000002, 27%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPR%3C/text%3E%3C/svg%3E)
Are there any D4 servers (v4, v5, v6) available at all in East US? I have tried multiple server types (SKUs) and multiple (single) Zone locations without success - adding a new Node Pool. Is there an issue provisioning AKS Nodes in East US? Or is the availability just very limited here? Do I need to move and recreate my resources in another Region?
It would be nice to be able to run a script such as the following to show if there is actual capacity available rather than whether an SKU can exist in that region:
az vm list-available-skus --location eastus --size Standard_D4 --all --output table
Wow this is really getting frustrating.
Azure really needs a tool to show the which regions have capacity - even if it was "Great > 100, Good < 50, Low < 10" or ballpark figures.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(54.400000000000006, 73%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAN%3C/text%3E%3C/svg%3E)
Hi Pete Raleigh,
We completely understand the difficulty you're facing. Right now, Azure doesn't provide real-time visibility into actual VM capacity per region, which makes planning for AKS and VM deployments especially in high-demand regions.
When you are trying to deploy in West US 2 region, did you get any error messages, could you please share any error messages or screenshots of the issue.
Hi Pete Raleigh,
Could you let us know, if the issue has been resolved. If the information provided by me has been helpful to you, please Upvote it and Accept Answer on it.
Hi Pete Raleigh,
It looks like you're having trouble provisioning D4-series VMs (v4, v5, v6) in the East US region for your AKS Node Pool. Availability can fluctuate based on demand, this issue is likely due to regional capacity constraints.
The East US region in Azure is one of its most heavily used locations, which can sometimes restrict the availability of specific VM sizes, particularly in-demand options like the D4 series. Although these SKUs are officially supported in East US, high demand may cause intermittent shortages. While D4-series VMs are listed as available in the region, capacity constraints frequently occur. This is primarily a supply-and-demand issue rather than a lack of SKU support.
If you’ve selected a specific availability zone, testing others in East US may help, as capacity fluctuates across zones. If immediate provisioning is critical, a nearby region with better availability, such as East US 2 or Central US could be a viable alternative, provided it meets your compliance and data residency needs.
SKU availability is not same as capacity. The command you provided confirms if the VM type is supported in that region but doesn't mean Azure can provision one right now. Currently, there’s no direct CLI or API that returns live capacity information.
For your information: Resolve errors for SKU not available
If you have any further queries, let me know. If the information is helpful, please click on Upvote and Accept Answer on it.