Forum Discussion
SQL Endpoint from Lakehouse is SUSPECT
Hi HarderT ,
I have suggested all the possible solutions. I recommend opening a Microsoft support ticket so they can trace the issue. To raise a support ticket for Fabric and Power BI, kindly follow the steps outlined in the following guide:
How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn
If my response has resolved your query, please mark it as the "Accepted Solution" to assist others. Additionally, a "Kudos" would be appreciated if you found my response helpful.
Thank you
Hi v-dineshya ,
thanks for the advice.
Option 1:
I dont have the option "Refresh Metadata" or connection? Do I have to have PowerBI-Admin rights for this?
Option 2:
Im admin of the workspace, so I cant be a permission problem. At least at the workspace level.
Option 3:
I tried with PowerBI Desktop and I got the following error:
Warning: Fatal error 615 occurred at May 27 2025 11:30AM. Note the error and time, and contact your system administrator. Login failed for user '<token-identified principal>'
Option 4:
That's my last resort, but it means a lot of work because we're already using Fabric productively and I'll have to change a lot of things. That's why I'm looking for a perhaps simpler solution.
Many thanks for your help!
Hi HarderT ,
Please follow below steps.
1. Use Azure Data Studio with Azure Active Directory - Universal with MFA
SSMS does not handle token refresh well, especially in Fabric/AAD contexts.
open Azure Data Studio, Try connecting using Authentication type: Azure Active Directory - Universal with MFA
Server: your-sql-endpoint-url (from Fabric Lakehouse). If it connects and shows your tables, the issue is SSMS specific.
2. Manually Refresh SQL Endpoint Metadata (with Admin Rights)
You mentioned not seeing the “Refresh Metadata” option this might be restricted to Fabric Admins or require certain roles.
Try this workaround to fix:
Go to Fabric > Lakehouse, From the Lakehouse Explorer panel, create a dummy table or modify a schema slightly
(e.g create/drop a test table). This sometimes forces a metadata refresh under the hood, similar to how auto-refresh gets triggered in dataflows. Then try reconnecting via SSMS or Power BI Desktop.
If my response has resolved your query, please mark it as the "Accepted Solution" to assist others. Additionally, a "Kudos" would be appreciated if you found my response helpful.
Thank you
Hi HarderT ,
We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet.do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.
Thank you.
Hi v-dineshya ,
we are trying all your steps, but none of them works.
We have recreated everything, but now we have the problem that when we create a new semantic model and change the connection in the Powerbi report, it creates a new report and does not overwrite the old one.
Hi HarderT ,
I have suggested all the possible solutions. I recommend opening a Microsoft support ticket so they can trace the issue. To raise a support ticket for Fabric and Power BI, kindly follow the steps outlined in the following guide:
How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn
If my response has resolved your query, please mark it as the "Accepted Solution" to assist others. Additionally, a "Kudos" would be appreciated if you found my response helpful.
Thank you