Issue during AKS automatic cluster deployment through manully,cli and terraform

Question

Issue during AKS automatic cluster deployment through manully,cli and terraform

Monalisa Barik 60

Getting error while deploying AKS automatic cluster {

"code": "DeploymentFailed",

"target": "/subscriptions/xxxx/resourceGroups/rg-xxx-devops/providers/Microsoft.Resources/deployments/microsoft.aksautomatic-1790588363145",

"message": "At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-deployment-operations for usage details.",

"details": [

{

  "code": "PropertyChangeNotAllowed",

  "target": "/subscriptions/xxx/resourceGroups/rg-ddmo-devops/providers/Microsoft.ContainerService/managedClusters/xxx-aks",

  "message": "Changing property \"agentPoolProfile.availabilityZone\" is not allowed in an api-version before \"2026-01-02-preview\"."

}

]

}

0 comments

1 answer

Your answer

Answer 1

Hi @Monalisa Barik

The important part of the error is:

"PropertyChangeNotAllowed: Changing property "agentPoolProfile.availabilityZone" is not allowed..."

This indicates that Azure is processing the request as an update to an existing AKS-managed cluster or node pool, and the requested configuration changes its availability zone setting. An existing node pool’s availability-zone configuration can’t be changed. Create a new node pool with the required zone configuration instead.

First, confirm whether the failed deployment left an AKS resource behind:

az aks show \
  --resource-group rg-ddmo-devops \
  --name <cluster-name>

The az aks show command returns the current managed-cluster configuration.

Also retrieve the complete nested deployment error:

az deployment operation group list \
  --resource-group rg-ddmo-devops \
  --name microsoft.aksautomatic-1790588363145 \
  --output json

This command lists the operations and underlying errors of a resource-group deployment.

If this was intended to be a new cluster but a partially created cluster already exists, deploy with a new cluster name or remove the failed resource after confirming that it contains no required workloads. If it’s an existing cluster, don’t attempt to modify the current node pool’s zone configuration; create a replacement node pool and migrate the workloads.

Please provide the complete inner error, the deployment method, and versions - Azure CLI version, Terraform AzureRM/AzAPI provider version, and whether the cluster name was previously used.

References:

Configure availability zones in AKS

Azure CLI: az aks

View Azure Resource Manager deployment history

Create an AKS Automatic cluster

Help make this community better for everyone: If this answer helped or resolved your issue, please accept it or upvote it. If not, share more details in a comment so we can continue the discussion and find the right solution. Thank you.