Need to create azure aks

Amit Hole 20 Reputation points
2026-10-05T09:51:40.6766667+00:00

Hi,

Getting error

az aks create --resource-group ecommerce-resource-group --name ecommerce-aks-cluster --node-count 1 --node-vm-size Standard_B2s --enable-addons monitoring --generate-ssh-keys

(BadRequest) The VM size of Standard_B2s is not allowed in your subscription in location 'southindia'. The available VM sizes are 'standard_b16als_v2,standard_b16as_v2,standard_b16ls_v2,standard_b16s_v2,standard_b2als_v2,standard_b2as_v2,standard_b

Will you please help

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.


Answer accepted by question author

AI answer

2026-10-05T09:51:56.0766667+00:00

Standard_B2s is blocked for AKS in this scenario. For AKS, system node pools might not be able to use VM sizes with fewer than 2 vCPUs and 4 GB memory, and AKS doesn't support B-series VMs for system node pools. Since az aks create creates the initial system node pool, Standard_B2s isn't a valid choice here.

Use one of these approaches:

  1. Pick a supported VM size from the list returned for southindia.
    • Your error already shows allowed sizes in the subscription and region.
    • A B-series option from that allowed list such as standard_b2as_v2 may work if it satisfies the system pool requirements.
  2. Check AKS-supported VM SKUs for the region before creating the cluster:
az aks list-vm-skus \
  --location southindia \
  --output jsonc
  1. Check general VM SKU availability in the region:
az vm list-skus --location southindia --output table
  1. Create the cluster with a supported size instead of Standard_B2s.

If cluster creation still fails after selecting a listed SKU, common causes are:

  • subscription quota limits
  • regional or zonal capacity restrictions
  • AKS restrictions on certain VM sizes

If no suitable SKU appears, review quota and regional availability. If creation fails with allocation or capacity errors, rerun az aks list-vm-skus and choose another SKU family or region.


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

Was this answer helpful?

2 people found this answer helpful.

1 additional answer

Sort by: Newest
  1. Krishnan Ramanathan 0 Reputation points Microsoft Employee
    2026-10-06T02:23:05.4433333+00:00

    The second issue you posted it because of an issue with the specific aks-preview version that you have installed.

    You can run the below command to verify the version of the aks-preview extension that is installed with AZ CLI:

    az extension list --output table
    

    If you don't need this extension, you can remove it and then retry the command.

    az extension remove --name aks-preview
    

    If you do need the aks-preview extension, I would recommend that you install a more stable build of this preview extension (for e.g. 20.0.0b7) and then retry the commands.

    az extension list-available --output table | grep aks-preview
    az extension add --name aks-preview --version 20.0.0b7
    

    Was this answer helpful?

    1 person found this answer helpful.
    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.