You go to save a file in Microsoft 365 and the same small panic shows up. OneDrive? The Teams channel you were just in? Some SharePoint site? They all look like folders, they all sync, and they all seem to work. So people pick whichever one is closest and move on.
That’s how an organization ends up with the real document buried in one person’s OneDrive, three slightly different copies in three Teams channels, and a SharePoint site nobody opens. The tools aren’t the problem. Nobody ever drew the line between them.
Here’s the line.
OneDrive: the drawer in your desk
OneDrive is your personal space in Microsoft 365. By default, nobody else can see what’s in it. That’s the whole point of it, and also where it goes wrong.
It’s the right home for a draft you’re still shaping, a meeting note only you need, a copy of your expense receipts. The moment you start sharing OneDrive files with the team, though, you’ve quietly made yourself a single point of failure. When you’re on vacation, or you leave, that “shared” file is locked in a personal account IT now has to go dig out.
A file that the business depends on should never live in one person’s OneDrive. When that person leaves, the file leaves with them.
So use OneDrive for work that is genuinely yours and temporary. The test is simple: would it matter if this file vanished when you left the company? If yes, it belongs somewhere the org owns.
SharePoint: the shared filing cabinet
SharePoint is where files the organization owns are supposed to live. A department’s documents, a policy library, the project folder five people touch. It doesn’t belong to a person, it belongs to a site, and the site has owners who can hand access to the next person without anyone losing the file.
This is also where the grown-up controls live: who can see what, version history, retention rules, and the structure that keeps things findable a year later. Most of the “Microsoft 365 is a mess” complaints I hear are really just SharePoint that was never set up with any structure, so people gave up and retreated to OneDrive and email attachments.
Teams: the front door, not a fourth filing system
This is the part that trips everyone up, so it’s worth saying plainly: Teams does not store your files. When you upload a document to a Teams channel, it lands in the SharePoint site that was created with that Team. The Files tab is a view into a SharePoint folder, nothing more.
Once that clicks, a lot of confusion clears. “Should this go in Teams or SharePoint?” is the wrong question, because Teams files are SharePoint files. The real question is whether the content belongs to that team’s workspace, in which case the Teams Files tab is a perfectly good way to get at it.
Where it goes sideways is the private chat. Files you drop into a one-to-one or group chat get stashed in your OneDrive and shared from there, not in any team site. So the document everyone references from the chat is, once again, sitting in one person’s personal storage. Same trap, different door.
The one rule, applied
Put the question to any file and you’ll almost always get a clear answer:
| The file is… | It belongs in… |
|---|---|
| Your own draft or personal note | OneDrive |
| Owned by a team or department | SharePoint (or that team’s Teams Files tab) |
| Something the whole org references | A dedicated SharePoint site |
| Shared “just quickly” in a chat | Stop. Move it to the team’s site instead. |
The chat habit is the one worth breaking first. It feels fast, and it quietly scatters your most-shared files into the least-shared place in the whole tenant.
Why this is worth getting right
This isn’t tidiness for its own sake. Where files live decides three things that bite later:
- Continuity. Org-owned files survive staff turnover. OneDrive files don’t.
- Security. You can govern a SharePoint site (who sees it, how it’s shared externally, how long it’s kept). You can’t really govern what people stash in personal storage and chats. If you’re cleaning up before turning on Copilot, this matters even more, because Copilot will happily surface a file that was over-shared years ago. I wrote about that in turning on Copilot without leaking HR data.
- Findability. A structured SharePoint site is searchable and survives. A pile of OneDrive folders and chat attachments is neither.
“Where should this file live?” is a governance question wearing an everyday-annoyance costume. Answer it once, as a rule everyone follows, and most of the mess never forms.
Bottom line
Three places, one rule. OneDrive is yours, SharePoint is the organization’s, and Teams is just a friendly door into a SharePoint site. If more than one person needs the file, it doesn’t go in OneDrive, and it definitely doesn’t live in a chat. Decide the structure once and the daily “where do I put this?” question mostly disappears.
If your tenant is already past the tidy stage and OneDrive has quietly become the filing cabinet, that’s a fixable problem, and the fix starts with mapping what you have before you move anything.