Currently the only Authentication option for the Microsoft SQL node is a standard username and password account. I work for an enterprise and that option is the least secure option for them, so other options would be helpful.
For example the ODBC connector lists these options, or if there are other options not related to ODBC that may be more preferred in the data realm;
Voted. This is a real blocker in enterprise environments where username/password auth is disabled at the network level. As a partial workaround for Azure-hosted SQL, you can get an access token from Azure AD via an HTTP Request node (client credentials flow), then pass it in the Authorization header of a second HTTP Request against your SQL endpoint - but that only works if you expose it through an API layer. Native support for Azure AD Integrated, Windows Auth, and Managed Identity directly in the SQL node credential would be the proper fix.
