Share via

Unable to delete ghost dabatricks workspace

Azure Administrator 0 Reputation points
2026-03-02T13:38:36.3066667+00:00

I have a Databricks workspace which I don't see in the Azure Portal anymore.

I have tried to force delete it with the Remove-AzDatabricksWorkspace but it does not work.

The documentation says I need to contact a Microsoft tech support so the can delete it.

I have the JSON resource ID if needed.

Azure Databricks
Azure Databricks

An Apache Spark-based analytics platform optimized for Azure.

{count} votes

Answer accepted by question author
  1. Manoj Kumar Boyini 9,180 Reputation points Microsoft External Staff Moderator
    2026-03-02T15:42:00.8666667+00:00

    Hi Azure Administrator

    The core Databricks team has removed the orphaned workspace from the backend using the provided Resource ID.

    The workspace has now been deleted. Could you please verify and confirm?

    If you have similar ghost or orphaned resource issues in the future, please reach out to Microsoft Q&A.

    0 comments No comments

1 additional answer

Sort by: Most helpful
  1. Jerald Felix 10,975 Reputation points
    2026-03-02T13:55:32.44+00:00

    Hello Azure Administrator,

    Thanks for raising this question in Azure Q&A forum.

    A "ghost" Azure Databricks workspace that appears in the Azure portal but has no URL, no managed resource group, and cannot be deleted is a known provisioning failure state where the workspace resource remains in a "stuck Accepted" provisioning state indefinitely. This is not recoverable through standard CLI/Portal deletion and requires Microsoft engineering intervention.

    Why this happens

    The workspace got stuck during the Appliance deployment phase (the internal Databricks control plane VM deployment). The Azure Databricks resource provider failed to complete the workspace URL assignment and managed resource group creation, leaving the resource in a limbo state where normal deletion operations fail with errors about "resource still provisioning" or "deny assignment from managed RG" (even though no managed RG actually exists).

    Step 1 — Confirm the stuck state

    Verify the exact symptoms:​

    bash
    az databricks workspace show --name dabatricks-workspace --resource-group <rg> --query "{provisioningState:provisioningState, workspaceUrl:workspaceUrl}"
    

    Expected output:

    text
    {
      "provisioningState": "Accepted",
      "workspaceUrl": null
    }
    

    Step 2 — Attempt force deletion (will likely fail but required)

    bash
    # CLI force delete
    

    These will fail with errors about provisioning state or deny assignments.

    Step 3 — Open an Azure Support Ticket (the only fix)

    This is a platform-level issue that requires Azure Databricks resource provider engineering to purge the stuck appliance deployment from the backend. Create a Severity A support ticket immediately:

    Support Ticket Details to Include:

    text
    Title: Azure Databricks workspace stuck in "Accepted" provisioning state - cannot delete
    
    Symptoms:
    1. az databricks workspace show shows provisioningState: "Accepted", workspaceUrl: null
    2. No workspace URL accessible, no managed resource group created
    3. Delete operations fail with [exact error message]
    4. No active clusters/jobs running
    
    Request:
    Escalate to Azure Databricks resource provider engineering team to:
    - Purge the stuck appliance provisioning state
    - Remove any backend deny assignments preventing deletion
    - Allow clean deletion of the ghost workspace resource
    
    Resource Details:
    - Workspace: dabatricks-workspace
    - RG: <your-rg>
    - Subscription: <sub-id>
    - Region: <region>
    

    Step 4 — Post-ticket cleanup (after engineering unblocks)

    Once Microsoft clears the backend state:

    bash
    # Delete the workspace resource
    

    Why standard methods don't work

    Azure Portal delete waits for provisioningState to change from "Accepted" — which never happens

    CLI/PowerShell force delete fails due to backend deny assignment from the incomplete appliance deployment

    Resource Group deletion fails due to the workspace resource dependency

    Prevention

    Always monitor workspace provisioning with az databricks workspace show during initial deployment. If it stays "Accepted" for >2 hours with workspaceUrl: null, cancel immediately before it becomes a ghost resource.​

    If it helps kindly accept the answer.

    Best Regards,

    Jerald Felix

    0 comments No 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.