Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and more.
Get startedGrow your Fabric skills and prepare for the DP-600 certification exam by completing the latest Microsoft Fabric challenge.
Hi all -- I hope someone can help with this unusual error!
We are embedding Power BI reports in an iframe within an portal hosted by azurewebsites.net and accessed by Azure AD.
I can upload, view, and refresh the reports within the Power BI Service, however when I access the report via the portal I receive an error:
Couldn't load the model schema associated with this report. Make sure you have a connection to the server, and try again.
Underlying Error: Impersonation is not supported for SSO enabled models.
I've tried searching for this error with no luck -- can anyone help me with what's going on here?
Thanks!!!
Solved! Go to Solution.
Hi @cwmichael
For the connection in your Power BI Report, it is currently set to enabled SSO (Single Sign On), make sure to remove the tick marks as shown below.
The reason that it is happening is because it is trying to use Single Sign On to authenticate and that is why it is failing.
during the last 48 hours i got either the following error - i have model which in use as embedding Power BI reports, with RLS :
ObjectdetailedMessage: "Couldn't load the model schema associated with this report. Make sure you have a connection to the server, and try again."errorCode: undefinedlevel: 6message: "ExplorationContainer_FailedToLoadModel_DefaultDetails"technicalDetails: errorInfo: Array(15)0: {key: 'Underlying Error', value: 'Impersonation is not supported for SSO enabled models.'}1: {key: 'Activity ID', value:
Great, that solved it -- thank you Gilbert!
Hi @cwmichael
For the connection in your Power BI Report, it is currently set to enabled SSO (Single Sign On), make sure to remove the tick marks as shown below.
The reason that it is happening is because it is trying to use Single Sign On to authenticate and that is why it is failing.
What if I cannot find this SSO setting?
I don't see SSO option either. How did you resolve your issue?
We finally got it to work by using older version of report and by changing workspace permission to MEMBER for service principal