☕ SharePoint Tip #11 — Microsoft Teams and SharePoint: one platform, two faces

Posted on by

Good morning! Here is your 15-minute SharePoint tip for today.

Day 11 | Week 3 — Integration, Automation & Migration

Microsoft Teams and SharePoint: the full picture

Most users don’t realise how deeply Teams and SharePoint are connected. Understanding this relationship is essential for a Product Owner managing both platforms.

What happens when a Teams team is created

  1. Microsoft 365 creates a Microsoft 365 Group
  2. That group gets a SharePoint Team Site automatically
  3. Each channel in Teams gets a folder in the site’s default document library
  4. The Files tab in each channel points directly to that folder

This means every file uploaded in Teams is stored in SharePoint — there is no separate Teams file storage.

Private channels are different

Private channels are an exception: each private channel gets its own separate SharePoint site collection — not a folder in the main team site. This is important for permissions — private channel members are the only people with access to that site.

Shared channels (Teams Connect)

Shared channels allow collaboration with people outside your organisation while keeping the channel inside Teams. The SharePoint site for a shared channel also has special permissions handling — external members get access only to that specific site.

Managing Teams files from SharePoint

Site owners can manage Teams files directly in SharePoint — adding metadata columns, creating views, setting permissions — even if those users never open Teams. This is powerful for governance: your document management policies apply to Teams files automatically.

Try it today (5 minutes)

In Teams, go to any channel → Files tab → click Open in SharePoint. You’re now in the SharePoint library that powers this channel. Try adding a column — for example a "Status" choice column. Go back to Teams and look at the Files tab. The column appears there too. One library, two interfaces.

As a Product Owner

Governance decisions about Teams ARE SharePoint governance decisions. When you define naming conventions, metadata requirements, and retention policies for SharePoint, they apply to Teams files automatically. This unified model is a feature — use it to simplify your governance story.

See you tomorrow at 6:00 AM with Tip #12 — Power Automate and SharePoint workflows!