The short answer: OneDrive is your personal drive, SharePoint is the organisation's shared drive and Teams is the collaboration layer on top — files you share in Teams technically live in SharePoint or OneDrive. Anyone who knows this three-way split always knows where a document belongs; anyone who doesn't ends up with documents scattered across personal folders, email attachments and dozens of teams. This article explains the division of roles, gives four rules of thumb and names the governance pitfalls every growing organisation runs into.
The short answer
OneDrive is your personal drive (drafts and your own work), SharePoint is the organisation's shared drive (team sites with shared documents), and Teams is the collaboration layer on top — chat, meetings and channels. The confusion arises because Teams has no storage of its own: files you share in a team technically live in SharePoint; files in a private chat live in the sender's OneDrive.
Anyone who knows that three-way split can answer virtually any 'where is this file' question. Anyone who doesn't gets the familiar landscape: documents scattered across personal folders, email attachments and ten teams — with no one knowing which is authoritative.
OneDrive: personal work
OneDrive is meant for documents in the draft stage and for personal work that is not (yet) the team's. It is tied to one person: if they leave, in principle access to those files leaves with them — there is a limited period in which an administrator can secure them.
That immediately gives you the most important policy rule: anything the team needs does not belong in OneDrive but on a team site. The practical pitfall is sharing from OneDrive: it works so easily that whole departments end up collaborating in one colleague's personal folder. That goes fine until that colleague leaves or reorganises the structure.
SharePoint: the shared source of truth
SharePoint is the place for documents that belong to the team or the organisation: projects, contracts, handbooks, templates. Every team site has its own permissions, version history and its own recycle bin; set up well, it replaces the classic network drive — including a structure per department or project.
The setup choice that makes the difference: few, logically organised sites with clear owners, rather than a site for every whim. And: manage permissions at site or library level, not per individual document — exceptions at document level are impossible to explain to anyone a year later. For retention periods and recovery, the periods in our article on Microsoft 365 backup apply.
Teams: the collaboration layer
Teams is the place where the work is discussed: chat, meetings, channels per topic. Every team you create automatically gets a SharePoint site behind it — the Files tab inside a channel is simply a folder on that site. Teams is therefore not a third storage location, but a window onto the other two.
The governance pitfall is called team sprawl: anyone can create teams, and after two years there are eighty — thirty of them dead and five duplicates. Agree on who creates teams, use a naming convention and archive finished projects. Watch out with external guests: a guest in a team sees the entire associated site, not just the channel they were invited to.
The rules of thumb for your team
Four agreements that remove ninety percent of the confusion. One: drafts with yourself (OneDrive), final and shared on the team site (SharePoint), the conversation about it in Teams. Two: share links instead of attachments — then there is one version and everyone works in the same document. Three: one owner per site or team, who manages permissions and clean-up. Four: policy before migration — anyone who moves everything first and wants to tidy up afterwards never tidies up.
This setup is a fixed part of a good migration to Microsoft 365 and of ongoing Microsoft 365 management. If you are torn between the Microsoft and Google ecosystems, read Google Workspace vs Microsoft 365.
In short
- OneDrive = personal (drafts), SharePoint = the team's (final and shared), Teams = the conversation about it.
- Teams has no storage of its own: channel files live in SharePoint, private-chat files in the sender's OneDrive.
- Team work does not belong in OneDrive: when the owner leaves, the team loses access.
- Share links instead of attachments — one version, no stray copies.
- Prevent team sprawl: limited creation rights, a naming convention, archiving after completion and one owner per team or site.
Further reading
- Microsoft 365 management by RiverFlows
- Migrating to Microsoft 365: the step-by-step plan
- Microsoft 365 backup: why the default is not enough
- Google Workspace vs Microsoft 365
- Microsoft 365 pricing per user (2026)
Frequently asked questions
What is the difference between OneDrive and SharePoint?
OneDrive is personal storage, tied to a single employee — meant for drafts and your own work. SharePoint is the organisation's shared storage, in team sites with their own permissions and version history — meant for everything that belongs to the team. Rule of thumb: as soon as more people need a document, it belongs on SharePoint.
Where are the files I share in Teams stored?
Teams has no storage of its own. Files in a team channel live on that team's SharePoint site (the Files tab is a folder on that site); files in a private chat live in the sender's OneDrive, with sharing permissions for the recipient.
What happens to OneDrive files when an employee leaves?
The OneDrive account is deleted after offboarding; an administrator has a limited period to secure the files. That is why the policy rule matters so much: team work belongs on SharePoint — then nothing is lost when someone leaves. Make securing OneDrive a standard part of your offboarding process.
How do I prevent sprawl of teams and sites?
Three agreements: limit who can create new teams (or set up a request process), use a naming convention and archive teams once a project is finished. Assign one owner per team and site to manage permissions and clean-up.
Can external people view content in Teams or SharePoint?
Yes, via guest access — handy for collaboration, but mind the scope: a guest in a team generally sees the entire associated SharePoint site. Prefer sharing with external people per site or folder with explicit permissions, and have guest access reviewed periodically.
Prefer these kinds of insights in your inbox?
Leave your email address and we'll add you to the list and email you as soon as the next edition on IT, automation and dashboards comes out. You can unsubscribe at any time with a single email.