SharePoint Page Accessible in Browser but Not Loading in Microsoft Teams for Users with Read Permissions

Question

SharePoint Page Accessible in Browser but Not Loading in Microsoft Teams for Users with Read Permissions

Vinay Shivakoti 0

Hello Microsoft Team,

We are experiencing an issue with a SharePoint Online site that has been integrated into Microsoft Teams as a tab/app.

Scenario

We have created a SharePoint Policy Portal and integrated it with Microsoft Teams.
The portal contains:
- Overall Policies – intended to be accessible to all internal employees.
Department Policies – intended to be accessible only to specific department users (e.g., HR users).

Permissions

The SharePoint page has been shared with "Everyone except external users" to allow access to all internal users.

Additionally, we tested by granting a specific user Read/View permissions directly on the page/site.

Issue

Although the user has the required permissions, when they attempt to access the SharePoint page from within Microsoft Teams, the page does not load and remains on a blank/black loading screen.

The same content appears to work correctly for other users with higher permissions.

Questions

Are there any known limitations when accessing SharePoint pages embedded in Microsoft Teams with Read-only permissions?

Are there additional site, page, or Teams app permissions required beyond SharePoint Read access?

Could this behavior be related to page-level permissions, Teams caching, or SharePoint audience targeting?

What troubleshooting steps would you recommend to identify why the page is not rendering for the affected user within Teams?

Any guidance or recommendations would be greatly appreciated.

Thank you

0 comments

2 answers

Your answer

Answer 1

Henry-N 15,065 Microsoft External Staff Moderator

Hi @Vinay Shivakoti,

Thank you for posting your question in the Microsoft Q&A forum.

Regarding the issue where the SharePoint page loads in the browser but not in the Microsoft Teams app, I’d like to gather a bit more information to better understand and help identify the root cause. Could you please clarify the following:

Does this issue occur only with this specific page, or does it affect other SharePoint pages added as Teams tabs as well?
Have you checked whether the issue occurs in other teams or channels?
Could you try removing and re-adding the tab, and confirm if the issue still persists?

Thank you for your time and cooperation. While this response may not provide an immediate resolution, it helps ensure the issue is properly diagnosed and routed to the appropriate team if needed.

I appreciate your patience, and I’m here to assist further. Please feel free to share any updates or additional details.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread  

Vinay Shivakoti 0 Reputation points

2026-06-10T06:50:56.34+00:00

Hi Team,

Based on our investigation, the issue appears to be specific to accessing the SharePoint page through the Microsoft Teams application. Please find our observations below:

We have integrated only this specific SharePoint page with Microsoft Teams and are not currently using any other SharePoint pages as Teams tabs.

The issue occurs when users attempt to access the page through the Microsoft Teams desktop application. The page displays a retry/loading error and does not open successfully.

This behavior is observed even for users who have already been granted the necessary permissions to access the page.

The issue is intermittent in nature. Some users can access the page successfully at certain times, while the same users encounter the retry/loading error at other times.

When the SharePoint page is shared directly with users, they receive the access notification email and can access the page without any issues through a web browser.

The problem appears to be isolated to the Microsoft Teams application, as browser access functions as expected.

This is currently our primary concern, as users require reliable access to the SharePoint page from within Teams.

Additionally, apart from granting access through SharePoint groups and direct sharing permissions, could you please advise if there are any other recommended configurations, permission models, or Teams-specific settings that should be considered to ensure consistent access to the SharePoint page through the Teams application?

Please let us know if any additional information, logs, screenshots, or diagnostic data are required from our end for further analysis.
Henry-N 15,065 Reputation points Microsoft External Staff Moderator

2026-06-10T14:59:00.5666667+00:00
Hi @Vinay Shivakoti,

For this issue, please try reinstalling Microsoft Edge WebView2. Follow the steps below:

1/ Uninstall WebView2

Navigate to a path similar to:

C:\Program Files (x86)\Microsoft\EdgeWebView\Application\142.0.3595.94\Installer

Note: The version number (e.g., 142.0.3595.94) may differ on your system. Open the folder that matches your installed version.

Inside that folder:

Right-click the Installer folder

Select Open in Terminal

In the terminal:

Type cmd and press Enter

