Question about using ODBC for SQL Gateway connections

I am currently experiencing frustration with trying to Authenticate an Active Directory account through JDBC as the Hospital System moves from OnPrem SQL Server to using Azure SQL Server with Microsoft Entra Authentication.

Microsoft cannot give me a straight answer of what is required from a JDBC standpoint to authenticate from a Linux environment.

I am working with WRC, but we are both struggling to find the specific answer for JDBC. If I use my local desktop and JDBC to connect through DBeaver I don't have an issue. So, I am thinking the issue is with not having a java keystore, or keys setup within Linux for this to work.

It got me thinking is that we do not have this issue with the Linux ODBC connections we use with Perl so maybe I should move to using ODBC in Intersystems as well. But we have so much code developed using the existing JDBC SQL Gateway connections, so I have some questions.

• What is the difference between using JDBC vs ODBC for SQL Gateway connections?
• How does it affect the SQL Adapters/code that is already in use if we move to ODBC from JDBC?
• Where does the ODBC.ini have to live for InterSystems to work?
  • the Documentation references the Templates in the bin directory, but those are templates. Where do I need to put the true odbc.ini that I intend to use?
• Can I use my existing Linux ODBC.ini?

Thanks

Scott