NOt able to increase quota - raised support ticket- no help since 3 days -

Varma 1,620 Reputation points
2026-10-13T08:57:11.9966667+00:00

ERROR

NOtAbleINcrease.png

Please do the needful at the earliest

2610100030000942

I am disappointed with AI support and MS support

Azure Kubernetes Service
Azure Kubernetes Service

An Azure service that provides serverless Kubernetes, an integrated continuous integration and continuous delivery experience, and enterprise-grade security and governance.

2 answers

Sort by: Oldest
Most helpful Newest Oldest

  1. AI answer

    2026-10-13T08:57:25.44+00:00

    For an AKS quota block, the fastest self-service path is to request the quota increase directly in the Azure portal for the affected region and SKU, then retry the cluster operation after approval.

    1. In the Azure portal, search for Quotas.
    2. Select Microsoft.Compute.
    3. Filter by the Location that matches the AKS deployment region.
    4. Find the quota record that is out of quota.
    5. Select the pencil icon at the end of that row.
    6. In Request quota increase, enter the New limit and select Submit.
    7. After the request is approved, retry the AKS cluster creation or update.

    If the quota item is not adjustable, use the support-request path:

    1. In the Azure portal, search for Quotas.
    2. Open the quota record and use the support request option.
    3. In the support form, provide the affected subscription, region, and the new limit requested.
    4. Submit the request under Service and subscription limits (quotas).

    Important details:

    • Quotas are regional, so the increase must be requested for the exact region where the AKS resources are being deployed.
    • These requests are often approved automatically and become available shortly after approval.
    • If capacity is urgently needed, an alternative is to reprovision the cluster in another region or use another SKU with available capacity.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

  2. Senthil kumar 2,585 Reputation points
    2026-10-13T09:12:45.5066667+00:00

    Hi @Varma

    Root Cause :

    1. Regional capacity constraints
      • The East US region may currently have limited capacity for the DDSv4 VM family.
    2. Subscription restrictions
      • New or low-usage Pay-As-You-Go subscriptions may have quota limitations.
    3. VM family availability
      • The DDSv4 series may not be available for new allocations in that region for your subscription.
    4. Account verification/spending limits
      • Azure may require additional subscription verification before approving quota increases.

    Solution :

    Option 1: Try another region

    Check if the VM is available in:

    • East US 2
    • Central US
    • South Central US
    • West US 2
    • West US 3

    Option 2: Try a different VM family

    Instead of DDSv4, test:

    • Dsv5
    • Ddsv5
    • Dasv5
    • B-series (for testing)

    Option 3: Create a Support Request

    Click "Create a support request" from the quota page and select:

    • Service and subscription limits (quotas)
    • VM quota increase

    Include:

    • Subscription ID
    • Region: East US
    • VM family: DDSv4
    • Requested quota: 2 vCPUs

    Thanks.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.