Then run the following command:setup.exe --uninstall --msedgewebview --system-level --verbose-logging --force-uninstall

2/ Reinstall WebView2

Download and install the latest version of Microsoft Edge WebView2 from the official link below: https://developer.microsoft.com/en-us/microsoft-edge/webview2/?form=MA13LH#download

After reinstalling, please check if the issue persists.

Thank you for your patience and understanding!
Henry-N 15,065 Reputation points Microsoft External Staff Moderator

2026-06-12T14:13:12.75+00:00

Hi @Vinay Shivakoti,

Just want to check if you have any new update on the issue feel free to share here. Thank you so much for your cooperation we truly appreciate your time and effort. Looking forward to hearing from you soon.

Answer 2

The behavior matches known limitations when loading websites (including SharePoint pages) inside the Teams Website tab, especially when Conditional Access or other web controls are involved.

Key points from known issues:

Websites may not load inside the new Teams desktop client
- A website tab in Teams can fail to load even when the same site works in a browser.
- Causes include:
  - The website disallows being embedded in other sites (X-Frame-Options / CSP, etc.).
  - Conditional Access policies are enforced for that site.
- In these cases, the Teams tab can show a blank or non‑responsive page for some users.
Conditional Access and session controls can affect SharePoint access
- If Conditional Access policies (for example, Microsoft Defender for Cloud Apps session policies) apply to the user’s session, the SharePoint session can be redirected and wrapped by session control.
- This can result in different behavior between:
  - Direct browser access (where the user may see a monitoring banner or redirected URL), and
  - Embedded access in Teams (where the same controls can prevent the page from rendering correctly).
Teams desktop vs browser differences
- When a website cannot be embedded or is blocked by Conditional Access, Microsoft guidance is to:
  - Use Open in browser from the Teams tab banner to open the SharePoint page directly in a browser, or
  - Use a dedicated app such as SharePoint Pages instead of a generic Website tab.

Answers to the specific questions based on available information:

Known limitations with read‑only permissions
- The documented limitations are not specifically about SharePoint “Read” vs “Edit” permissions, but about:
  - Websites that cannot be embedded.
  - Conditional Access policies that restrict or wrap browser sessions.
- Read‑only users can be more affected if Conditional Access or session policies are scoped differently for them than for higher‑privileged users.
Additional permissions beyond SharePoint Read
- No additional Teams‑specific permissions are documented as required beyond normal SharePoint access.
- However, Conditional Access policies (for example, requiring specific browsers, IP ranges, or device compliance) can effectively block or alter the session when accessed via Teams.
Possible causes in this scenario
- Conditional Access policies or Microsoft Defender for Cloud Apps session policies applied to the affected users, but not to higher‑permission users.
- The site or page being blocked from being embedded inside an iframe (Teams Website tab uses an embedded frame).
- Differences between Teams desktop and browser behavior for sites under Conditional Access.
Recommended troubleshooting steps
1. Compare behavior in Teams desktop vs browser
  - Have the affected user:
    - Use Open in browser from the Teams tab (if the banner appears) and confirm the page loads correctly.
    - Try Teams in a browser instead of the desktop app and check if the tab loads there.
  - If it works in a browser but not in the desktop client, this aligns with the documented Website tab limitation.
2. Check for Conditional Access / session policies
  - Verify whether Conditional Access policies are enforced for the affected users and this SharePoint site.
  - If Microsoft Defender for Cloud Apps session policies are in use, confirm whether the user’s session is being redirected/monitored.
  - If such policies are causing issues, consider:
    - Adjusting the policy scope, or
    - Using the browser instead of the Teams desktop client for that tab.
3. Use a SharePoint‑specific app instead of a generic Website tab
  - If the content is a SharePoint page, configure the tab using the SharePoint Pages app rather than a generic Website tab, as recommended.
4. Test with a different user and permission set
  - Assign another user the same Read permissions and test in Teams.
  - Temporarily grant the affected user higher permissions (if allowed) to see whether the behavior changes; if it does not, the issue is more likely Conditional Access or embedding, not SharePoint permission level.

These steps help distinguish between a pure SharePoint permission issue and a Teams/Conditional Access embedding limitation.

References: