An Apache Spark-based analytics platform optimized for Azure.
The behavior matches a stuck or inconsistent control-plane state for the Databricks workspace. There is no documented self-service operation that can repair a workspace that is already stuck in Deleting for days; available tools only cover normal delete and force-delete paths.
From the documented options, the only supported delete mechanisms are:
- Delete the workspace normally
- From Azure portal: open the Databricks workspace resource and select Delete.
- Or via CLI:
az databricks workspace delete \ --name DatabricksDemoRG \ --resource-group David_group - Or via PowerShell:
Remove-AzDatabricksWorkspace -Name DatabricksDemoRG -ResourceGroupName David_group
- Force delete the workspace catalog and managed resource group
This only applies if the workspace is still in a normal state and the goal is to ensure the managed resource group and Unity Catalog data are removed at delete time:
- Azure portal: when deleting the workspace, select the checkbox to delete the workspace along with its managed resource group.
- Azure CLI:
az databricks workspace delete \ --name DatabricksDemoRG \ --resource-group David_group \ --force-deletion true - Azure PowerShell:
Remove-AzDatabricksWorkspace \ -Name DatabricksDemoRG \ -ResourceGroupName David_group \ -ForceDeletion - Or by deleting the parent resource group with force-deletion types:
az group delete \ --name David_group \ --force-deletion-types Microsoft.Databricks/workspacesRemove-AzResourceGroup \ -Name David_group \ -ForceDeletionType Microsoft.Databricks/workspaces \ -Force
- Soft-delete behavior and retention
- When a Databricks workspace is deleted successfully, it enters a 7‑day soft-delete state where only Databricks-managed metadata may be recoverable; Azure resources (VMs, disks, networking) are cleaned up immediately.
- This retention does not block deletion of the Azure resource itself; it only affects Databricks-side metadata. A workspace stuck in
Deletingfor days is not a normal part of this retention behavior.
Given that:
- The workspace is already in
Deletingfor multiple days. - Standard delete and force-deletion paths have been tried.
- The resource group and subscription deletions are blocked by this state.
There is no additional documented CLI/PowerShell or portal operation that can clear a Databricks workspace that is already stuck in Deleting. Resolution in such cases requires backend intervention by Microsoft/Azure Databricks support to fix the control-plane state and complete or roll back the delete.
The practical next step is to open a support case with Azure (or via the Databricks support channel if available for the workspace) and provide:
- Subscription ID, resource group, workspace name, and region.
- The fact that provisioningState is
Deletingfor >72 hours. - The errors
ApplianceBeingDeleted,ResourceGroupDeletionBlocked, andResourceNotFoundfor management operations.
Support can then clear the stuck resource so that resource group and subscription deletion can proceed.
References: