Teams Error Codes

How to Fix SharePoint Page Showing 404 Error in Microsoft Teams Tab

Khadija KhanKhadija Khan Nov 3, 2026 869 views

Question details

The user needs to resolve a 404 Not Found error that appears when accessing a SharePoint page embedded as a tab in a Microsoft Teams channel.

How to Fix SharePoint Page Showing 404 Error in Microsoft Teams Tab
Product
Microsoft Teams and SharePoint
Device & OS
not provided
Scenario
Accessing a previously functional SharePoint page that has been integrated as a tab within a Microsoft Teams channel.
Observed behavior
The Teams tab displays a 404 Not Found error, even though the same SharePoint page opens and loads perfectly in a standard web browser.
Before you start

Verify that the SharePoint page is fully published and accessible to all channel members via a standard web browser to ensure the page itself has not been moved, deleted, or restricted.

Solution 1Recommended

Use a Website Tab as a Workaround

Bypass the native SharePoint tab integration by using a standard Website tab, which forces Teams to load the page URL directly exactly like a web browser.

Sometimes the native SharePoint app integration in Teams fails to sync the correct routing path after a page is updated or moved, resulting in a 404 error. Adding the page via a Website tab creates a direct link that circumvents these internal routing issues.

1
Copy the SharePoint URL

Open your web browser, navigate to the functioning SharePoint page, and copy the full URL from the address bar.

2
Add a new tab in Teams

Navigate to your Microsoft Teams channel and click the '+' (Add a tab) icon at the top of the window.

3
Select the Website app

In the app gallery, search for and select the 'Website' app instead of the 'SharePoint' app.

4
Configure and save the tab

Enter a name for the tab (e.g., 'SharePoint Portal'), paste the copied SharePoint URL into the URL field, and click 'Save'.

Use a Website Tab as a Workaround
Workaround Successful: The Website tab will require users to authenticate via their Microsoft 365 credentials the first time they view it, but it will correctly display the page content.
Free Microsoft Office alternative

Try WPS Office for Seamless Document Collaboration

While resolving Microsoft Teams and SharePoint integration issues, consider WPS Office as a lightweight, robust alternative for your daily document workflows. It provides professional tools for word processing, spreadsheets, and presentations with seamless compatibility.

  1. 1. Download and Install: Download WPS Office for free from the official website and install it on your device.
  2. 2. Open Your Office Files: Launch WPS Office and directly open any existing Microsoft Office documents without needing format conversions.
  3. 3. Edit and Save Seamlessly: Collaborate and edit your documents, saving them in standard formats like .docx or .xlsx to share with others easily.
Free, lightweight, and incredibly easy to useHigh compatibility with Microsoft Word (.docx), Excel (.xlsx), and PowerPoint (.pptx) formatsBuilt-in PDF editing, merging, and format conversion toolsCross-platform support for Windows, Mac, Linux, iOS, and Android devices
microsoft office alternative - wps office

Frequently Asked Questions

Why does my SharePoint page show a 404 error in Teams but works in the browser?

This commonly occurs due to caching issues in the Microsoft Teams desktop client, or because of sync delays between SharePoint and Teams routing after a page URL or content has been updated.

Will republishing the SharePoint page fix the Teams tab error?

Yes, sometimes making a minor edit (such as adding or modifying a web part) and republishing the SharePoint page forces Microsoft Teams to fetch the latest page structure, which can resolve the 404 error after about 30 minutes.

How do I know if the issue is with the Teams app or my Microsoft 365 tenant?

Log into the web version of Microsoft Teams via your browser. If the SharePoint tab loads correctly in the web version, the problem is isolated to your Teams desktop app's cache. If it fails in both environments, it may be a tenant-level issue requiring administrator support.