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(195.2, 50%, 28%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMD%3C/text%3E%3C/svg%3E)
We have orphaned AKS nodepool resource group that cannot be deleted. Only managed RG remains, the parent RG no longer exists. There are 4 resources - VMSS, VNET, Load Balancer, Public IP address. Individual deletion and force delete fail. Trying to disassociate the resources also fails.
How can I raise support request to delete?
An Azure service that provides serverless Kubernetes, an integrated continuous integration and continuous delivery experience, and enterprise-grade security and governance.
![](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(300.8, 8%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EHS%3C/text%3E%3C/svg%3E)
In this state, the remaining resources such as VMSS, VNet, Load Balancer, and Public IP are still logically tied to the AKS resource provider lifecycle, and may also have stale backend dependencies (for example VMSS references) which are not visible or accessible to you. Because of this:
Reached for additional details via private messages
Michael Damat - The failure is occurring because one of the VM scale set instances is still present and holding its network interface, which is preventing the platform from completing the deletion. We recommend verifying whether any VM instances (especially instance 0) are still in a deleting or failed state and attempting to remove those instances first, then retrying the VMSS deletion.
There are no VM scale set instances available to me, so I cannot delete. Through both Az Powershell and Azure Portal there are no instances returned.
Answer accepted by question author
![](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(249.60000000000002, 21%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMD%3C/text%3E%3C/svg%3E)
Customer confirmed that the RG is deleted by manual intervention from PG by clearing the backend dependencies.
Good to close the thread.
Answer accepted by question author
Michael Damato - PG has verified that the VM instance is already deleted; however, the VMSS remains due to a stale NIC reference. NRP has completed the backend dependency cleanup. Requesting to proceed with complete cleanup of the VMSS
MC_ RG won’t drop because the AKS RP still holds a lock on the VMSS chain; just open Support → Technical → AKS → Cluster mgmt → Resource‑deletion and ask them to clear it. If that doesn’t move, have them run an RP‑side purge.
This actually is my support request! For non-critical requests they redirect you to answers forum now
Thanks for the update — understood. I’d still surface it to support as an RP‑side lock case. the orphaned MC_ RG can’t be cleared from the portal; AKS RP needs to purge the VMSS chain.