- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-05-2026 07:06 AM
Is there a way to create multiple serverless compute instances in a Databricks workspace?
I have a use case where multiple all-purpose clusters are allocated to different user groups. I want to replace these all-purpose clusters with serverless compute. Is it possible to allocate or logically separate serverless compute for different user groups?
Additionally, is it possible to limit or control serverless compute usage per user group or workspace?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-05-2026 07:30 AM
Not really. There isn’t an admin-managed concept like “Serverless Cluster A for Team A” and “Serverless Cluster B for Team B” for notebooks/jobs serverless.
Serverless compute is described as Databricks-managed on-demand resources where Databricks “automatically allocates and manages the necessary compute resources” instead of you provisioning/creating clusters.
If it is for cost tracking. Databricks provides Serverless budget policies (public preview) that apply tags to serverless activity for users/groups assigned to those policies. Those tags then appear in billing records, enabling chargeback/showback by team/cost center.
https://docs.databricks.com/aws/en/admin/usage/budget-policies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-05-2026 09:40 AM
I want limit or control serverless compute usage per user group? Is there any way to do that?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-05-2026 09:56 AM
No — Databricks does not currently offer a native way to set hard quotas or throttles on serverless compute per user group (for example, “Team A is limited to X DBUs/hour on serverless notebooks”). Serverless compute is intentionally a shared, autoscaling service managed by Databricks.
What is available today are governance and cost‑control mechanisms, not hard enforcement.
Some recommended best practices around serverless are:
Serverless budget policies for per‑group attribution and monitoring
Budget alerts + reporting (FinOps dashboards, system tables)
