Hi @bradleyjamrozik ,
The problem is that the current designed behavior of Power BI can lead to the connection not being closed under certain conditions.
In short, since Databricks is Async, if an error occurs while fetching data, the connection may not be closed gracefully. This causes Databricks Sql Serverless to not terminate after the idle timeout is reached, even without any queries running.
Microsoft has a backlog item to improve their process of closing connections on errors. They said it is a complex change and needs to be prioritized. As of now they have no ETA confirmed by the Product Team.
This was the important part of the response I received from the Microsoft PowerBI Technical Support Team.
Until someone fixes it, Sql Serverless may keep active 24x7, for something that should be kept active when needed.