Hi @Nid-cbs,

Thanks for the extra detail. Since this is on Azure and you’re seeing the same behaviour after multiple retries and even after resizing, it sounds less like a one-off startup delay and more like an environmental issue.

I can’t say for certain that the trial status is the cause, but it’s reasonable to check. On Azure, there may be required setup steps for serverless SQL warehouses in supported regions, and for classic or pro SQL warehouses, there must be sufficient Azure vCPU quota available. 

Since this is a 14-day Azure trial workspace and the issue is happening consistently, I’d suggest opening a support ticket through your Azure / Databricks support path if you have that available, because they’ll be able to confirm whether this is related to workspace state, serverless eligibility, quota, or another backend provisioning issue. From what you described, it doesn’t sound like you need to make any obvious manual pricing-tier change to get a Starter Warehouse past Starting.

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