Can not delete a workspace

Question

Can not delete a workspace

Ngô Khang 0

Databricks workspace stuck in Deleting state. Cannot delete workspace or resource group. Getting error ApplianceBeingDeleted . Tried Azure CLI, PowerShell Az module - i try all and 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"}}

Maksood Ahmed 100 Reputation points Microsoft External Staff Moderator

2026-10-07T15:24:30.1+00:00
Hi @Ngô Khang ,

The error ApplianceBeingDeleted means the Azure Databricks workspace is already in a deletion state, but the deletion has not completed. Because of this, Azure is also blocking deletion of the resource group. Similar cases show the same combination of ApplianceBeingDeleted and ResourceGroupDeletionBlocked.

Since you have already tried the Azure portal, CLI, and PowerShell, please try the resource-group force deletion:

az group delete --name dev-mobility-rg --force-deletion-types Microsoft.Databricks/workspaces

This force-deletion option has been recommended for the same stuck Databricks workspace scenario.

If this also returns ApplianceBeingDeleted, further retries from the portal, CLI, or PowerShell are unlikely to clear the stuck state. At that point, please open an Azure support request for Azure Databricks and provide:

Workspace name

Resource group name

Subscription ID and region

ApplianceBeingDeleted error

Failed operation/correlation ID from the Azure Activity Log

A similar Azure Databricks case required investigation of the stuck appliance state after the available deletion methods failed.

FYR: Delete an Azure Databricks workspace Azure CLI Databricks workspace commands
Maksood Ahmed 100 Reputation points Microsoft External Staff Moderator

2026-10-08T12:34:13.62+00:00

Hi @Ngô Khang ,

Just following up to check whether you were able to try the force deletion option suggested above.

Please let us know if the workspace was deleted successfully or if you are still receiving the ApplianceBeingDeleted error. We will be happy to assist further.
Ngô Khang 0 Reputation points

2026-10-09T02:45:53.9766667+00:00

I did try the az group delete --name dev-mobility-rg --force-deletion-types Microsoft.Databricks/workspaces command and it still does not work with ApplianceBeingDeleted error still existing
Maksood Ahmed 100 Reputation points Microsoft External Staff Moderator

2026-10-09T07:47:35.32+00:00

Hi @Ngô Khang ,

Thank you for the update.

Since you have already tried the Portal, CLI, PowerShell, and force-deletion command and the workspace is still showing ApplianceBeingDeleted, please open an Azure Support ticket for Azure Databricks for further investigation.

Please include the workspace name, resource group, subscription ID, region, and the ApplianceBeingDeleted / ResourceGroupDeletionBlocked error details in the support request.

2 answers

Your answer

Maksood Ahmed 100 Reputation points Microsoft External Staff Moderator

2026-10-07T15:24:30.1+00:00

Hi @Ngô Khang ,

The error ApplianceBeingDeleted means the Azure Databricks workspace is already in a deletion state, but the deletion has not completed. Because of this, Azure is also blocking deletion of the resource group. Similar cases show the same combination of ApplianceBeingDeleted and ResourceGroupDeletionBlocked.

Since you have already tried the Azure portal, CLI, and PowerShell, please try the resource-group force deletion:

az group delete --name dev-mobility-rg --force-deletion-types Microsoft.Databricks/workspaces

This force-deletion option has been recommended for the same stuck Databricks workspace scenario.

If this also returns ApplianceBeingDeleted, further retries from the portal, CLI, or PowerShell are unlikely to clear the stuck state. At that point, please open an Azure support request for Azure Databricks and provide:

Workspace name

Resource group name

Subscription ID and region

ApplianceBeingDeleted error

Failed operation/correlation ID from the Azure Activity Log

A similar Azure Databricks case required investigation of the stuck appliance state after the available deletion methods failed.

FYR: Delete an Azure Databricks workspace Azure CLI Databricks workspace commands
Maksood Ahmed 100 Reputation points Microsoft External Staff Moderator

2026-10-08T12:34:13.62+00:00

Hi @Ngô Khang ,

Just following up to check whether you were able to try the force deletion option suggested above.

Please let us know if the workspace was deleted successfully or if you are still receiving the ApplianceBeingDeleted error. We will be happy to assist further.
Ngô Khang 0 Reputation points

2026-10-09T02:45:53.9766667+00:00

I did try the az group delete --name dev-mobility-rg --force-deletion-types Microsoft.Databricks/workspaces command and it still does not work with ApplianceBeingDeleted error still existing
Maksood Ahmed 100 Reputation points Microsoft External Staff Moderator

2026-10-09T07:47:35.32+00:00

Hi @Ngô Khang ,

Thank you for the update.

Since you have already tried the Portal, CLI, PowerShell, and force-deletion command and the workspace is still showing ApplianceBeingDeleted, please open an Azure Support ticket for Azure Databricks for further investigation.

Please include the workspace name, resource group, subscription ID, region, and the ApplianceBeingDeleted / ResourceGroupDeletionBlocked error details in the support request.

Answer 1

Hi Ngô Khang & thx for join me at Q&A platform,

ApplianceBeingDeleted usually means Azure Databricks has already accepted the workspace deletion, but the backend cleanup hasn't finished. The resource group deletion is failing bc Azure Resource Manager still sees Mobility-WS as an existing resource. I'd check the workspace's provisioningState with az resource show and look at the Activity Log for the original delete operation. Pay attention to whether that operation failed, timed out, or is still reporting InProgress. Also check how long the workspace has been stuck. A normal asynchronous deletion can take some time, but being stuck for hours with the same error is a different story.

If the workspace is permanently stuck in Deleting, repeating the delete through CLI or PowerShell probably won't help. Both use the same Azure resource provider, so changing tools won't bypass the backend state.

I'd open an Azure support case for the Microsoft.Databricks resource provider and ask them to investigate the stuck workspace deletion and complete the backend cleanup. Include the workspace resource ID, region, original deletion timestamp, and Activity Log correlation ID. Don't manually delete the Databricks managed resource group or try to force-remove the resource from ARM. That can leave orphaned infrastructure behind. The resource provider needs to finish cleaning up the workspace before dev-mobility-rg can be deleted successfully.

rgds,

Alex

Answer 2

Deleted

This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Comments have been turned off. Learn more