If you use Microsoft Teams every day, you’ve probably run into situations like these: you send a file in a chat and can’t find it later; you create a channel and a SharePoint folder appears from nowhere; you share a document and realise the whole team can see it. These aren’t random bugs, they’re the product of a system most people have never had explained to them properly.
Microsoft Teams connects to both SharePoint and OneDrive, and knowing how that connection works will save you from lost files, broken sharing links, and cluttered environments.
What Microsoft Teams actually is
Teams is a collaboration and communication platform, messaging, meetings, calls, file sharing, and app integrations in one interface. What it is not is a file storage system. Teams has no file storage of its own. Every file you touch in Teams lives in either SharePoint or OneDrive.
Understanding this single fact makes the rest of the system legible.
How Teams is organised: everything in Teams is structured around two levels.
A Team is a shared workspace for people who work together regularly, a department, a project group, a function. Each Team has members (who collaborate), owners (who manage settings), and optionally guests (external users with restricted access).
A Channel is a workspace inside a Team, organised around a topic, project, or workstream. Every Team gets a General channel by default. Channels have three visibility types, and each one stores its files differently:
The three channel types
-
Standard channels
Visible to all Team members. Files go into the Team’s own SharePoint site.
-
Private channels
Visible only to selected members, and they get a separate SharePoint storage area, independent of the Team’s main site.
-
Shared channels
Built for collaboration with people outside the Team, including external partners. Files live in the channel’s shared space with restricted access.
Private channels create a separate SharePoint site collection, not just a folder in the Team’s existing site. This means permissions are entirely independent, removing someone from the main Team doesn’t remove them from a private channel they were added to.
How SharePoint connects to Teams behind the scenes
When you create a new Team, Microsoft automatically creates a SharePoint site in the background. This site is the file storage layer for that Team. You may never open it directly, but every file shared in a Standard channel is stored there.
The structure works like this:
- The Team’s SharePoint site has a Documents library.
- Each Standard channel creates a folder inside that library with the same name as the channel.
- When you upload or share a file in a channel’s Files tab, you’re adding it to that folder, you’re just seeing it through the Teams interface.
This is why files shared in a Teams channel survive even if someone leaves the Team. The files aren’t attached to the person, they’re in SharePoint, owned by the Team’s site, and governed by the Team’s membership settings.
Version history and real-time co-authoring (multiple people editing the same Word or Excel document simultaneously) work because SharePoint handles the underlying storage and conflict resolution. Teams just surfaces it.
Where OneDrive fits in
OneDrive is your personal cloud storage tied to your Microsoft 365 account. It’s designed for files you’re working on individually, drafts, personal notes, documents you haven’t shared yet.
The key distinction in Teams: where you share a file determines where it’s stored.
- Upload a file in a channel → goes to the Team’s SharePoint site (shared, governed by Team membership)
- Share a file in a one-on-one or group chat → goes to your OneDrive (you remain the owner, you control the permissions)
This means a file you share in a private chat is your file, shared to those specific people. It doesn’t appear in a channel, it doesn’t follow Team membership rules, and if you leave the organisation, it’s at risk of being lost unless ownership is transferred during offboarding.
| Scenario | Where the file lives | Who controls access |
|---|---|---|
| Shared in a channel | Team’s SharePoint site | Team membership |
| Shared in a private chat | Your OneDrive | You (owner) |
| Shared in a private channel | Separate SharePoint site collection | Private channel members only |
What this means for keeping your environment clean
Most Teams environments that become messy or confusing got that way because nobody understood this structure when the environment was set up. Files end up in the wrong places, permissions become inconsistent, and channels multiply without a governing logic.
Understanding how Teams, SharePoint, and OneDrive connect gives you a foundation for making deliberate choices:
- Create channels for work that belongs to the team, not to an individual.
- Use OneDrive for personal working files and in-progress drafts.
- Review private channels regularly, they have separate permissions that can become invisible to Team owners over time.
- Check external sharing settings, especially for Standard channels where SharePoint’s default sharing settings may be more permissive than you expect.
At Sereno IT, we help businesses set up Microsoft 365 environments properly from the start, and clean up setups that have become disorganised over time. If your Teams environment feels chaotic, the fix is usually structural, not technical.
Written by
Sahaj Arrora
Part of the Sereno IT team helping growing UK businesses make confident, jargon-free technology decisions. Read more microsoft 365 guidance in our Microsoft 365 library.
