Forum Discussion
Error: SQL Endpoint Integrated Security not supported.
Hi alebet_biel,
The error itself gives a useful clue here:
Microsoft SQL: Integrated Security not supported.Fabric Lakehouse SQL analytics endpoints use Microsoft Entra authentication, so I would not expect Windows/Integrated authentication to be used for this connection. Microsoft documents Entra authentication for both Warehouse and Lakehouse SQL analytics endpoints.
Since the same account can connect to Lakehouses in other workspaces, I would first rule out a cached connection for this particular SQL analytics endpoint.
I would try:
- In Power BI Desktop, go to File > Options and settings > Data source settings.
- Find the entry for the affected Lakehouse SQL endpoint and choose Clear Permissions.
- Close Power BI Desktop completely and reopen it.
- Instead of manually entering the SQL server endpoint, try connecting through OneLake catalog / Get Data and select the affected Lakehouse directly.
Microsoft specifically supports Warehouse and Lakehouse SQL analytics endpoints as native Power BI sources, so you do not need to build the connection from the SQL connection string manually.
If it still fails, I would compare the actual endpoint and workspace configuration with one of the Lakehouses that works. In particular, I would check whether the affected workspace has different security/network settings, because Entra authentication for these endpoints depends on Fabric tenant/workspace configuration as well.
One other useful test would be to open the affected Lakehouse in Fabric, switch to its SQL analytics endpoint, and confirm that you can run a simple query there. If that works in the Service but Power BI Desktop still returns Integrated Security not supported, that would make the local Desktop connection/credential state much more likely than the Lakehouse itself.
I would not start by rebuilding the Lakehouse or changing notebooks, since the error is occurring at the authentication/connection layer before any of that becomes relevant.
AI-assisted drafting: AI was used to help structure and phrase this response. I reviewed and validated the technical content before posting.
Hi alebet_biel,
The error itself gives a useful clue here:
Microsoft SQL: Integrated Security not supported.Fabric Lakehouse SQL analytics endpoints use Microsoft Entra authentication, so I would not expect Windows/Integrated authentication to be used for this connection. Microsoft documents Entra authentication for both Warehouse and Lakehouse SQL analytics endpoints.
Since the same account can connect to Lakehouses in other workspaces, I would first rule out a cached connection for this particular SQL analytics endpoint.
I would try:
- In Power BI Desktop, go to File > Options and settings > Data source settings.
- Find the entry for the affected Lakehouse SQL endpoint and choose Clear Permissions.
- Close Power BI Desktop completely and reopen it.
- Instead of manually entering the SQL server endpoint, try connecting through OneLake catalog / Get Data and select the affected Lakehouse directly.
Microsoft specifically supports Warehouse and Lakehouse SQL analytics endpoints as native Power BI sources, so you do not need to build the connection from the SQL connection string manually.
If it still fails, I would compare the actual endpoint and workspace configuration with one of the Lakehouses that works. In particular, I would check whether the affected workspace has different security/network settings, because Entra authentication for these endpoints depends on Fabric tenant/workspace configuration as well.
One other useful test would be to open the affected Lakehouse in Fabric, switch to its SQL analytics endpoint, and confirm that you can run a simple query there. If that works in the Service but Power BI Desktop still returns Integrated Security not supported, that would make the local Desktop connection/credential state much more likely than the Lakehouse itself.
I would not start by rebuilding the Lakehouse or changing notebooks, since the error is occurring at the authentication/connection layer before any of that becomes relevant.
AI-assisted drafting: AI was used to help structure and phrase this response. I reviewed and validated the technical content before posting.