Explore discussions on Databricks administration, deployment strategies, and architectural best practices. Connect with administrators and architects to optimize your Databricks environment for performance, scalability, and security.
The feature should actually be implemented to allow usage of serverless instead to restrict usage of serverless. The default should be not allowed. Outside of this, admins have a clear control on how compute can be used using the compute policies. If we don't assign a policy to a user, he/she can't use any compute. With serverless default, it has bypassed everything like other users have mentioned.
The feature should actually be implemented to allow usage of Serverless instead to restrict usage of serverless. The default should be not allowed. Outside of this, admins have a clear control on how compute can be used using the compute policies. If we don't assign a policy to a user, he/she can't use any compute. With Serverless default, it has bypassed everything like other users have mentioned.
We are in the same situation, users use Serverless without noticing as it starts as the default cluster, we have set a daily alert and reach the user to educate them, but it's a tricky move from Databricks, not cool.