Currently databricks workspace is in deploying state and not able to delete or create

Question

Answer 1

Sowmya H P - Thanks for the question and using MS Q&A platform.

How long the deployment is in deploying state after creating the databricks workspace?

Why this error occurs in first place?

The Databricks workspace is stuck in Deploying because the Azure Resource Manager (ARM) deployment failed or didn’t complete, leaving the resource in a locked transitional state. Common causes include failed dependencies (Managed Identity, Key Vault, networking) or partial provisioning.

If the Databricks workspace stays in Deploying for more than 30 minutes, it usually indicates a failed or stuck ARM deployment. Here’s what you should do:

Actions Required to resolve this issue:

Step1: Check Deployment Logs

• Go to Resource Group → Deployments.
• Look for the failed deployment and review error details.

Step2: Cancel or Delete or Redeploy the Deployment

• If the deployment is still active, Cancel it.
• Then Delete the failed deployment entry.
• Click on Redeploy

Step3: Force Delete the Workspace using Azure PowerShell or Azure CLI.

az databricks workspace delete \
  --resource-group rg-10387803-tfmod-databricksprovider-dependency-test \
  --name adbs-10387803testcase \
  -y \
  --force-deletion \
  --retain-unity-catalog-data true

Step4: Review the activity logs and remove manually.

• Check Activity Logs for stuck dependencies (Managed Identity, Access Connector).
• Remove them manually.
• Retry deletion.

Step5: In case, if you are unable to resolve the issue. Please contact Azure Support by opening a support ticket. For details: How to create an Azure support request

• Subscription ID
• Resource Group name
• Workspace name
• Error details

Hope this helps. Let me know if you have any further questions or need additional assistance. Also, if these answer your query, do click the "Upvote" and click "Accept the answer" of which might be beneficial to other community members reading this thread.

---

𝘛𝘰 𝘴𝘵𝘢𝘺 𝘪𝘯𝘧𝘰𝘳𝘮𝘦𝘥 𝘢𝘣𝘰𝘶𝘵 𝘵𝘩𝘦 𝘭𝘢𝘵𝘦𝘴𝘵 𝘶𝘱𝘥𝘢𝘵𝘦𝘴 𝘢𝘯𝘥 𝘪𝘯𝘴𝘪𝘨𝘩𝘵𝘴 𝘰𝘯 𝘈𝘻𝘶𝘳𝘦 𝘋𝘢𝘵𝘢𝘣𝘳𝘪𝘤𝘬𝘴, 𝘥𝘢𝘵𝘢 𝘦𝘯𝘨𝘪𝘯𝘦𝘦𝘳𝘪𝘯𝘨, 𝘢𝘯𝘥 Data & AI 𝘪𝘯𝘯𝘰𝘷𝘢𝘵𝘪𝘰𝘯𝘴, 𝘧𝘰𝘭𝘭𝘰𝘸 𝘮𝘦 𝘰𝘯 𝘓𝘪𝘯𝘬𝘦𝘥𝘐𝘯.

Answer 2

Hi Sowmya H P,

It sounds like you're having an issue with your Azure Databricks workspace being stuck in a deploying state, which is preventing both deletion and creation of new resources. Here’s what you can do:

1. Check Provisioning State: First, you can check the provisioning status of your workspace. You can do this by navigating to the Azure portal and checking the Activity log for your Databricks workspace. If the status is Failed, you may need to delete the workspace.
2. Delete the Workspace:
   • Make sure that all clusters are terminated and that the workspace is no longer in use.
   • You can delete the workspace via the Azure portal or using the Azure CLI. If you’re using the CLI, run:

     
          az databricks workspace delete --resource-group <YourResourceGroup> --name <YourWorkspaceName> -y
     
     

   • If the workspace is in a Failed state, you might still be able to delete it. Make sure to confirm that it’s not locked or has any dependencies.
3. Check for Locks or Dependencies: If

you encounter issues while attempting to delete the workspace, check if there are any locks on it by going to the Locks section in the Azure portal, and remove any that might be preventing deletion. Also, make sure there are no dependencies that need addressing.

4. Wait for Cleanup:

Sometimes, the cleanup of resources after a deletion can take some time (5-10 minutes), so if you've initiated the deletion and it seems to be stuck, just give it a little while.

If you're still having issues, could you provide a bit more detail? Here are some follow-up questions:

• What specific error message do you see when you try to delete or create a new workspace?
• Have you tried terminating all clusters associated with that workspace?
• Are there any locks or dependencies listed in the resources associated with the workspace?

Let me know how it goes or if you need further assistance!

References:

• Deploy a workspace using the Azure Portal
• Diagnose and resolve issues with workspace deletion
• Delete a workspace with Azure CLI