An Azure service that provides serverless Kubernetes, an integrated continuous integration and continuous delivery experience, and enterprise-grade security and governance.
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:
- 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_v2may work if it satisfies the system pool requirements.
- Check AKS-supported VM SKUs for the region before creating the cluster:
az aks list-vm-skus \
--location southindia \
--output jsonc
- Check general VM SKU availability in the region:
az vm list-skus --location southindia --output table
- 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.
- Virtual machine (VM) sizes, generations, and features for Azure Kubernetes Service (AKS)
- Quotas, virtual machine size restrictions, and region availability in Azure Kubernetes Service (AKS)
- List available virtual machine (VM) SKUs for Azure Kubernetes Service (AKS) clusters (Preview)
- Resolve errors for SKU not available