vCPU quota denied

Question

vCPU quota denied

Christian Salway 0

We are trying to run a kubernetes application which requires 32G RAM VM's in the southeastasia location. However, our quota request keeps on getting denied. I have tried absolutely every type of vm and all are declined. So how is anyone supposed to run any decent sized application in AKS?!

I have also tried uksouth and uscentral. All have the same quota issue.

Anonymous

2026-03-12T16:52:29.6566667+00:00

Christian Salway This AKS behavior is understandably frustrating, but it’s typically due to Azure capacity constraints, not a misconfiguration.

Even when quota requests are valid, Azure evaluates three factors before approval:

(1) vCPU quota availability,

(2) VM SKU eligibility for the subscription, and (3) actual regional or zonal capacity.

In busy regions (including Southeast Asia, UK South, US Central), popular 32‑GB VM sizes (D8s/E4s v5) are often capacity‑constrained, so requests may be denied despite correct quota requests.

Practical workarounds succeed includes trying AMD-based SKUs (e.g., E4as_v5, D8as_v4), deploying in a different availability zone within the same region, or temporarily using smaller nodes (e.g., 2×16‑GB) while keeping the quota request open.

This is a platform capacity limitation rather than an AKS issue, and capacity approvals may succeed later as availability improves.
Christian Salway 0 Reputation points

2026-03-13T10:59:56.3933333+00:00

I've tried all sizes and keep getting quota denied.

With regards to the sizes you suggested:

Insufficient vcpu quota requested 12, remaining 0 for family standardEASv5Family for region southeastasia.

I could request more, but I will just get denied. You are massively under supplied on resources in all your locations. How is anyone supposed to launch any decent application in Azure in any location?

Your answer

Anonymous

2026-03-12T16:52:29.6566667+00:00

Christian Salway This AKS behavior is understandably frustrating, but it’s typically due to Azure capacity constraints, not a misconfiguration.

Even when quota requests are valid, Azure evaluates three factors before approval:

(1) vCPU quota availability,

(2) VM SKU eligibility for the subscription, and (3) actual regional or zonal capacity.

In busy regions (including Southeast Asia, UK South, US Central), popular 32‑GB VM sizes (D8s/E4s v5) are often capacity‑constrained, so requests may be denied despite correct quota requests.

Practical workarounds succeed includes trying AMD-based SKUs (e.g., E4as_v5, D8as_v4), deploying in a different availability zone within the same region, or temporarily using smaller nodes (e.g., 2×16‑GB) while keeping the quota request open.

This is a platform capacity limitation rather than an AKS issue, and capacity approvals may succeed later as availability improves.
Christian Salway 0 Reputation points

2026-03-13T10:59:56.3933333+00:00

I've tried all sizes and keep getting quota denied.

With regards to the sizes you suggested:

Insufficient vcpu quota requested 12, remaining 0 for family standardEASv5Family for region southeastasia.

I could request more, but I will just get denied. You are massively under supplied on resources in all your locations. How is anyone supposed to launch any decent application in Azure in any location?