Share via

Azure Databricks workspace stuck in Deleting state; managed resource group still contains resources

Shubham Gandhi 0 Reputation points
2026-05-16T16:10:09.6666667+00:00

My Azure Databricks workspace is stuck in the Deleting state and cannot be deleted again from the Azure Portal or Azure CLI.

Workspace details:

[Redacted PII Information]

Issue:

The workspace has been stuck in the “Deleting” state for a long time. The Azure Portal deletion does not complete, and Azure CLI also cannot proceed further.

CLI command used:

az databricks workspace delete --resource-group DataStorageGroup --name Azure_[Redacted] --yes

CLI output:

(ApplianceBeingDeleted) The operation cannot be performed on the appliance 'Azure_[Redacted]' because it is being deleted.

I also verified the following:

  • No locks exist in the Databricks workspace Locks section.
  • Managed Resource Group still contains resources such as:
    • Managed Identity
    • Storage Account
    • NAT Gateway
    • Public IP
    • Network Security Group
    • Virtual Network

I also attempted to manually delete NAT Gateway, Public IP, and Virtual Network resources from the managed resource group, but Azure does not allow them to be deleted either.

Current concern:

Since the workspace and managed resources are stuck, I want help with backend cleanup or force deletion of the Databricks workspace and its managed resource group to avoid unnecessary Azure charges.

Please guide me on how to fully remove these stuck resources.

Azure Databricks
Azure Databricks

An Apache Spark-based analytics platform optimized for Azure.

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Alex Burlachenko 21,795 Reputation points MVP Volunteer Moderator
    2026-05-20T07:41:28.7766667+00:00

    hi Shubham Gandhi & thanks for join me here at Q&A portal,

    workspace delete is half-complete and managed RG is orphaned, only Microsoft/Databricks backend can purge it. Once Databricks workspace is in Deleting, Azure blocks new delete/update operations, so ApplianceBeingDeleted is expected. The managed resource group still having NAT/Public IP/VNet/etc means the Databricks appliance cleanup did not finish. Those resources are owned/locked by the Databricks workspace lifecycle, so manual delete often fails too. First check RG-level locks and Activity Log just to capture errors, but dont keep retrying individual deletes. Open Azure Support under Azure Databricks and ask for backend force delete / appliance cleanup. Include workspace name, workspace resource ID, managed resource group name, original resource group DataStorageGroup, CLI error ApplianceBeingDeleted, and list of remaining managed resources. For charges, delete anything not blocked, stop any unrelated compute, and ask support to confirm billing impact while resource is stuck.

    rgds,

    Alex

    &

    If my answer was helpful pls mark it and additional thx if u follow me at Q&A portal

    Was this answer helpful?

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.