Hi @jakobhaggstrom, this error likely occurs due to the type of secret you're using. For M2M authentication, the Databricks JDBC driver requires a Databricks generated OAuth secret, not a Microsoft Entra ID client secret. While your service principal credentials may work with other tools like dbt, JDBC connections will fail if the wrong secret type is provided.

Try switching to a Databricks OAuth secret and see if that resolves the issue.