9 September 2026

OneDrive or SharePoint? Where Your Business Files Should Live

Photo by Tumisu on Pixabay

When someone leaves a business, the files they were halfway through don't automatically become the team's. If they were sitting in that person's OneDrive, the files belong to that account rather than the business, and the clock starts running on how long anyone else can reach them.

OneDrive and SharePoint are both part of Microsoft 365, both sync through the same little cloud icon in File Explorer, and most people have never had the difference between them explained. Files end up scattered across whichever one happened to be open at the time, or wherever the team was working in Teams that week. It's a distinction most small businesses using Microsoft 365 have never had spelled out, because nobody sits down to plan file storage on day one. It just accumulates as the team grows.

The one-line difference that solves most of the confusion

OneDrive is your own space. Treat it as the cloud version of a personal documents folder: drafts, working files, anything that's yours until you choose to share it.

SharePoint is the team's space. It's built for files with shared ownership, the documents a department or the whole business works on together. Microsoft's own guidance puts it simply: working alone, save to OneDrive; working with others, save to where the team works.

That's really the whole rule. Everything else, the departures, the broken links, the five slightly different versions of the same proposal, comes down to not applying it consistently.

Why Microsoft Teams throws people off

Teams looks like a third place to store files, which is where a lot of the confusion actually starts. Upload a file to a Teams channel and it isn't stored inside Teams at all, it lands in the SharePoint site sitting behind that team. The Files tab is just a window into that SharePoint library, not a separate storage location.

That's a good thing once you know it. It means anything shared through a Teams channel already has the shared ownership a business file needs, rather than sitting in one person's personal account without anyone realising.

A quick way to decide where something belongs

Three questions cover nearly every case:

• Is it a draft or something only you're working on? OneDrive.
• Does more than one person need it, or is it a client or project file? SharePoint, or the matching Teams channel, which is the same storage underneath.
• Is it currently living only on somebody's desktop, or only in their personal OneDrive, with nobody else able to reach it? Move it.

What actually goes wrong when the split gets ignored

The clearest example is what happens when someone leaves. A deleted user's OneDrive isn't handed over to the business automatically. By default, Microsoft gives their line manager access to it, but only if that manager is actually recorded against the employee in Microsoft Entra ID, or a secondary owner has been set up in the SharePoint admin centre as a fallback. Without either in place, nobody is notified and nobody has automatic access at all.

Where a manager or secondary owner is set, they get an email confirming access, then a reminder seven days before the OneDrive's retention period runs out, and after that the account moves into a recycle bin other people can no longer reach. The default window is 30 days. That's manageable if IT knows to check it, and a scramble if the first anyone hears about it is after the account's already gone. It's exactly the kind of gap our guide to handling staff departures properly is built around: get the process right on the way in, and the way out stops being a fire drill.

Findability suffers too. When a team's documents live across a dozen personal OneDrives instead of one shared SharePoint library, colleagues and new starters alike end up hunting through inboxes and chat history for a file that should have taken seconds to find.

Recovery is the one upside worth knowing about either way. Both OneDrive and SharePoint keep version history and a recycle bin, so a file that's overwritten by mistake or scrambled by ransomware can usually be rolled back rather than rebuilt from scratch. That's a genuinely useful safety net, but it isn't the same as a proper backup. Microsoft's own position is that customers, not Microsoft, are responsible for backing up their Microsoft 365 data, which is worth knowing if a cyber insurance renewal ever asks about your backup arrangements.

Sharing files without creating five different versions

Where a file lives also decides how well sharing it actually works.

Share something from your own OneDrive and you're handing out a link tied to your account. It works today, but if you leave the business or the file gets moved, that link can quietly stop working for whoever it was sent to.

Share from SharePoint or a Teams channel instead, and the people who need it already have access, because the file belongs to the team rather than to you personally. There's no one-off link to remember or reissue later.

It's worth sharing the link itself rather than emailing a copy of the file too. Everyone opening the same document in OneDrive or SharePoint is looking at the current version, rather than each working from their own attachment and creating five conflicting copies by lunchtime. Whether that shared link even asks someone to sign in first depends on a tenant setting a lot of businesses have never checked.

Getting it right without a big cleanup project

• Put shared work in SharePoint or Teams. Anything more than one person touches belongs in a shared library, not one person's OneDrive.
• Keep OneDrive for drafts and personal files. That's what it's for. Just don't let it quietly become the only home for something the team actually needs.
• Turn on Known Folder Move if IT hasn't already. It redirects the Desktop, Documents and Pictures folders on a work laptop straight into OneDrive automatically, so files saved out of habit to the desktop still end up backed up and reachable, without anyone having to remember to move them.
• Check every employee has a manager recorded in Microsoft Entra ID, or a secondary owner set as a fallback. It's the difference between someone automatically inheriting access to a leaver's OneDrive and nobody finding out there was anything worth keeping until it's already gone.
• Agree one simple rule as a team, something like "client files live in the client's SharePoint folder," and it saves the same argument happening every few months.
• Use version history when something goes wrong. Restoring an earlier version is usually quicker than redoing the work, and your IT provider can help if you can't find the option yourself.

None of this needs a big migration project. Most of it is a habit change plus two or three settings worth checking once. If your team's files have never had a proper home, sorting out Microsoft 365 storage properly is part of our Microsoft 365 and cloud work, and we're happy to take a look if you'd rather have someone else work through it.