Sharepoint page stops loading in Teams client Tab

Occasional Contributor

I have noticed that when adding a Sharepoint page to a Team's tab the page eventually stops loading in the Teams client.


While it displays beautifully when it is first added, it seems that once the client is closed and then reopened some time later, clicking on the same page tab simply presents a blank screen.


It loads correctly in the web version of Teams though. Anyone else experienced this or have a solution?

30 Replies
Ey Greg,
Some questions here to narrow the issue:
(1) How did you add the page to the Team: using the SharePoint Tab or the Web one?
(2) The SPO page you are adding: is a modern SPO page or a classic one?
(3) What customizations do you have in the page?
It might happen that something in the page is preventing it to be displayed properly in the Teams App

Hi Juan Carlos


Thank-you for the reply and your time.

I added the pages to the channels using the Sharepoint tab. 

The pages I am adding are new pages to the best of my knowledge...i have only recently made them usign the new page- site page template provided - all web parts they use are standard eg file viewer, embed, text etc

There arent any customizations that I am aware can see the issue at this link...






Since one week, I have the same problem with Sharepoint pages. 

They first work fine on TEAMS but by now I can read them (blank page or error message) but I also cann't add a new one ! Same Error message "A problem is going on", no precisions. 


When I try to abb Sharepoint Library it's working but for pages not. I don't know why... 

I've had trouble with this as well..If the page not showing, I need to browse the SharePoint site itself then it will load in Teams..

Also there are webparts not working when the SP is added with the Sharepoint Tab, this was resolved by opening the site with the Web Tab instead, so try that!


Hopefully this integration will be better when the new "Sharepoint interface" in Teams is released!



Yes I know this solution but we work in Teams and we want guys to stay on teams and don't go to sharepoint. This solution was working really fine, I would like to know why now pages doesn't work anymore (I can't even add a new one in tab).
And It's not the sharepoint connection because add a new tab with library add-on work fine... I have no clues...

When the new "Sharepoint Interface" in Teams will be released ?

I believe it's Q1 next year..I'll check up on that!


Have you tried doing this from the web? Another user/computer?

OK thanks, I look forward to see that.

I Try from the web version and my collegue too. Nothing work.
For now the tab who doesn't work, we had a website (instead of Sharepoint pages).
Too bad for the adding elements...
Ok! Tried without issues
Please create a ticket with Microsoft!


It isn't just your experience that is broken - everyone in our tenant is experiencing the same thing.

At one time, we could add a SharePoint Page - nothing custom, taken straight from a new news-feed page right from the SharePoint team site sitting underneath the Teams team.

But now, we can no longer see that page in the tab, and we can no longer add a SharePoint news article or page using that one SharePoint add-a-tab icon.

Also, Connector method is broken, too.  Can't specify which news article or page.

Yeah, I’ve noticed this too! Pages have stopped loading, showing just a white screen one so on!
Feels better when you know they are working with doing a better experience
Not seeing this problem in my test tenant, so not sure if this is a general problem or a problem in your tenants
I’ve seen it in multiple’s not always but the experience is uneven.

We have experienced the similar issue - but it's limited to using Teams Web client on IE. It works fine while using Teams desktop client and web client on Edge and Chrome browser. 

We have a support ticket open for last three months. It's been escalated to product team but no updates on resolution and no ETA.




@Hemat Maheshwari I faced same issue in a customer's tenant.


@Juan Carlos González Martín : SPO Tab, Modern SPO Page, no customization


from MS : after analyzing correlation ID, issue seems to be with "an connection error between Teams & SPO. Teams ask informations to SPO and SPO refuses with a network error related to network port"




Still analyzing on MS support 

Anyone faced similar issue ?

We experience inconsistent behavior with SharePoint team site pages added as tabs in the Teams app, including symptoms like:


-Pages sometimes won't load in Teams tab, only displaying a blank white screen.

-Hero web part links to PDF files in team site Documents will not load.  Click the tile, nothing happens. Other Hero tiles linked to other PDFs will load successfully.

-Adding a new tab and selecting SharePoint will sometimes fail to display any pages, libraries or lists to choose. The window gets stuck with a blank white screen.

-Clicking the icon to "Go to website" launches a browser page address that begins with "" and only displays a blank white screen.



-Failures happen in the Windows Teams Desktop App and Teams Online with Internet Explorer, but not in Teams Online with Chrome.  Using Teams in Chrome eliminates the failures.  The Teams Mobile app works fine, because it sends you to the device's default browser instead of trying to render pages within the Teams App.

-Different people in different Teams in different channels are affected.  Some days are better than others.

-The pages that won't load or have problem tile links are in the Modern format.

-We had some success shortening the Hero link URLs as suggested by @Deleted in this thread: Hero Link Open in New Tab.  But not always.

-Have tried adding the Pages as Website and SharePoint tabs with no difference.

-Microsoft premier support thinks the problem is likely with our company's internal network and/or firewall settings.  Our network team is skeptical.


Definitely looking forward to any future improvements in this Teams feature.

I am having the same issue. I hope MS is still working on a solution to this bug!

I am having the same issue across all users who access via the MS Teams Desktop app. I have a SP Modern Page and an SP Modern List (no customization). The pages weren't working last week, then they worked for a few days, and now they aren't working again.  


All the tabs work as expected when accessed via the Teams Online version. 

This is why I use the website tab :)

I believe I may have figured out the reason as well as a possible work around. I ran into the same problem where the page would show and then the next day it would be blank, but then if I was playing around with other things sometimes it would come back again. I believe what is happening is you are being logged out of Sharepoint (as far as TEAMS is concerned) and then the Sharepoint Page is no longer showing because you don't have access. The workaround is to create the tab as a Website instead of a Sharepoint Page. You need to get the Link to the Sharepoint page you already created and use that link as the Website URL. It then shows the page in the tab just like when you create a Sharepoint page. The difference is that when you shutdown your computer or close Teams and it logs you out of Sharepoint, you'll get a login page within the Website Tab instead of just a blank screen. You'll need to log in again which is annoying, but at least it's intuitive for other team members and doesn't just look broken or missing.

Website Tab linked to SharePoint Page - Login required to view page.Website Tab linked to SharePoint Page - Login required to view page.


For some reason it doesn't matter if you are logged into Sharepoint through your web browser when you open Teams, nor does it matter if you log in and out on your web browser while Teams is open and then refresh. Instead there is some issue within the Teams/Sharepoint connection that seems to be causing the issue.


BTW, during testing I noticed that logging into the Website Tab made my Sharepoint Page tabs all work again, which is why I believe it's a Teams/Sharepoint connection issue.


Hopefully this helps anyone who has been having this extremely frustrating problem until Microsoft can fix their bugs.