I'm trying to connect Retool Cloud to a Microsoft Fabric Lakehouse's SQL Analytics Endpoint, and I've read through two older threads that kind cover this same issue:
Both threads are a bit old, so wondering if anything changed:
Any native Fabric resource, or Entra ID / Service Principal auth for the SQL Server connector on Cloud?
JDBC driver list on Cloud is fixed (DB2, ClickHouse, Trino, Ingres, Teradata, Informix), any way to request mssql-jdbc be added?
Our setup: Fabric SQL Analytics Endpoint, only accepts Entra ID / Service Principal, no username/password. Trying to avoid building a bridge just for this if there's a more direct path now.
Thanks for reaching out, @Luan! Welcome to the community.
I don't think there have been any significant developments on either front, but was able to track down a nearly identical request that was previously logged internally. I'll update the ticket with the context you've shared here and give you an update as soon as I can!
Just to be clear, either implementation would unblock you, right? My understanding is that the JDBC connection string would natively support authentication via Entra ID / Service Principal.
Yes, either would unblock me. And you're right, our Fabric endpoint only supports Entra ID / Service Principal auth (no SQL username/password), so as long as whichever path supports that, I'm unblocked.
Glad to see an update here Darren! We’re also self-hosted and just upgraded to version 4. Fabric is our official data warehouse and right now connecting via GraphQL is a huge limitation. If we could get a SQL connection unlocked it would allow anyone in our org to use Retool’s new AI capabilities to spin up reports, and interactive data exploration on-demand. Even if it doesn’t become a “native” connector, some official documentation showing how we can do that JDBC connection instead of a user posting in a forum would be amazing.
Welcome to the community, @dchimento-bw! I've added your +1 to the internal tracking ticket.
In the meantime - because you're self-hosting - you can definitely configure a custom JDBC driver. I am sure we have documentation somewhere and will try to find it, but this is the best I can easily find.
How are you currently hosted? That would help me give specific recommendations.