Ashwin_DSA
Databricks Employee
Databricks Employee

Hi @jduran9987,

 
The "no longer eligible for Serverless Compute" error from the CLI, combined with only Pro and Classic showing in the UI, points to an account-level enablement issue rather than anything wrong with your workspace configuration.
 
On AWS, serverless is enabled by default in most accounts, but accounts created through certain channels (such as the AWS Marketplace free trial path) may end up in a state where serverless is never enabled at the account level, even after upgrading to a paid Premium plan. The Set up serverless SQL warehouses docs note that serverless requires the account to not be on a free trial, and that accounts with a "granted postponement" inherit that restriction across all workspaces. Without account-level enablement, no workspace under that account can offer the Serverless warehouse type, which is exactly the behaviour you are seeing.
 
Unfortunately, there's no self-service fix for this. You'll need to open a support ticket (or reach out to your Databricks account team) with your account ID and workspace IDs, and mention the CLI error message you received. The backend team can enable the feature for your account directly, and the resolution is typically quick once it reaches the right team.
 

If this answer resolves your question, could you mark it as “Accept as Solution”? That helps other users quickly find the correct fix.

Regards,
Ashwin | Delivery Solution Architect @ Databricks
Helping you build and scale the Data Intelligence Platform.
***Opinions are my own***

View solution in original post