I can not delete the databrick workspace

Question

Databricks workspace stuck in Deleting state. Cannot delete workspace or resource group. Getting error ApplianceBeingDeleted . Tried Azure CLI, PowerShell Az module— all failed. How to resolve?"

Code: ResourceGroupDeletionBlocked

Message: Deletion of resource group 'dev-mobility-rg' failed as resources with identifiers 'Microsoft.Databricks/workspaces/Mobility-WS' could not be deleted.

Exception Details: (None) {"error":{"code":"ApplianceBeingDeleted","message":"The operation cannot be performed on the appliance 'Mobility-WS' because it is being deleted"}}

    Code: None

    Message: {"error":{"code":"ApplianceBeingDeleted","message":"The operation cannot be performed on the appliance 'Mobility-WS' because it is being deleted"}}

Answer 1

Hello Ngô Khang,

Welcome to the Microsoft Q&A and thank you for posting your questions here.

I understand that you are unable to delete the Databrick workspace.

Azure Databricks workspaces stuck in Deleting or Creating states cannot be removed by your actions because the appliance and its managed resource group hold system deny assignments that block deletion. The only effective step you should attempt locally is a single forced delete to generate backend telemetry using: az databricks workspace delete --name <workspace> --resource-group <rg> --force-deletion true --yes -https://learn.microsoft.com/azure/databricks/admin/workspace/delete-workspace

If this command fails with ApplianceBeingDeleted or ApplianceBeingCreated, it confirms the workspace is in a corrupted appliance state that cannot be corrected through portal, CLI, PowerShell, or ARM operations. These errors occur when Databricks internally locks the appliance during failed deployment or partial deletion, preventing all customer‑side remediation. - https://learn.microsoft.com/azure/databricks/admin/workspace/delete-workspace

To resolve the issue fully, you must open an Azure Support request from your Azure Portal, providing the workspace name, resource group, managed resource group, subscription ID, and Activity Log correlation IDs from the failed delete attempt. Support will execute a backend forced purge, removing appliance metadata, deny assignments, and clearing blocked resources.

After backend cleanup completes, verify removal by checking the workspace and managed resource group no longer appear in your subscription, and confirm that dependent assets such as storage accounts, NAT gateways, and VNets have been released. You may then redeploy a new Databricks workspace cleanly using:

az databricks workspace create --name <new> --resource - https://learn.microsoft.com/azure/databricks/admin/workspace/create-workspace

I hope this is helpful! Do not hesitate to let me know if you have any other questions or clarifications.

---

Please don't forget to close up the thread here by upvoting and accept it as an answer if it is helpful.