OneDrive

OneDrive is the personal cloud file storage that comes with every Microsoft 365 user account. Each user gets their own OneDrive (commonly 1 TB on business plans) for files that belong to them rather than to a team — drafts, notes, personal working copies — with apps that sync those files to Windows, macOS, iOS, and Android devices.

Under the hood, OneDrive is built on the same engine as SharePoint, and the same co-authoring, versioning, and sharing controls apply. The practical rule of thumb: store personal working files in OneDrive, and shared team files in SharePoint or a Teams channel. There's also a consumer "OneDrive" tied to personal Microsoft accounts.

Why "personal SharePoint site" isn't a technicality

That OneDrive is literally a SharePoint site under the hood explains almost every behaviour that otherwise looks inconsistent: the same file-path length limits, the same version history depth, the same external-sharing policy dial, and the same recycle-bin mechanics apply to a OneDrive as to any SharePoint document library. It also explains the organisational risk that gives OneDrive its bad reputation for team files: a SharePoint team site has an owning team that survives any one person leaving, but a OneDrive belongs to exactly one person, and when that person's account is deleted, their OneDrive enters a retention countdown (default 30 days, configurable) before it's gone for good — see OneDrive storage quotas and limits for the exact mechanics and how to extend or automate the rescue.

Worked example

A consultant leaves a client's OneDrive project folder shared with three colleagues via a link, rather than moving the material to the team's SharePoint site — a shortcut that feels harmless at the time. Eight months later the consultant leaves the company. IT's standard leaver process disables the account and starts the OneDrive retention countdown; nobody remembers the shared folder exists until one of the three colleagues can no longer open it. Recovering it means an admin restoring access to the departed user's OneDrive during the retention window (or, if that's already passed, requesting an emergency restore from backup if one exists) — work that a five-minute move to SharePoint at the time would have avoided entirely. This is the exact failure mode the "personal files in OneDrive, team files in SharePoint" rule exists to prevent.

Common pitfalls

The most common mistake is using OneDrive sharing links as an informal team-collaboration pattern instead of moving the content to a SharePoint site once more than one person needs it regularly — the smell test is simple: if a file in someone's OneDrive has accumulated several sharing links, it has become a team file living in the wrong place. The second is not enforcing Known Folder Move, which leaves Desktop and Documents unprotected on laptops and turns every hardware failure into a potential data-loss incident that OneDrive was specifically positioned to prevent. The third is confusing OneDrive for Business with consumer OneDrive when troubleshooting sync issues — the two are entirely separate services with separate storage and controls, and a user signed into both on the same device can genuinely be looking at the wrong one when a file "goes missing."