An Apache Spark-based analytics platform optimized for Azure.
Hi Maxx,
Thank you for reaching out, and I understand how this behavior can be confusing—especially since it worked in your earlier workspaces.
From what you’ve described and shared in the screenshot, the issue is not related to a platform bug but is most likely due to workspace configuration or missing permissions for cluster creation in the new workspace.
In Azure Databricks, the Compute section can show different options depending on your permissions and workspace setup. If you are being redirected only to SQL Warehouses, it typically means that classic compute (clusters) is currently not enabled for your user.
As per Microsoft guidance, creating clusters depends on:
- User entitlements (permissions)
- Assigned compute policies
If these are not configured, the UI may only display SQL warehouse options instead of cluster creation
Additionally, Microsoft documentation confirms that Databricks provides multiple compute types (serverless, classic clusters, SQL warehouses), and access to these depends on workspace setup and permissions
Please check with your Databricks Workspace Admin and request one of the following:
Option 1: Enable cluster creation entitlement
- Ask the admin to enable: “Allow unrestricted cluster creation” for your user/group
Option 2: Assign a compute policy (recommended approach)
- The admin should assign you access to a policy (for example, Personal Compute)
- After that, go to Compute → Create compute, where you should be able to select the policy and create a cluster
If no policy or entitlement is assigned, the system will continue showing only SQL Warehouses.
After these changes:
- The Compute page will display “Create compute”
You will be able to create all-purpose or job clusters as expected
Since this started happening only in new workspaces after April 24, it is very likely due to default configuration changes (especially with serverless/managed compute features) combined with missing policy or entitlement assignment.
If you still face the issue after these changes, please feel free to share a screenshot of the Admin → User entitlements / Compute policies, and I’ll be happy to assist further.
Microsoft reference links: