Microsoft Teams + SharePoint Integration: Complete Guide for IT Administrators

# Microsoft Teams + SharePoint Integration: Complete Guide for IT Administrators

Microsoft Teams and SharePoint are deeply integrated in Microsoft 365 — understanding the relationship between them is essential for any IT administrator managing the modern workplace. Teams without SharePoint knowledge leads to governance gaps; SharePoint knowledge without Teams context misses how users actually work.

---

How Teams Uses SharePoint Behind the Scenes

Every Microsoft Teams team has a corresponding SharePoint site that stores all files shared in the team. This isn't optional — it's architectural.

The Teams-SharePoint Relationship

```

Teams Team: "Project Phoenix"

↕ (automatically created)

Microsoft 365 Group: "Project Phoenix"

↕ (automatically creates)

SharePoint Team Site: /sites/ProjectPhoenix

├── Documents (General channel files)

├── [Channel Name] (each channel gets a folder)

├── [Channel Name 2]

└── Private Channels → Separate SharePoint site collection

```

Key facts:

• Standard channels store files in folders within the team's SharePoint site
• Private channels get their own dedicated SharePoint site collection (separate from the main team site)
• Shared channels also get their own SharePoint site
• Deleting a Teams team archives (but does not immediately delete) the SharePoint site

What Lives Where

| Content | Location |

|---------|---------|

| Files shared in Teams channels | SharePoint team site Document library |

| Channel posts (conversations) | Teams data store (not SharePoint) |

| Meeting recordings (after Sept 2023) | OneDrive (organizer's) or SharePoint (channel meetings) |

| Wiki content | SharePoint pages or OneNote (depending on settings) |

| Tabs content | Varies by tab type |

| Team membership | Microsoft 365 Group |

---

Permissions: The Relationship That Trips Everyone Up

Standard Channel Permissions

Teams membership controls SharePoint permissions automatically:

| Teams Role | SharePoint Permission |

|-----------|----------------------|

| Team Owner | Site Owner (Full Control) |

| Team Member | Site Member (Edit) |

| Guest | Site Member (Edit, limited) |

Important: Adding someone to a Teams channel automatically adds them to the SharePoint site with Edit permissions. This is a common source of unintended SharePoint access in over-permissioned environments.

Private Channel Permissions

Private channels are the most complex Teams/SharePoint permission scenario:

• Private channel members get access ONLY to that channel's SharePoint site
• They do NOT get access to the parent team's SharePoint site
• This isolation is by design — it's what makes channels "private"
• Managing private channel memberships requires careful planning to avoid fragmentation

Guest Access Across Teams and SharePoint

When guests are added to Teams:

• They become Azure AD guest accounts
• They get SharePoint access based on their Teams membership level
• They can access files via Teams AND via direct SharePoint URL
• Their access is governed by your Azure AD B2B settings

---

Best Practices: Governing Teams Through SharePoint

1. Consistent Naming Between Teams and SharePoint

Teams provisioning creates SharePoint sites with auto-generated URLs based on the team name. Long team names create long URLs that can break SharePoint's 400-character path limit.

Recommendation: Implement Teams provisioning governance that:

• Enforces a naming convention at Teams creation
• Sets SharePoint URL (alias) at creation time (cannot be changed after)
• Adds required columns to the SharePoint site template

2. Information Architecture: Teams vs SharePoint Sites

Not all content belongs in Teams. A common governance mistake is using Teams for everything, which fragments content across hundreds of team-scoped SharePoint sites with no cross-search.

Use Teams for:

• Project collaboration with a defined team
• Ongoing department communication
• Time-limited workstreams

Use SharePoint (not Teams) for:

• Company-wide intranet content (policies, procedures, announcements)
• Document repositories accessed by large audiences
• Formal records that need structured governance
• Content requiring fine-grained permissions Teams doesn't support

3. File Management Principles in Teams

Common Teams file management anti-patterns:

Anti-pattern: Everything in the General channel

Result: General channel becomes a filing cabinet with thousands of files and no structure.

Better approach: Create channels by project phase or topic, each with its own organized files.

Anti-pattern: Using Teams for formal records

Result: Compliance records stored in Teams with no retention policy, accessible to entire team.

Better approach: Use SharePoint with retention policies for formal records; link from Teams tab.

---

Connecting SharePoint Content to Teams: Tab Types

Bring SharePoint content into Teams channels using tabs:

SharePoint Page Tab

Add any SharePoint page as a Teams channel tab:

• Teams channel → + (Add a tab) → SharePoint
• Select any page or library from connected site
• Users can interact with SharePoint content without leaving Teams

Document Library Tab

Show a specific SharePoint library in Teams:

• Teams channel → + → Document Library
• Select site and library
• Users see the full document library with all metadata and actions

Power Apps Tab

Embed a Power Apps form or app:

• Teams channel → + → Power Apps
• Select app from your Power Platform environment
• Users submit forms, view dashboards without leaving Teams

Viva Connections Tab (Intranet in Teams)

Bring your SharePoint intranet into Teams:

• Viva Connections home experience configured in SharePoint
• Added to Teams as pinned left-rail app
• Users access intranet news, quick links, and tools from Teams

---

Teams Meeting Recordings and SharePoint

Since September 2023, Teams meeting recordings are stored in OneDrive or SharePoint:

• Non-channel meetings: Stored in organizer's OneDrive (My Recordings folder)
• Channel meetings: Stored in the channel's SharePoint site (Recordings folder)

Managing Recording Storage

Set expiration policies:

All Teams recordings expire by default (company policy can override). Configure in Microsoft Teams Admin Center → Meetings → Meeting policies → Recording expiration.

Move recordings to SharePoint:

For recordings that should be retained long-term (training sessions, all-hands, board meetings):

• User downloads from OneDrive/Teams
• Uploads to designated SharePoint library with proper metadata
• Apply retention label for long-term retention

Storage cost consideration:

Recordings are large (1 hour ≈ 400MB). 500 users with 3 meetings/week = significant OneDrive storage consumption. Monitor via SharePoint Admin Center → Reports → OneDrive files.

---

Search Across Teams and SharePoint

Microsoft Search indexes content from both Teams and SharePoint, but there are nuances:

What's searchable from Microsoft Search:

• Files in SharePoint (including Team-attached SharePoint sites)
• Teams messages (conversations — shown separately from documents)
• Meeting recordings (if stored in SharePoint/OneDrive)
• Wiki pages (converted to SharePoint pages)

What's NOT searchable globally:

• Private channel files (only visible to private channel members)
• Files from external tenants in Teams Connect channels

Improving search for Teams/SharePoint:

• Add descriptive metadata to SharePoint columns (searchable as refiners)
• Ensure Teams naming conventions help users find teams in search
• Configure promoted results for frequently searched content

---

Lifecycle Management: Teams Archiving and SharePoint

When a Teams team is no longer active, what happens to the SharePoint site?

Teams Archive vs Delete

Archive a Teams team:

• Team becomes read-only in Teams (no new messages)
• SharePoint site remains ACTIVE and accessible
• Team can be unarchived
• Best for: Completed projects where content must remain accessible

Delete a Teams team:

• Team is removed from Teams
• Microsoft 365 Group is soft-deleted (30-day recovery window)
• SharePoint site goes to SharePoint Recycle Bin (93-day recovery)
• After 93 days: Content permanently deleted unless retention policy applies

Lifecycle Policy Recommendations

For regulated industries, implement:

• Teams expiration policy (Azure AD Groups): Teams expire after 1 year of inactivity
• Renewal notification: Team owners notified 30 days before expiration
• SharePoint retention policy: Apply to Team-connected sites based on content type

---

Troubleshooting Common Teams/SharePoint Issues

"I can't see files in Teams"

Usually caused by: Permissions mismatch between Teams membership and SharePoint permissions.

Fix: Check if user is a Team member; check SharePoint site permissions; verify no unique permissions on the Documents library.

"Files shared in Teams don't appear in SharePoint"

Usually caused by: Wrong SharePoint site selected in Teams tab configuration.

Fix: Verify Teams channel → Files tab → "Open in SharePoint" points to correct site.

"Private channel members can see all team files"

Cause: User was also added as a Team member (not just private channel).

Fix: Remove from Team, keep only as private channel member.

"Teams search doesn't find SharePoint files"

Usually caused by: Files in sites not indexed yet, or user doesn't have permissions.

Fix: Wait for crawl (new content: 15 minutes; permission changes: up to 24 hours). Verify user has at least Read permission on the SharePoint site.

---

Need Help Managing Your Teams + SharePoint Environment?

Most organizations have accumulated governance debt across Teams and SharePoint that creates compliance risks and user productivity issues. Our team specializes in Teams/SharePoint governance assessments and remediation.

[Schedule a free Teams governance assessment →](/services/sharepoint-consulting)

Or explore our [SharePoint Support Plans](/services/sharepoint-support) for ongoing Teams and SharePoint management.