Unable to delete Databricks managed resource group after it's Databricks workspace deletion

Question

I recently deleted a Databricks workspace (databricks-test), but the associated managed resource group (databricks-rg-databricks-test-wuvmnal2weo6e) still remains in my Azure subscription. When I try to delete it manually, it fails, it seems like the managed resource group might be corrupted or in a stuck state.

Here’s what I’ve tried so far:

• Verified that the actual Databricks workspace is fully deleted.
• Attempted force delete of management resource group via Azure CLI and Portal, but still unsuccessful.

Issue: The managed resource group appears empty or corrupted, but Azure won’t let me remove it.

Question: How can I completely delete this managed resource group and clean up any residual/corrupted state left behind by the deleted Databricks workspace?

Any guidance or experience resolving this would be appreciated.

Answer 1

Hi Balaji Krishnan This issue can happen when the Databricks-managed resource group gets stuck due to hidden dependencies or incomplete cleanup during workspace deletion.

Here are some troubleshooting steps:

Check for Hidden Resources: Use Azure Resource Graph Explorer to ensure no hidden resources remain:

Resources
| where resourceGroup == "databricks-rg-databricks-test-wuvmnal2weo6e"

Look for Stuck Deployments: In the Azure Portal, go to: Resource Group > Deployments Delete any failed or stuck entries.

Check for Locks: Run this via CLI to list/delete any locks:

az lock list --resource-group databricks-rg-databricks-test-wuvmnal2weo6e
az lock delete --name <lock-name> --resource-group databricks-rg-databricks-test-wuvmnal2weo6e

Try Force Delete via REST API: Sometimes the Portal/CLI doesn't work if the RG is in a bad state. Use REST API:

• List resources in the group: GET https://management.azure.com/subscriptions/{subscriptionId}/resourcegroups/{rgName}/resources?api-version=2021-04-01
• Delete any listed resources manually If the group is truly empty and still won’t delete, it's likely backend-locked.

---

Hope this helps. If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.