An Apache Spark-based analytics platform optimized for Azure.
The workspace is in a stuck “Deleting” state and CLI deletion attempts are failing because the underlying appliance is already in a delete operation. There is no additional self-service action available beyond what has already been tried.
For Azure Databricks workspaces, deletion is normally handled by:
- Deleting the workspace resource itself.
- Automatically deleting the managed resource group and deployed resources.
If the workspace delete is stuck and az databricks workspace delete --force-deletion and az group delete both fail with ApplianceBeingDeleted, the only resolution path is a backend fix by Microsoft support to reset or complete the delete operation on the appliance.
Because this is a control-plane issue with the workspace/appliance state, open a support request with Microsoft Azure Support and provide:
- Workspace name and resource group.
- Subscription ID and region.
- Managed resource group name.
- Error code and message (
ApplianceBeingDeleted - The operation cannot be performed on the appliance ... because it is being deleted). - A list of commands already attempted (
az databricks workspace delete --force-deletion,az group delete).
Once support resets or completes the backend delete, the workspace and managed resource group can be removed and the stuck state will clear.
References: