Teams, SharePoint or OneDrive: Where Each File Belongs in Microsoft 365

Table of Contents

1. All three tools sit on the same foundation
2. OneDrive: your workspace, not the company’s
3. Teams: where a document lives while people discuss it
4. SharePoint: the memory that outlives people
5. The four-question decision grid
6. The filing habits that cost the most
7. Where to start when everything is already mixed up
8. What Swiss data protection adds to the equation
9. Conclusion
10. FAQ

In most companies, the same question comes back every week: where should this file go? One person drops it into a Teams channel. Another sends it in a private chat. A third keeps it in their OneDrive “until it is finished”. Three weeks later, nobody can find the current version, and the reference document exists in four slightly different copies.

The problem is not technical. In fact, the question is never whether a file belongs in SharePoint or OneDrive as a matter of principle: all three tools do exactly what you ask of them. What is missing in Microsoft 365 is a simple shared rule that anyone can apply without thinking. Therefore, this article sets out that rule, starting from what these tools actually do under the hood.

All three tools sit on the same foundation

Here is the first surprise for many teams: in Microsoft 365, Teams stores nothing. Every team you create spins up a SharePoint site, and each channel gets its own SharePoint document library. As a result, dropping a file into the “Lausanne project” channel means writing into SharePoint. Teams is only the interface.

A file sent in a private chat, however, takes another route. In practice, it lands in the OneDrive of the person who sent it, inside a dedicated chat files folder. In other words, that document belongs to an individual rather than to the team, even when ten people read it.

This architecture also explains permissions, which are often misunderstood. Adding someone to a team opens every file in that team’s standard channels, with no further action. A private channel, on the other hand, creates a separate SharePoint site with its own members. Practically speaking, you never manage permissions in Teams: you manage SharePoint sites from Teams.

Consequently, the real question is never which app to open. It comes down to two points: who needs this file, and how long must it survive? Everything else follows.

OneDrive: your workspace, not the company’s

First of all, OneDrive is personal space. You own it, you decide what leaves it, and the rest stays invisible to colleagues. For a draft, a set of meeting notes or a temporary export, it is exactly the right place.

That comfort comes at a price, though, and teams usually discover it too late. The space depends on an individual account, and accounts eventually close. When someone leaves, that closure takes their OneDrive with it. Microsoft’s documentation on OneDrive retention and deletion adds a useful detail. An unlicensed OneDrive account moves into archive on the 93rd day.

Concretely, the “2026 tender” folder neatly stored in the project manager’s OneDrive turns into a liability the day they resign. So keep one sharp limit in mind. A file your colleague would need while you are away does not belong in your OneDrive.

• Drafts, experiments, intermediate versions: OneDrive fits perfectly.
• Contracts, procedures, deliverables: these belong to the company, so they live elsewhere.
• Files received from a third party for the team: move them at the first share.

Teams: where a document lives while people discuss it

Teams, by contrast, shines on work in progress. Specifically, a channel brings together the people, the conversation and the files of one subject. Moreover, everyone sees who changed what. On an active project, that closeness between discussion and document saves real time.

However, two habits break the model. The first is sending working documents through private chat instead of the channel. That file then leaves the shared space for an individual OneDrive. The second is opening a team for every subject that comes up. After a year, the company runs forty of them, half are dead, and nobody knows which one counts.

Ultimately, one rule holds up over time: a team matches a stable group of people, a channel matches a subject. The Geneva project is therefore not a team, it is a channel of the department that runs it.

SharePoint: the memory that outlives people

SharePoint, for its part, holds everything that must outlast the conversation. Procedures, templates, signed contracts, product documentation, closed project archives: the list grows quickly. These documents need a stable address, deliberate permissions and version history.

In addition, SharePoint offers what Teams does not expose directly. You get metadata, filtered views and separate libraries with their own permissions. You also get communication sites, built to publish information that nobody should edit. Note the nuance: a team site is for producing, a communication site is for publishing.

Metadata beats nested folders

In practice, most teams rebuild their old file server tree inside SharePoint. The result is seven folder levels, endless paths and a structure that only makes sense to whoever built it.

SharePoint suggests another approach. You add columns to a library, such as client, year or status, then create filtered views on those columns. Everyone finds documents through their own logic, without imposing it on others. In short, you describe the document instead of locking it into a single box.

