Forum Discussion
Error: SQL Endpoint Integrated Security not supported.
Hello,
I am trying to connect to a Fabric Lakehouse through the SQL Endpoint using Power BI Desktop to create a new semantic model.
For all lakehouses from the workspace, I get the following error:
I have tried this with other lakehouses from other workspaces and there it works. I do not have the same issue there.
It seems Workspace related.
User is still always the same connected (me) through Entra on Power BI Desktop.
I have only notebooks which load data into my Lakehouses.
Did anyone encountered such issue before ?
Thanks
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.
4 Replies
Hi alebet_biel,
I haven't run into that exact error myself, but the fact that it only happens with Lakehouses in a specific workspace is interesting.
Since the same account can connect to SQL Endpoints in other workspaces, I'd be looking more at the workspace or endpoint configuration than at Power BI Desktop itself.
A few things I'd try:
Clear any saved credentials for the affected SQL Endpoint in Power BI Desktop (Data Source Settings), then reconnect using an Organizational Account. Sometimes Desktop hangs on to an old auth method and throws an "Integrated Security not supported" message even though Fabric expects Entra ID authentication.
Open the SQL Endpoint directly in Fabric and make sure it's healthy and responsive. If there were any recent changes to the workspace, capacity, or Lakehouse, the endpoint metadata may not have updated correctly.
Try copying the SQL Endpoint connection details and create a fresh SQL Server connection from Power BI Desktop. Make sure you're signing in with Organizational Account and not Windows authentication.
Check whether another user with access to the same workspace can connect to the SQL Endpoint. That can quickly tell you whether this is user-specific or workspace-specific.
If possible, create a brand new Lakehouse in the same workspace and test its SQL Endpoint. If the new one works but the existing ones don't, that points more toward a workspace metadata or endpoint issue.
One other thing: do all Lakehouses in that workspace fail, or just a specific subset? If every SQL Endpoint in that workspace returns the same error while other workspaces are fine, I'd be tempted to raise a Fabric support ticket because that doesn't sound like expected behavior.
Let us know whether another user can reproduce it and whether a newly created Lakehouse in the same workspace behaves the same way. That should help narrow it down quite a bit.
Hi alebet_biel
try clearing data setting by using clear permissions
You can also check permissions in the workspace or check your VPN/Network.
Please give kudos or mark it as solution once confirmed.
Thanks for the answers.
I wasn't aware about caching the connections directly in PBI Desktop.
It did solve the issue.Best regards,
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.
