Microsoft.Databricks workspaces The DeploymentBeingDeleted error occurs when attempting to modify or deploy a resource in Azure while it is in the process of being deleted. This issue is encountered with resources such as Microsoft.Databricks workspaces,

Question

My Azure Databricks workspace ADBNikhilProject in resource group Azure_Fundamentals is stuck in a deleting state.

Issue

I am unable to:

• Delete the Databricks workspace

Delete the resource group

Errors

ApplianceBeingDeleted

ResourceGroupDeletionBlocked

Actions already attempted

az databricks workspace delete --force-deletion

az group delete --force-deletion-types Microsoft.Databricks/workspaces

Both commands fail with:

"The operation cannot be performed because it is being deleted"

This appears to be a backend issue where the workspace is stuck in a deleting state. Could you please assist with force cleanup or backend purge so that the resource group can be deleted?

Answer 1

Hey Nikhil,
it looks like your Databricks workspace is stuck in a “Deleting” state and ARM has locked both the workspace and its resource group. Here’s a checklist of things you can try before escalating to a back-end force-purge via support:

1. Monitor the deletion status • In the Azure Portal, go to the Notifications blade or the Activity Log for the workspace’s resource group.

 az databricks workspace show \
       --resource-group Azure_Fundamentals \
       --name ADBNikhilProject
     ```  

 Watch the `provisioningState` field—if it’s still `Deleting`, it’s just an asynchronous ARM delay.

2. Check for locks or dependencies • List locks on the resource group:

az lock list --resource-group Azure_Fundamentals
     ```  

 Remove any ReadOnly or Delete locks with:  

 az lock delete --lock-name <lockName> --resource-group Azure_Fundamentals
     ```  

• Survey remaining resources in the RG:

az resource list --resource-group Azure_Fundamentals
     ```  

 Delete any lingering dependencies (private endpoints, NICs, storage accounts, etc.) that might be holding up the workspace deletion.

3. Wait for propagation Azure Resource Manager operations can occasionally take upwards of 20–30 minutes (or longer if there were network hiccups or service-level dependencies). If you can, let it sit for a bit and then re-check the state with az databricks workspace show.
4. Retry the RG delete once the workspace disappears Once the workspace is fully gone, your az group delete --name Azure_Fundamentals command should succeed.
5. Open a support ticket for a back-end purge if it never clears If after 1–2 hours the provisioningState still shows Deleting, this is a known “stuck delete” scenario where we have to intervene on the back end. and reference the workspace name/ID along with your subscription and RG. We can force-purge the resource and unblock the group deletion.

References

• Unable to delete this databricks workspace (propagation delay) – Link: https://docs.microsoft.com/4511240040011277

• Resolve DeploymentBeingDeleted for Microsoft.Databricks workspaces – https://docs.microsoft.com/azure/databricks/error-messages/deployment-being-deleted

• Resolve ResourceGroupBeingDeleted for Azure Databricks workspaces – https://docs.microsoft.com/azure/databricks/error-messages/resourcegroup-being-deleted

Hope this helps. If you have any follow-up questions, please let me know. I would be happy to help.
Please do not forget to "Accept Answer" and "up-vote" wherever the information provided helps you, as this can be beneficial to other community members.