Of course, none of this means abandoning Teams. Your teams keep working there every day, since their channel files already live in SharePoint. The difference shows at the end of a project. Deliverables move to a durable library, and the conversation can disappear without taking the company’s memory with it.

The four-question decision grid

Here is the grid we use in our training sessions. It holds four questions, asked in this order, and a whole team picks it up in ten minutes.

One point deserves attention: the SharePoint or OneDrive answer is not fixed forever. A document often starts as a personal draft, moves into a channel during the active phase, then joins a durable library once approved. That journey is part of the work, exactly like filing a paper folder.

The filing habits that cost the most

Some habits look harmless and still cause most of the time lost in companies. Here they are, in order of frequency.

Sending the working document through private chat

As a result, the file becomes invisible to anyone joining the project later, and it depends on the sender’s account. Use the channel instead, then mention the person you need.

Copying instead of sharing a link

Indeed, every copy starts its own life. Three weeks later two versions circulate, and one of them misses the corrections. A link guarantees a single original.

Creating a Teams team for every subject

Furthermore, multiplying teams scatters documents and complicates access rights. A channel does the job in most cases, and it stays attached to a clear group of people.

Leaving external shares open forever

A link sent to a partner in 2024 often still works today. Consequently, a default expiry date settles the issue once, without blocking collaboration.

Storing company documents in a personal OneDrive

This one costs the most, because it only shows up when the person leaves. On the day the account closes, the company discovers what it lost.

Where to start when everything is already mixed up

Few companies start from a blank page, however. Most inherit a mix of file server, personal OneDrive accounts and teams created along the way. Reclaiming that ground calls for a method rather than a migration project.

1. List the existing spaces. Active Teams teams, SharePoint sites, shared folders on the old server: one spreadsheet is enough to see the real scale.
2. Identify the vital documents. The ones whose absence would block invoicing, an audit or a delivery, whether they currently sit in SharePoint or OneDrive.
3. Decide the rule and write it down. One page, four questions, one example per case. Without a shared document, everyone keeps their own habits.
4. Move in batches, not all at once. One department, then the next, keeping links up to date so current work never breaks.
5. Train people on their own files. A demonstration on a real document beats any generic presentation.

Two of our resources complete this clean-up. Our comparison of SharePoint and OneDrive settles the borderline cases. The ten OneDrive for Business rules secure the personal side.

What Swiss data protection adds to the equation

Finally, filing goes beyond day-to-day comfort. Since the revised Swiss Federal Act on Data Protection came into force, a company must know which personal data it processes. It must also know where that data sits. A candidate file stranded in a former employee’s OneDrive makes that inventory impossible.

External sharing deserves the same attention. Moreover, the Swiss Federal Data Protection Commissioner states that the cross-border transfer of personal data is only allowed under specific conditions. An open share link, with no expiry and no restriction, means losing control of that transfer.

Consequently, a clear storage structure is not only an efficiency matter. It drives your ability to answer an access request, to document your processing activities and to prove that sensitive files stay inside a controlled perimeter.

Conclusion

Choosing between SharePoint or OneDrive is not a contest. Together with Teams, these tools cover three different moments in the life of a document. OneDrive holds what belongs to you, Teams carries the work while people discuss it, and SharePoint keeps whatever must outlive the project and the people.

Ultimately, the point is not to pick one tool forever. It is to give your teams a rule they apply without hesitating. Four questions are enough, provided everyone knows them. That is precisely what separates a company that finds its documents from one that keeps searching.

FAQ

Are Teams channel files really stored in SharePoint?
Yes. Every channel has its own SharePoint document library. Teams simply sits on top of that storage.

What happens to the files of an employee who leaves?
They follow the Microsoft 365 account. A retention period applies after deletion, then the data goes. Company documents therefore belong somewhere other than a personal OneDrive.

Do we need one Teams team per project?
Rarely. A team matches a stable group of people, a channel matches a subject. That distinction prevents a graveyard of abandoned teams.

How do we avoid duplicate documents?
Always share a link rather than a copy. One original circulates, and every change stays visible to everyone.

What is the difference between a team site and a communication site?
The first exists to produce documents together. The second publishes information to an audience that does not edit it.

Should we settle the SharePoint or OneDrive question once and for all?
No. The first hosts company documents, the second your work in progress. Both coexist, each on its own use.