This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(32, 65%, 13%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECS%3C/text%3E%3C/svg%3E)
Hi team,
I cannot delete the "kuebernetes" load balancer from my deleted AKS clusters.
I also cannot delete the backpools.
I don't have any support plan so I cant file a ticket. Can I get some support to delete the resource please. I am still being charged.
I have checked https://learn.microsoft.com/en-us/answers/questions/1381363/delete-aks-loadbalancer-not-possible
And none of the solutions work since I no longer have any vmss. (az vmss list is empty)
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(268.8, 61%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EGV%3C/text%3E%3C/svg%3E)
Hi Chi Sang Hui,
This issue occurs when an Azure Kubernetes Service (AKS) cluster is deleted, but the associated Azure Load Balancer ("kubernetes") and backend pools remain in the resource group. This is often due to orphaned network interfaces (NICs) or lingering dependencies.
Steps to resolve:
Check and delete orphaned NICs
The load balancer might still be associated with orphaned NICs from the deleted Virtual Machine Scale Set (VMSS). Run the following command to list NICs in the resource group:
az network nic list --resource-group <RESOURCE_GROUP_NAME> --query "[].id" -o tsv
If any NICs exist, delete them:
az network nic delete --ids <NIC_ID>
Remove backend pools manually
If the backend pools are still associated with deleted VMSS instances, remove them manually:
az network lb address-pool list --resource-group <RESOURCE_GROUP_NAME> --lb-name kubernetes
If any backend pools exist, delete them:
az network lb address-pool delete --resource-group <RESOURCE_GROUP_NAME> --lb-name kubernetes --name <POOL_NAME>
Delete the load balancer Once dependencies are removed, delete the load balancer:
az network lb delete --resource-group <RESOURCE_GROUP_NAME> --name kubernetes
Check for other dependencies
Verify if any public IPs, managed identities, or NSGs related to the AKS cluster remain in the resource group and delete them.
If it was helpful, please click "Upvote" on this post to let us know.
Thank You.
Hi Chi Sang Hui,
Just checking in to see if you have got a chance to see my response to your question in resolving the issue.
If it was helpful, please click "Upvote" on this post to let us know.
Thank You.