Databricks workspace is not getting deleted since 48 hours

Question

I am experiencing an issue with an Azure Databricks workspace that has been stuck in the “Deleting” state for more than 48 hours.

The workspace was initiated for deletion along with its associated resource group; however, the deletion process has not completed and appears to be stalled. As a result, the resource group deletion is also failing due to this dependency.

Answer 1

Hi Santosh Nair,
sorry you’re seeing your Databricks workspace stuck in “Deleting” for over 48 hours—that’s way longer than the usual 5–10 minutes cleanup window. Here’s how you can unstick it:

1. Check the workspace deletion status • Run: az databricks workspace show \

   --resource-group <YourResourceGroup> \
   
   --name <YourWorkspaceName>  
   

   • Verify provisioningState is still “Deleting.”
2. Terminate any lingering compute or network dependencies • In the portal or via CLI, make sure all clusters are terminated and no jobs are running. • List all resources in the Managed Resource Group (MRG): az resource list --resource-group <YourManagedRG> • If you see VNets, NICs, disks, NSGs, private endpoints, etc., delete or detach them.
3. Remove any resource locks or deny assignments • List locks on both your RG and the MRG: az lock list --resource-group <YourResourceGroup> az lock list --resource-group <YourManagedRG> • Delete any “ReadOnly” or “CanNotDelete” locks: az lock delete --id <lock-resource-id>
4. Force delete the workspace (if needed) • CLI: az databricks workspace delete \

   --resource-group <YourResourceGroup> \
   
   --name <YourWorkspaceName> \
   
   --force-deletion  
   

   • Or delete the whole resource group with force-deletion of workspaces: az group delete \

   --name <YourResourceGroup> \
   
   --force-deletion-types Microsoft.Databricks/workspaces \
   
   --yes  
   

5. Re-check and retry • Rerun the “show” command to confirm the workspace is gone or in a Succeeded/Deleted state. • Once it’s fully deleted, you can recreate or remove the RG without errors.

If it’s still stuck, please share:

• The full output of az databricks workspace show ...
• Any errors you’re seeing in Activity Log or CLI
• Whether there are custom locks or private endpoints attached
• The exact CLI or portal steps you’ve taken

Reference docs:

• Diagnose and resolve issues with workspace deletion

https://learn.microsoft.com/azure/databricks/admin/workspace/delete-workspace

• Resolve DeploymentBeingDeleted errors

https://learn.microsoft.com/cli/azure/databricks/workspace?view=azure-cli-latest#az-databricks-workspace-delete

• Force-delete workspace catalog / MRG

https://learn.microsoft.com/azure/databricks/admin/workspace/delete-workspace#force-delete-the-workspace-catalog

• Troubleshoot ResourceGroupBeingDeleted

https://learn.microsoft.com/azure/databricks/error-messages/error-classes#resourcegroupbeingdeleted

Hope this helps you get past the stalled delete—let me know how it goes!

Note: This content was drafted with the help of an AI system. Please verify the information before relying on it for decision-making.