Power BI is turning 10! Tune in for a special live episode on July 24 with behind-the-scenes stories, product evolution highlights, and a sneak peek at what’s in store for the future.
Save the dateEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
Dear all,
we have a Power BI report stored in Power BI service. This report is embedded in a SharePoint page (all plain vanilla, if additional description required, let me know). The report itself is working impeccably, also in the embedded version.
Recently when pulling up the SharePoint page with the report embedded the web part shows this error:
After some refreshs of the page, the error disappears and the report is displayed normally.
Do you have an idea about this issue?
Kind regards
Phil
Solved! Go to Solution.
Dear Hammad,
ticket was raised with Microsoft, however in parallel we checked with the internal network team, and it seems like the issue is related to some settings in DNS configuration (azure private link). I think that we will solve this issue with internal IT, hence kind of closing or marking this questions thread here as answered.
Anyhow, thank you for our input. As usual, when facing new issues, help is searched in every direction; some of which might not be leading to the solution.
Thank you again and kind regards
Phil
Hi @PhilippHof,
Thanks for reaching out to the Microsoft fabric community forum.
Based on your description, the Power BI report itself is functioning correctly, but intermittently fails to load when embedded in SharePoint, displaying a "Failed to fetch" error. The fact that refreshing the page resolves the issue suggests a temporary connectivity, authentication, or network-related issue.
You can follow these few steps to troubleshoot and resolve your issue:
* You can clear Browser Cache & Cookies and try accessing the SharePoint page in an incognito window or a
different browser to see if the issue persists.
* Verify Authentication and make sure you are properly logged into both SharePoint and Power BI. Try logging out
and back in.
If I misunderstand your needs or you still have problems on it, please feel free to let us know.
Best Regards,
Hammad.
Community Support Team
If this post helps then please mark it as a solution, so that other members find it more quickly.
Thank you.
Dear Hammad,
thank you for your reply. I've assessed the proposed options, however they didn't show any effect. In fact, we have been using the report for at least a year now, configuration unchanged, and only beginning of last week, the issue appeared with different users. Would you have another idea about the issue?
Kind regards
Phil
Hi @PhilippHof,
Thank you for following up. As the issue appeared recently without any configuration changes and is affecting multiple users, it may be due to a Microsoft service update or a change in authentication behavior.
You can follow these additional steps to look into the issue and resolve it:
* You can check Microsoft’s Service health dashboard to see if there are any ongoing incidents with
Power BI or SharePoint.
* Again add the Power BI Web Part to the SharePoint page to refresh the embedding settings.
* Mske sure Conditional Access Policies or MFA settings haven't changed, as authentication timeouts
can cause irregular failures.
* Also allow third-party cookies in your browser settings, as recent security updates may block
embedded content.
If the problem is still there, we recommend you to escalate this to Microsoft Support, as it may be related to a recent update impacting Power BI embedding.
Best Regards,
Hammad.
Community Support Team
If this post helps then please mark it as a solution, so that other members find it more quickly.
Thank you.
Hi @PhilippHof,
I wanted to follow up on our previous conversation. Has your issue been resolved or were you able to raise a support ticket with Microsoft Fabric Support?
Your feedback would be greatly appreciated, as it can help us better understand and address similar issues in the community.
Thank you.
Dear Hammad,
ticket was raised with Microsoft, however in parallel we checked with the internal network team, and it seems like the issue is related to some settings in DNS configuration (azure private link). I think that we will solve this issue with internal IT, hence kind of closing or marking this questions thread here as answered.
Anyhow, thank you for our input. As usual, when facing new issues, help is searched in every direction; some of which might not be leading to the solution.
Thank you again and kind regards
Phil