Cannot delete an Azure Local cluster
Failed to delete resource group and Azure local cluster
Azure Local
-
Hemalatha • 14,620 Reputation points • Microsoft External Staff • Moderator
2026-06-23T00:56:04.8066667+00:00 Hello Bill,
Thank you for reaching out Q/A and sharing the details.
I reviewed the error message and confirmed that the resource group deletion is failing because the Azure Local cluster resource: Microsoft.AzureStackHCI/clusters/rc0101-cl is not being deleted successfully.
Azure Local cluster resource deletion failed, which caused the resource group deletion to be rolled back with the errors: ResourceGroupDeletionBlocked ResourceDeletionFailed
For Azure Local environments, the cluster resource needs to be properly unregistered and cleaned up before removing the Azure resource. A direct resource group deletion can fail if the Azure Local registration, Azure Arc integration, locks, or dependent resources are still present.
As a first step, we recommend unregistering the Azure Local cluster from one of the cluster nodes. From an elevated PowerShell session on any Azure Local node, please run:
Unregister-AzStackHCI
-SubscriptionId "ff37bfea-eb2d-4bfa-99bb-ab00a8b50ac7"-ResourceName "RG_RESOURCE_ NAME" ` -ResourceGroupName "RG_NAME"This will remove the Azure Local cluster resource from Azure and complete the unregister operation.
If the unregister operation fails due to Azure Arc integration issues, please verify the Arc integration status on the affected node. In scenarios where Arc cleanup is incomplete, the Azure Arc integration may need to be disabled before retrying the unregister operation.
Additionally, please verify whether any resource locks exist on the resource group, as Azure Local deployments may create protection locks to prevent accidental deletion.
You can check this from: Azure Portal → Resource Group → Settings → Locks
If any DoNotDelete or similar locks are present, remove them before retrying the cleanup.
If the Azure Local cluster nodes are no longer available (for example, the hosts were reimaged or removed), the remaining Azure resource may need to be cleaned up manually. In that scenario, we would need to validate and remove any remaining Azure Arc registration artifacts and Microsoft Entra application registrations associated with the cluster.
After the Azure Local cluster resource is successfully removed, the resource group deletion should complete successfully.
Please also review the Activity Log using the tracking ID below and share the detailed failure message if the issue continues: Tracking ID: b3ec7141-5783-4cff-b491-ee3ec9c39998
You can find this under: Azure Portal → Monitor → Activity Log → Failed operations
Related documentation:
Troubleshoot Azure Stack HCI registration
-
Bill Snider • 0 Reputation points • Microsoft Employee
2026-06-23T01:36:28.9+00:00 This is part of a CI pipeline and the nodes have all been deleted and reinstalled already. The cluster resource is the only thing left in the resource group. I don't see any locks or other hidden files. How can I find any Azure Arc registration artifacts or Microsoft Entra application registrations for this cluster? They all get logged as s_cluster.
-
Hemalatha • 14,620 Reputation points • Microsoft External Staff • Moderator
2026-06-23T18:14:16.4033333+00:00 Hello Bill
Could you please check the private message and provide necessary details
-
Hemalatha • 14,620 Reputation points • Microsoft External Staff • Moderator
2026-06-24T17:00:28.44+00:00 Hello Bill,
We have engaged the Azure Local engineering team regarding the cluster deletion issue.
The team has confirmed that this is a known platform-side issue affecting specific internal build versions. In the latest 2607 builds, storage volumes are being reported to the Azure control plane, which triggers a deletion failure due to a bug in the Azure Local Resource Provider (RP).
The engineering team has already implemented a fix, and the deployment of the fix to production regions is currently in progress.
Current rollout status:
- Southeast Asia region is expected to receive the fix today.
- East US region is expected to receive the fix tomorrow.
- Full rollout across all production regions is targeted to complete by July 1, 2026.
At this time, there is no available workaround to successfully delete the Azure Local cluster until the fix has been deployed to the affected region.
-
Alex Burlachenko • 23,250 Reputation points • MVP • Volunteer Moderator2026-06-25T11:43:40.6533333+00:00 hi Bill Snider & thx for sharing urs issue here at Q&A portal,
Need more detail, but for Azure Local / Arc resources, RG delete usually fails bc child resources or Arc registrations are still hanging around. Check the failed delete error in Activity Log first. It should show the exact resource that blocked the RG delete.
Common blockers are locks, connected machines, Arc resource bridge, custom locations, Kubernetes extensions, Azure Local cluster resource, storage/network child resources, or a delete operation already stuck in progress.
az lock list -g <rg>
az resource list -g <rg> -o table
Then delete child resources first, not the whole RG. If something is stuck, grab its resource ID and provisioning state
az resource show --ids <resource-id> --query "{type:type, state:properties.provisioningState}"
https://learn.microsoft.com/en-us/azure/azure-local/manage/delete-cluster
https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/delete-resource-group
https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/lock-resources
If the cluster resource is stuck deleting, open support w/ the cluster resource ID, RG name, region, Activity Log correlation ID, and the exact failed delete message. Without that error, it’s basically guessing.
rgds,
Alex
&
If my answer was helpful pls mark it and additional thx if u follow me at Q&A portal and at my blog https://ctrlaltdel.blog/
Sign in to comment