Share via

FAILED Preflight validation check for resource(s) for container service

Christian Salway 0 Reputation points
2026-02-18T14:44:33.4066667+00:00

New to Azure and just tried to create a Kubernetes cluster using default settings and cant. Ive requested quota increase but get told I cant as limited in uksouth location. So whats the point of having a service a user cant even launch!

{
  "error": {
    "code": "InvalidTemplateDeployment",
    "details": [
      {
        "code": "BadRequest",
        "message": "Preflight validation check for resource(s) for container service my-cluster in resource group my-rg failed. Message: AKS Automatic could not find a suitable VM size. The subscription may not have the required quota of '16' vCPUs, may have restrictions, or location 'uksouth' may not support three availability zones for the following VM sizes: 'standard_d4lds_v5,standard_d4ads_v5,standard_d4ds_v5,standard_d4d_v5,standard_d4d_v4,standard_ds3_v2,standard_ds12_v2,standard_d4alds_v6,standard_d4lds_v6,standard_d4alds_v5'. Please request some quota for one of these candidate vm sizes in the target region or explicitly specify a vm-size with sufficient quota via --node-vm-size. For more information, please visit https://aka.ms/aks-automatic-quota. Details: "
      }
    ],
    "message": "The template deployment 'microsoft.aksautomatic-1771425452368' is not valid according to the validation procedure. The tracking id is '5646191f-cdd4-4aca-a5be-a964340b3366'. See inner errors for details."
  },
  "details": {
    "code": "InvalidTemplateDeployment",
    "message": "The template deployment 'microsoft.aksautomatic-1771425452368' is not valid according to the validation procedure. The tracking id is '5646191f-cdd4-4aca-a5be-a964340b3366'. See inner errors for details.",
    "details": [
      {
        "code": "BadRequest",
        "message": "Preflight validation check for resource(s) for container service my-cluster in resource group my-rg failed. Message: AKS Automatic could not find a suitable VM size. The subscription may not have the required quota of '16' vCPUs, may have restrictions, or location 'uksouth' may not support three availability zones for the following VM sizes: 'standard_d4lds_v5,standard_d4ads_v5,standard_d4ds_v5,standard_d4d_v5,standard_d4d_v4,standard_ds3_v2,standard_ds12_v2,standard_d4alds_v6,standard_d4lds_v6,standard_d4alds_v5'. Please request some quota for one of these candidate vm sizes in the target region or explicitly specify a vm-size with sufficient quota via --node-vm-size. For more information, please visit https://aka.ms/aks-automatic-quota. Details: "
      }
    ]
  }
}
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.

0 comments No comments
{count} votes

3 answers

Sort by: Most helpful
  1. Christian Salway 0 Reputation points
    2026-02-18T18:02:33.3633333+00:00

    So both of your feedback is "request quota" which i mentioned that i already did and was denied, change location without thought as to being bound to uksouth for legal/compliance reasons, or use smaller vm images which wouldn't support the application I need to run on kubernetes...

    Anything else thats not textbook, or already in the error message, for a solution? how about reconfiguring your AKS automatic deployment to give vm images that are available.

    0 comments No comments

  2. Jilakara Hemalatha 10,200 Reputation points Microsoft External Staff Moderator
    2026-02-18T17:24:57.3466667+00:00

    Thank you for reaching out Q/A. I completely understand your frustration.

    The issue here is regional limitations in UK South. Some VM sizes that AKS Automatic needs are either out of quota or not supported across all availability zones in that region, which is why your cluster couldn’t launch. This isn’t a limitation of AKS itself, but of the combination of VM size, quota, and regional availability.

    To move forward, you can consider the following options:

    1. Try a different region where you may have available quota.
    2. Use smaller node sizes for your AKS cluster that require fewer vCPUs.
    3. Check existing resources in UK South that might be consuming your vCPU quota and remove any unnecessary ones.

    Reference: https://learn.microsoft.com/en-us/troubleshoot/azure/azure-kubernetes/create-upgrade-delete/aks-automatic-troubleshoot?

    0 comments No comments

  3. SUNOJ KUMAR YELURU 17,981 Reputation points MVP Volunteer Moderator
    2026-02-18T16:31:45.8733333+00:00

    Hello @Christian Salway,

    To resolve this, you can either request a quota increase through the Azure portal or consider reprovisioning your cluster in a different region or SKU that has available capacity. Keep in mind that quota requests may not always be approved, especially in regions with limited capacity.

    Quotas, virtual machine size restrictions, and region availability in Azure Kubernetes Service (AKS)


    If this answers your query, do click Accept Answer and Up-Vote for the same. And, if you have any further query do let us know.

    0 comments No comments

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.