SharePoint to Teams: Quick Connect Guide

Key insights

• New SharePoint-first flow: Microsoft moved the connector into the updated SharePoint experience so you now start on the SharePoint team site and use Add real-time chat to create a linked Microsoft Teams workspace.
  Functionality is the same; only the access point changed.
• Who can do it: The flow works on a group-connected team site and must be run by the site owner.
  If the site isn’t connected to a Microsoft 365 group, you must connect it first.
• Step-by-step action: Open the team site → choose Add real-time chat → pick Add Microsoft Teams → select which SharePoint resources to surface as tabs → confirm Add Teams.
  Selected resources appear as tabs in the Teams General channel and a Teams link is added to the site navigation.
• What can surface in Teams: You can add SharePoint pages, news posts, lists, and document libraries as tabs so teams work from the same content without copying it.
• Why it helps: The integration reduces content duplication and keeps collaboration anchored to the SharePoint site while adding chat, meetings, and collaboration features in Teams.
  This preserves existing site structure and makes content easier to find and use in one place.
• Important distinction: This process creates a Team from a SharePoint team site (a guided, site-owner workflow) and is not the same as simply adding a SharePoint page as a tab inside an existing Teams channel.

Video summary and context

Ami Diamond [MVP], a male Microsoft MVP, published a short YouTube video that demonstrates how to connect a SharePoint team site to Microsoft Teams. The clip focuses on a recent relocation of the command in the updated SharePoint experience and explains which site types can be connected. Consequently, the video helps site owners who cannot find the option after Microsoft moved it in the interface. Moreover, the demonstration emphasizes that the underlying functionality has not changed even though the navigation has.

What changed and where to look

Diamond explains that the option to connect a team site to Teams now appears on the SharePoint site itself, using the Add real-time chat entry point from the SharePoint home page or the Next Steps panel. In other words, administrators no longer have to start in the Teams app to create a team from an existing site. However, this change can produce confusion because the workflow moved from Teams to SharePoint, and many users will need short guidance to find the new placement. Therefore, the video’s short walkthrough aims to reduce that confusion by showing the exact clicks and confirming who can perform the action.

How the connection flow works in practice

In the video, Ami Diamond walks through the owner experience: open the SharePoint team site, choose Add real-time chat, select Add Microsoft Teams, review the options to add SharePoint content as Teams tabs, and then confirm to create the team. As a result, the selected SharePoint pages, news posts, lists, and document libraries appear as tabs in the General channel, and Teams links are added to the SharePoint navigation. This SharePoint-first flow therefore creates a Teams workspace that is tightly linked to existing site content, so teams can chat and meet without duplicating documents or pages. Additionally, Diamond highlights that the process is presented as a guided, site-owner workflow, which simplifies setup for non-admin owners.

Content surfaced and technical requirements

Diamond clarifies that the content types you can surface as tabs include SharePoint pages, news posts, lists, and document libraries, so teams can keep working from their existing site structure. Importantly, Microsoft 365’s guidance requires the site to be a group-connected team site and the person initiating the connection to be the site owner; if the site lacks a Microsoft 365 group, it must be connected to one first. Consequently, tenants whose sites are not group-connected will need an extra step, and IT policies that restrict group creation or site ownership may block the workflow. Thus, administrators should verify group settings and ownership rights when planning rollout to avoid friction.

Tradeoffs, governance, and challenges

While the SharePoint-first approach reduces content duplication and preserves site structure, it introduces governance tradeoffs that organizations must weigh carefully. On one hand, allowing site owners to create Teams from existing SharePoint sites speeds collaboration and keeps content anchored, but on the other hand, it can complicate lifecycle management if many site owners create Teams without coordination. Moreover, tenant-level controls about who can create Microsoft 365 groups or Teams may prevent the workflow, which requires either clearer delegation or additional admin steps. Therefore, teams should balance agility with oversight by defining who can initiate the connection and by auditing created Teams for naming and retention compliance.

Practical advice and next steps

Diamond’s video is pragmatic: he not only shows the new location but also points out the difference between creating a Teams environment from a site and simply adding a SharePoint page as a tab in an existing channel. Consequently, organizations should decide whether they need a full Teams workspace connected to a site or merely a tab to surface a single page or library. For practical rollout, it helps to prepare short internal guidance, align group creation policies, and train site owners about the required preconditions, so the feature delivers clear benefits without creating governance gaps. Finally, the clip serves as a useful quick reference for anyone who has noticed the move and wants to understand the supported patterns and limits.

Keywords

Connect SharePoint to Microsoft Teams, Add SharePoint Team Site to Teams, SharePoint Teams integration guide, Link SharePoint site with Teams, Sync SharePoint files to Teams, Modern SharePoint Team Site Teams connection, Microsoft Teams SharePoint connector, SharePoint Team Site Teams tutorial