Currently, when using ADAL, we request the access token and attach it to the connection object, so we are required to include ADAL4J or ADAL (pylib) in every platform as an additional lib and request token. When moving to MSAL, is it possible to merge the access token request to the JDBC driver?

Replace "Access Token" param with 3 additional parameters:
.option("TenantID","")
.option("ClientID","")
.option("ClientSecret/Cert","KeyVaultKey/plain secret")

Add a new "ClientCredential" or "ServicePrincipalWithCert" and "ServicePrincipalWithSecret" authentication type.

Particularly, in databricks/spark platforms, when we create external table references to Azure SQL, since the driver does not service principal auth, we are forced to resort to SQL Auth.

This SQL connector from MS stable for apache spark, relies on the MSSQL JDBC driver.

CREATE TABLE $tableName
USING com.microsoft.sqlserver.jdbc.spark
OPTIONS (
url "jdbc:sqlserver://$url",
databaseName "$databaseName",
dbtable "$tableName",
user "$user",
password "$password",
loginTimeout "240"
)