Issue: Resource stuck deleting / DenyAssignmentAuthorizationFailed

Question

Issue: Resource stuck deleting / DenyAssignmentAuthorizationFailed

Lokesh Butra 0

Hi Team,

I am facing deleting issue every time when I created data brick . I tried all options to delete work space but I am getting access denied issue. I cancel subscription and create new one but no luck. Can you please help me to the steps for resolving issue?

SAI JAGADEESH KUDIPUDI 3,645 Reputation points Microsoft External Staff Moderator

2026-03-17T15:09:06.67+00:00
Hi Lokesh Butra,
it looks like you’re hitting a service-side deny assignment or lock on the Databricks managed resource group (MRG), which by design you can’t delete directly. Instead you need to delete the Databricks workspace itself and let the service clean up the MRG. Here’s what you can try:

Stop all active Databricks clusters and jobs

Make sure there are no running clusters, jobs or interactive sessions in your workspace.

Delete the workspace (not the MRG)

Azure Portal: Go to your Databricks workspace resource → Delete → OK

Azure CLI:
az databricks workspace delete \ --resource-group <YourResourceGroup> \ --name <YourWorkspaceName> \ -y

PowerShell:
Remove-AzDatabricksWorkspace -ResourceGroupName <YourResourceGroup> -Name <YourWorkspaceName>

Wait for asynchronous cleanup (5–10 minutes)

The service will automatically remove the MRG, VNet, NSGs, disks, etc.

Don’t attempt to intervene in the MRG—those system-level locks and deny assignments get removed only when the parent workspace is gone.

If the workspace deletion hangs or shows “Deleting” indefinitely: a. Check for resource locks

In the portal: Resource groups → your MRG → Locks → delete any ReadOnly/Delete locks

CLI: az lock list --resource-group <MRG>

b. Inspect Azure activity logs for errors (correlation ID will help us pinpoint root cause) c. If you see errors about the AzureDatabricksRP application being disabled, re-enable the Microsoft.Databricks first-party app in your tenant (see “Resources stuck in deleting or deployment state” below).

Retry the delete once locks are removed and the Databricks RP app is enabled.

Follow-up questions if you still see “access denied” or the workspace won’t delete after these steps:

• What exact error message and error code do you see (including correlation ID)?

• Subscription ID, resource group name and workspace name you’re trying to delete

• Your Azure role (Owner/Contributor/etc.) on both the subscription and that resource group

• Any resource locks you see on the MRG or workspace RG

Hope this helps. If you have any follow-up questions, please let me know. I would be happy to help.

Please do not forget to "up-vote" wherever the information provided helps you, as this can be beneficial to other community members.
SAI JAGADEESH KUDIPUDI 3,645 Reputation points Microsoft External Staff Moderator

2026-03-25T03:16:36.21+00:00

Hi **Lokesh Butra,
**I hope you had a chance to review the information shared earlier, and I hope this information has been helpful! If you still have questions, please let us know what is needed in the comments so the question can be answered.
SAI JAGADEESH KUDIPUDI 3,645 Reputation points Microsoft External Staff Moderator

2026-03-26T12:15:29.37+00:00

Hi Lokesh Butra,
This issue appears to be impacting several customers Globally, as we have noticed many cases in today's queue experiencing the same problem. We are coordinating with the relevant team for further investigation. We are closely monitoring similar incidents and will share updates as soon as we have more information. Thank you for your understanding.

1 answer

Your answer

SAI JAGADEESH KUDIPUDI 3,645 Reputation points Microsoft External Staff Moderator

2026-03-25T03:16:36.21+00:00

Hi **Lokesh Butra,
**I hope you had a chance to review the information shared earlier, and I hope this information has been helpful! If you still have questions, please let us know what is needed in the comments so the question can be answered.
SAI JAGADEESH KUDIPUDI 3,645 Reputation points Microsoft External Staff Moderator

2026-03-26T12:15:29.37+00:00

Hi Lokesh Butra,
This issue appears to be impacting several customers Globally, as we have noticed many cases in today's queue experiencing the same problem. We are coordinating with the relevant team for further investigation. We are closely monitoring similar incidents and will share updates as soon as we have more information. Thank you for your understanding.

Answer 1

Follow these steps to resolve Azure Databricks workspace delete issues and access-denied errors:

Verify delete permissions on the workspace
- In the Azure portal, open the Databricks workspace resource.
- Go to Access control (IAM).
- Check the role assignments for the signed-in identity.
- Ensure a role is assigned that allows delete on the resource (for example, a role that includes Microsoft.Databricks/workspaces/delete via built-in roles like Owner/Contributor at the subscription, resource group, or workspace level).
- If the required role is missing, have the subscription or resource group Owner grant an appropriate role and then retry deletion.
Delete the workspace from Azure portal (Databricks UI path)
- Sign in to the Azure Databricks workspace as the account owner (the identity that originally created the workspace).
- In the top bar, select the username → Azure portal.
- In the Azure Databricks service blade that opens, select Delete and follow the prompts to delete the workspace.
- This initiates workspace deletion and cleans up most compute resources.
Use Azure CLI if portal delete is blocked
- If the portal delete button is disabled or fails, use Azure CLI:
```
     az databricks workspace delete \
       --name <workspace-name> \
       --resource-group <resource-group-name> \
       --subscription <subscription-id> \
       --yes
```
- If Unity Catalog is enabled and there is a need to control catalog data retention, add --force-deletion as needed based on the desired catalog behavior.
Understand retention behavior after delete
- After a successful delete, the workspace enters a 7‑day soft-delete state. During this time, some Databricks-managed metadata (notebooks, jobs, configs) may be recoverable, but Azure resources such as VMs, disks, and networking are cleaned up immediately and cannot be restored.
- Treat deletion as permanent and ensure all important data is backed up before retrying deletion.
If deletion is still blocked by deny assignments
- If a DenyAssignmentAuthorizationFailed or similar access-denied error persists even for a subscription Owner, it typically indicates a deny assignment at subscription or resource group scope.
- A user with sufficient privileges at the tenant or management group level must remove or adjust the deny assignment that blocks delete on the Databricks workspace resource, then retry the delete (portal or CLI).
If the workspace is stuck in deleting or cannot be removed
- If the workspace remains in a stuck state (for example, deleting for a long time) even after permissions and deny assignments are corrected, open an Azure support request so the backend team can force-complete the delete.
Be aware of workspace deletion retention policy
- During the 7‑day retention period, the workspace name and metadata may still be reserved. Avoid recreating a workspace with the same name until the soft-delete period has expired or the backend has completed the hard delete.

References: