Share via

Unable to create databricks workspace

Srishti Ahlawat 0 Reputation points Microsoft Employee
2026-05-20T16:29:52.21+00:00

I am getting the error attached in the the image "quota exceeded" whenever I am trying to create a databricks workspace in my resource group even though I have deleted my previous databricks workspace, I suspect it is still consuming some quota but need help to identify and rectify this as soon as possible.

Azure Databricks
Azure Databricks

An Apache Spark-based analytics platform optimized for Azure.


1 answer

Sort by: Most helpful
  1. Alex Burlachenko 21,715 Reputation points MVP Volunteer Moderator
    2026-05-27T08:12:47.5833333+00:00

    hi Srishti Ahlawat & thanks for join me here at Q&A portal,

    deleted Databricks workspace can still leave managed resources or capacity/quota usage behind for a while, but first prove whether this is Databricks-specific or normal VM quota. Try creating the same VM SKU in the same region outside Databricks. If that fails too, request VM family quota/capacity. If it works, the Databricks workspace cleanup or workspace quota is stuck. Run these checks

    az quota list --scope /subscriptions/<sub-id>/providers/Microsoft.Compute/locations/<region> -o table

    and check Total Regional vCPUs plus the VM family Databricks is trying to use. Azure VM quota is regional and VM-family based https://learn.microsoft.com/en-us/azure/virtual-machines/quotas

    List leftover Databricks managed resources az group list --query "[?contains(name, 'databricks') || contains(name, 'managed')].{name:name, location:location}" -o table

    and inspect the managed resource group for old VMs, disks, public IPs, NAT gateway, storage, NICs or locks.

    If the old workspace is stuck in deleting, do not manually delete random managed resources unless support confirms it. Databricks managed resource groups are owned by the workspace lifecycle, and half-deleting them can make cleanup uglier.

    Create a test VM in the same region and same VM family. If VM creation gives quota/capacity error, follow the moderator advice and raise compute quota or capacity request. If VM creation works but Databricks workspace fails, open Azure Databricks support and ask for backend cleanup of the deleted workspace or managed resource group.

    Azure quota troubleshooting u can find it at https://learn.microsoft.com/en-us/azure/azure-resource-manager/troubleshooting/error-resource-quota

    Portal “quota exceeded” may be real compute quota, regional capacity, or orphaned Databricks managed resources. The VM test separates those paths fast

    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 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.