Azure-docs: Regional Cores quota limitation - Failed to create the aks private in Free Trail subscription

[michaelsync]

It would be worth to mention that it's required a minimum of 6 Cores to create the AKS private cluster. The Free trial subscription comes with only 4 Cores and not eligible to increase the cores as well.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 0b68f2c4-bb6c-11a2-6c61-8af4057a2438
• Version Independent ID: e3498bed-1447-6841-8353-9f1b5d3dc8df
• Content: Create a private Azure Kubernetes Service cluster
• Content Source: articles/aks/private-clusters.md
• Service: container-service
• GitHub Login: @mlearned
• Microsoft Alias: mlearned

[michaelsync]

Error message:

Operation failed with status: 'Bad Request'. Details: Provisioning of resource(s) for container service my-cluster-name in resource group my-cluster-name-resource-group failed. Message: Operation could not be completed as it results in exceeding approved Total Regional Cores quota. Additional details - Deployment Model: Resource Manager, Location: australiaeast, Current Limit: 4, Current Usage: 0, Additional Required: 6, (Minimum) New Limit Required: 6. Submit a request for Quota increase at https://aka.ms/ProdportalCRP/?#create/Microsoft.Support/Parameters/{#subscription-id-and-link##} by specifying parameters listed in the ‘Details’ section for deployment to succeed. Please read more about quota limits at https://docs.microsoft.com/en-us/azure/azure-supportability/regional-quota-requests.. Details:

[Karishma-Tiwari-MSFT]

Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as appropriate.

[ezlee]

You can still build a cluster with even 1 node or 2 nodes under free trial, no more than 4 cores.

[michaelsync]

@ezlee Does it have that option? I know I can do with AKS (public) but couldn't find the option for AKS private (preview).

Seems like I couldn't tag @ontoneio

[TomGeske]

You can use --node-count 1 parameter.

I'm going ahead closing this one. Feel free to keep commenting in case of further questions.

please-close