![](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(35.2, 49%, 13%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EUK%3C/text%3E%3C/svg%3E)
Azure Kubernetes Service
An Azure service that provides serverless Kubernetes, an integrated continuous integration and continuous delivery experience, and enterprise-grade security and governance.
AKS creates this other resource group so that it can automatically create
As stated from the AKS FAQ section about this extra resource group:
The second resource group, known as the node resource group, contains all of the infrastructure resources associated with the cluster. These resources include the Kubernetes node VMs, virtual networking, and storage. By default, the node resource group has a name like MC_myResourceGroup_myAKSCluster_eastus. AKS automatically deletes the node resource group whenever the cluster is deleted, so it should only be used for resources that share the cluster's lifecycle.
You can change the Resource Group name if you want, but AKS manages the resource group (and all resources within it). This allows AKS to create VMs, clusters, instances ect... for you. When you delete the AKS cluster, AKS SHOULD delete this resource group for you.
In the error you listed, a NSG was added to the subnet that has a policy that AKS does not have permission to delete. This is why you had to delete that resource group manually. If you do not want to do this in the future, you can remove any policies on NSGs for AKS resource groups. Many orgs put these NSGs & policies on automatically.