Sharepoint Embedded Paginated Report "Sign In" button does not work

[keith_smith1]

Hello,

I am trying to embed "PowerBI Report Builder" Paginated reports in Sharepoint. 

If a Sharepoint user loads a page with an embedded paginated report, they see the following message: 

Clicking "Sign In" opens a new tab where the typical Microsoft login occurs. The new tab closes and nothing happens. Clicking "Open in new tab" results in the report opening properly in a new tab. Reloading the page after the login has occurred does not resolve the issue. Other users report nothing happens at all when they click "Sign in". Issue is happening on Microsoft Edge. 

EDIT: Embedding reports in Sharepoint seemed to be working fine previously and this issue suddenly popped up for one reason or another.

[keith_smith1 · Accepted solution]

@v-prasare @burakkaragoz @andrewsommer Per Microsoft tech support, embedding PowerBI Report Builder reports (rdl) in Sharepoint is not supported.

It works fine for one customer, doesn't work for the other! 

[v-prasare]

Hi @keith_smith1,

Thanks for confirming that you have raised a support ticket for this issue. kindly let us know if there is any update on this ticket from support team. If, yes can you please post your steps below and accept it as answer this will help other commmunity members find answers for similar issues quickly.

Thanks,

Prashanth Are

[keith_smith1 · Accepted solution]

@v-prasare @burakkaragoz @andrewsommer Per Microsoft tech support, embedding PowerBI Report Builder reports (rdl) in Sharepoint is not supported.

It works fine for one customer, doesn't work for the other! 

[burakkaragoz]

Hi @keith_smith1 ,

The problem you are experiencing with the “Sign In” button not working in Power BI Paginated reports embedded in SharePoint has been reported by some users recently. You can try the following solutions:

1. Browser and Session Issues
If this problem occurs in the Microsoft Edge browser, first try clearing cookies and site data.
Blocking third-party cookies can interfere with the login process. Try disabling this feature in the browser settings.
Alternatively, test in a different browser such as Google Chrome or Firefox.

2. Power BI and SharePoint Session Incompatibility
Make sure that users are logged in to SharePoint and Power BI with the same account.
After clicking the “Sign In” button and logging in to a new tab, the SharePoint page should be refreshed manually. Automatic redirection sometimes does not work.

3. Update the Embed Code
The method used to create the embed code may have changed. Try to regenerate the embed code via Power BI Service and add it to the SharePoint page again.
Especially if a different method such as “Publish to web” is used instead of the “Secure Embed” method, such problems may occur.

4. Temporary Problem on Microsoft Side
Such issues can sometimes be caused by updates made by Microsoft. Check the Microsoft 365 Service Health Dashboard to see if there is an outage or issue.

[keith_smith1]

@burakkaragoz Thank you for your response. Unfortunately the problem persists!

[burakkaragoz]

Hi @keith_smith1 ,

Thanks for the update, and sorry to hear the issue is still unresolved.

Since the usual fixes didn’t help, here are a few additional steps you might try:

1. Check Browser Console Logs
   Open the browser’s developer tools (F12) and check the Console and Network tabs when clicking the "Sign In" button. Any errors there might give clues (e.g., CORS issues, blocked scripts, auth redirects).

2. Use Incognito/Private Mode
   Sometimes extensions or cached sessions interfere. Try accessing the SharePoint page in an incognito/private window.

3. Test with a Different Network or VPN
   If your organization uses a proxy, firewall, or VPN, try accessing from a different network to rule out network-level blocks.

4. Check Azure AD Conditional Access Policies
   If your tenant has Conditional Access policies, they might be blocking embedded authentication flows. Your IT admin can check this in Azure AD > Security > Conditional Access.

5. Try Embedding via Power BI App Web Part
   If you're using a standard embed code, consider switching to the Power BI web part in SharePoint Online, which is designed for better integration and authentication handling.

Let me know if any of these help—or if you can share any console error messages, I’d be happy to help interpret them!

[keith_smith1 · Accepted solution]

@burakkaragoz @v-prasare @andrewsommer 

I was able to solve this issue by adding the "sandbox" tag to the iframe. Now it is working as expected.

[keith_smith1]

@burakkaragoz thank you for more suggestions.

Regarding using the PowerBI Web Part I believe this is only compatible with PowerBI Reports and not Paginated reports. 

The console logs have a few things that may be worth investigating.

https://login.microsoftonline.com/organizations/oauth2/v2.0/token

Failed to load resource: the server responded with a status of 400 ()

<Error generated from Report URL>

https://res-1.cdn.office.net/files/odsp-web-prod_2025-04-25.001/spappbarwebpack/spappbarwebpack.js was preloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an appropriate `as` value and it is preloaded intentionally.

I will continue testing further and have created a Support ticket for this issue.

[andrewsommer]

When you embed a Paginated Report into SharePoint Online (e.g., via iframe or Power BI web part), the authentication to Power BI Service must complete within the same browser context (iframe + session + token chain).
What you're seeing is:

• Clicking "Sign in" inside the embedded report triggers a popup-based login (modern auth).
• The popup authenticates the user and closes, but:
• The parent page fails to detect that authentication completed, due to:
• Blocked third-party cookies, or
• SameSite cookie restrictions, or
• Cross-origin iframe sandboxing, or
• Recent Microsoft identity flow update (April–May 2025 updates hardened this).
• Result: The iframe can’t reuse the token, and reloading doesn't help.

Recommended Fixes

1. Enable Third-Party Cookies: Edge and Chrome have started enforcing third-party cookie restrictions that block Power BI iframe auth tokens.

In Edge:

• Go to edge://settings/content/cookies
• Allow all cookies
• Or, add an exception for https://app.powerbi.com and your SharePoint domain

1. Add Trusted Sites in Edge

Ensure both Power BI and SharePoint domains are in trusted sites:

• Open Internet Options > Security > Trusted Sites > Sites
• Add:
• https://*.powerbi.com
• https://*.microsoftonline.com
• https://*.sharepoint.com

This helps the Microsoft Identity Platform maintain session integrity across domains.

1. Enable "Allow Authentication Context" in SharePoint Embed

If embedding via iframe manually (i.e., not Power BI web part), ensure:

<iframe
  src="https://app.powerbi.com/reportEmbed?reportId=...&..."
  sandbox="allow-scripts allow-same-origin allow-forms allow-popups allow-popups-to-escape-sandbox"
  allow="fullscreen"
></iframe>

Please mark this post as a solution if it helps you. Appreciate Kudos.

[keith_smith1]

@andrewsommer Thank you for your suggestions.

I have:

1. Added cookie exceptions for app.powerbi.com and our sharepoint site.
   • I can see I have two cookies from paginated-reports.powerbi.com 
2. Added Trusted Sites you listed
3. Updated my iFrame to include the details you listed

Unfortunately the issue persists!