You're viewing content from https://.... Make sure you trust this site before using it. If the site doesn’t load properly, open it in a browser.

The following is the answer I got back from Microsoft:

The Website tab is not a supported mechanism for integrating content into Teams. The Website tab has always been a best effort mechanism and we cannot guarantee that the content embedded in it will work as expected. If the content doesn't work, then customers should click on the "Open in browser" button in the warning header to launch the pinned URL in their default browser where it should work as expected: From a technical perspective, the Electron webview that we used to embed websites into the Classic Teams Client has been deprecated and we have switched to using a vanilla iframe in the New Teams Client. That means a number of sites that worked in the Classic Teams Client will no longer work in the New Teams Client. Customers should use dedicated apps from the Store to embed the content where available or load the sites in their browser if no app is available.

If this is true; this would take the only good thing about the teams environment away. I am using it to show document libraries are a certain level (as in a few folders deep rather than at the root folder), and no app will achieve this unless I am missing something!

Same; update would be great! It's very annoying. I've spent four hours today trying to figure this out. Thanks!

That will work until they stop supporting the old Teams . . .

My impression is that the New Teams is less about new functionality than it is about cleaning up the code base so that it runs smaller and faster. Teams has been a massive resource hog, and hopefully this will make it run better, especially on older hardware. And, if it holds true to Microsoft's longtime pattern, odd releases will be full of bugs, which will be cleaned up in even releases, to be replaced by new bugs in the next odd release.

I solved this problem by switching back to the old Teams. I didn't think my organization would let me do that, but apparently I could. And since as far as I could tell there was no new functionality in the new Teams, it's a win!

Any updates on this, I'm having the same issue.

Update: Actually this is only happening in the New Teams. Reverting to old teams fixed my issue, but many of our users on are on New Teams.