People treat OneDrive, SharePoint, and Teams as three separate places to put files. They’re really one storage platform with three doors into it. Teams files live in SharePoint. SharePoint and OneDrive run on the same document library engine. Once you see how they connect, the “where did my file go?” questions mostly answer themselves.
This guide explains what each one actually stores, how a file posted in Teams ends up in SharePoint, and a simple rule for deciding where to save things so they survive staff changes. If you manage a tenant, knowing the plumbing here saves you from a lot of confused tickets about missing files.
The one-line version of each
Start with what each product is for, before worrying about how they connect.
What each one is for
| OneDrive | Your personal work storage. Owned by you. For drafts and files only you work on. |
|---|---|
| SharePoint | Shared team storage in document libraries. Owned by a site, not a person. |
| Teams files | A view into the SharePoint site behind a team. Not separate storage. |
OneDrive is the one with an owner. SharePoint is the one a group owns. Teams is a friendlier window onto SharePoint with chat and meetings wrapped around it.
Where files really live
This is the part that clears up most of the confusion. Teams has no storage of its own. When you post a file, Teams puts it in either SharePoint or OneDrive depending on where you posted it.
- A standard channel → the file goes to the team’s SharePoint site, in a document library folder named after the channel.
- A private chat or group chat → the file goes to the sender’s OneDrive and is shared with the other people in the chat.
- A private channel → the file goes to a separate, dedicated SharePoint site provisioned just for that private channel.
This is also why a file you shared in a Teams chat can vanish for everyone else when your account is removed — it lived in your OneDrive, not in a shared site.
OneDrive vs SharePoint, side by side
They look almost identical in the browser because they use the same engine. The difference that matters is ownership and what happens when people leave.
OneDrive vs SharePoint
| Owner | OneDrive: one person | SharePoint: a site/team |
|---|---|
| Best for | OneDrive: personal drafts | SharePoint: shared, owned-by-team docs |
| Survives an account deletion? | OneDrive: at risk | SharePoint: yes, it's not tied to a person |
| Default sharing | OneDrive: private until you share | SharePoint: visible to site members |
| Underlying tech | Both: document libraries, same sync client |
The practical takeaway: a file in someone’s OneDrive depends on that someone. A file in SharePoint belongs to the team and stays put when staff change.
A simple rule for where to save things
You don’t need a policy document for this. One question handles almost every case: if this person left tomorrow, should the file leave with them?
- If yes (it’s a personal draft, a scratch file, something only you use) → OneDrive.
- If no (the team needs it regardless of who’s around) → SharePoint or a Teams channel.
Save to OneDrive when
- It's a personal draft or working copy
- Only you need it right now
- It's not part of a shared process the team depends on
- You'll move it to a team library once it's ready to share
Save to SharePoint or a Teams channel when
- The team collaborates on it
- It must survive someone leaving the company
- It's an official or shared document, not a personal copy
- Several people need consistent access without re-sharing
How sync ties them together
All three surface through the same OneDrive sync client in File Explorer, which adds to the impression that they’re one thing.
- Your OneDrive syncs under your organization name, for example OneDrive - Contoso.
- A SharePoint or Teams library you Sync or Add shortcut to OneDrive appears alongside it, often under the company name.
- The files still live in SharePoint; the client just mirrors them locally.
If that sync stalls or shows errors for any of these locations, the fixes are the same regardless of source — see how to fix OneDrive sync problems, since it’s all the one client.
Storage and quotas don’t share a single pool
Because the three feel like one system, people assume they draw from one bucket of storage. They don’t. OneDrive and SharePoint are metered separately.
- OneDrive gives each licensed user their own storage allocation, set by their plan and adjustable per user by an admin.
- SharePoint (which is what backs Teams channels) draws from a separate tenant-wide pool, plus storage allotted to individual sites.
- A Teams channel consumes the SharePoint site’s storage, not anyone’s personal OneDrive — except for files shared in chat, which land in the sender’s OneDrive and count against that person’s quota.
The practical consequence: a user can be “out of space” in their personal OneDrive while the team’s SharePoint sites have plenty, or the reverse. When someone reports a storage problem, the first question is which storage — personal OneDrive or a team site. If it’s a sync stall rather than a true quota issue, how to fix OneDrive sync problems covers the difference between a full cloud quota and a stuck client.
Governance angle for admins
Because Teams, SharePoint, and group membership are linked, decisions in one place ripple into the others. Creating a team creates a site. Deleting a team deletes the site and its files. Controlling who can spin up teams is really controlling who can spin up SharePoint sites — which is one reason to control who can create teams rather than leave it open to everyone.
The same connection matters for access reviews and external sharing: a guest added to a team can reach the channel files in SharePoint, so managing guest access in Microsoft Teams is also managing file access. Treat the three as one platform when you set policy, not as three unrelated apps.
Bottom line
OneDrive is personal, SharePoint is shared, and Teams files are just a view of SharePoint (or OneDrive, for chat files). Save personal work to OneDrive and anything the team owns to SharePoint or a channel, using the “would it leave with the person?” test. For admins, remember the plumbing connects them: a team is a SharePoint site, deleting one deletes the other, and the sync client treats all three the same. Get the storage decision right at save time and you avoid the messy migrations later.
