Lakehouse: ODBC error when runnning queries (error to authenticate)

Hi, 

Error appears after submitting multiple queries to a Lakesahouse SQL Endpoint using an ODBC. Time that does take error to appear might change and not relies on the amount of time required to execute the queries. The relevant factor is the amount of queries executed. Error only appears when many queries (even if they are simpler ones) are executed.

After reading this blog

https://techcommunity.microsoft.com/t5/sql-server-blog/all-about-sql-drivers-and-access-tokens/ba-p/4004499

I quickly recognized our problem when it describes " we get support escalations related to failures around expired access tokens when using Microsoft Entra ID (formerly Azure Active Directory) authentication. "

This is exactly what is going on here. Multiple queries are executed through an ODBC (using authentications based on Service Principals-tokes) which for some reason is trying to use a connection that is already closed.. This leads to the error message shown above

Would be possible to escalate the issue? It sounds a bug to me

ODBC: Connection pooling in ODBC is handled by the ODBC driver manager, which is what is responsible for loading the correct ODBC driver requested by the application. The ODBC driver manager signals an ODBC driver when a connection is going into and out of the connection pool, so the ODBC driver for SQL Server knows when to set the RESETCONNECTION status. At the same time, it also knows if it needs to obtain a new access token and open a new connection on this event.