Forum Discussion
Service report embedded in SharePoint occasionally shows error message
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,
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