SharePoint vs OneDrive: Differences & When to Use Each

A question our SharePoint support services team answers weekly: where does a given file belong — SharePoint or OneDrive? The two services run on the same engine, which is why they look similar, and they differ in exactly one dimension that matters: who owns the content. This article states the differences and the rule for choosing.

Same engine, different ownership

OneDrive for Business is not a separate storage platform. Each user's OneDrive is a personal SharePoint site provisioned for that user — Microsoft's own admin documentation manages OneDrive quotas, retention, and restore through the SharePoint admin center and SharePoint Online PowerShell, because that is what a OneDrive is: a SharePoint site with one document library and one owner. See pre-provisioning OneDrive (a SharePoint Administrator role and SharePoint license are required to create OneDrives) and OneDrive storage settings, both of which live in SharePoint administration.

The ownership rule: OneDrive holds my files — drafts, working copies, and documents that have no meaning to anyone but the author, where access by others is the exception granted per file. SharePoint holds our files — anything a team, department, or process depends on, where access follows membership in the site rather than a per-file grant. A file that a second person would need if the author left the company is an "our file" and belongs in SharePoint, regardless of who created it.

SharePoint vs OneDrive comparison table

Quota sources: default OneDrive storage space (1 TB default, license-dependent) and the OneDrive service description (5 TB and 25 TB expansion conditions). SharePoint tenant storage is pooled and managed per site in the SharePoint admin center, per manage site storage limits. Teams file placement is documented in how SharePoint and OneDrive interact with Teams.

Retention when a user leaves

This is the difference with operational consequences. When an account is deleted from Microsoft Entra ID, the OneDrive deletion clock starts. The sequence, from OneDrive retention and deletion:

• The OneDrive is marked for deletion and retained for the configured retention period — default 30 days, configurable from 30 to 3,650 days in the SharePoint admin center (set the OneDrive retention for deleted users).
• The deleted user's manager (or a configured secondary owner) receives access and a notification, with a reminder seven days before deletion.
• After the retention period, the OneDrive moves to the site collection recycle bin for 93 days. Shared content stops working at this point; restore requires a SharePoint Administrator and PowerShell.
• After the recycle-bin period, the content is gone. Default total: 30 + 93 = 123 days.

SharePoint sites have no equivalent lifecycle tied to a person. A site owner leaving changes nothing about the content; ownership is reassigned and work continues. Purview retention policies override both timelines in either direction.

When to use which

• OneDrive: personal drafts not yet ready to share; working copies; personal reference material; files shared briefly with one or two people before moving to a team location.
• SharePoint: any document a team produces or consumes; project deliverables; policies and procedures; templates; records with retention requirements; anything referenced from Teams channels; anything that must survive staff turnover.
• Decision test: if the file matters to the business after its author leaves, it goes in SharePoint. If deletion after 123 days would bother no one but the author, OneDrive is acceptable.

Moving files between them

Both directions are built in. In the OneDrive or SharePoint web interface, select files and use Move to (moves the file and, within the same environment, its version history) or Copy to, choosing a SharePoint site as the destination — steps at move or copy files in SharePoint. The OneDrive sync client handles both services: synced SharePoint libraries appear in File Explorer alongside the personal OneDrive folder, so drag-and-drop between them is also a valid move path. Note that Move to does not carry sharing links — links to the old location stop resolving after a move.

Common confusion scenarios

Files shared from OneDrive break when the user leaves. The classic incident: a team works for months from a spreadsheet shared out of one member's OneDrive. The member leaves, the account is deleted, and 30 days later every link dies and the file is in a recycle bin only an administrator can reach. The file was an "our file" living in a "my files" location. The fix is preventive: move team-dependent files to SharePoint while the owner is still employed.

Teams puts files in two different places. A file dropped into a private chat lands in the sender's OneDrive; the same file posted in a channel lands in the team's SharePoint site. Users who share project files over chat are silently building OneDrive dependencies with the failure mode above. Channel posts are the safe default for anything project-related.

"It's shared, so it's a team file." Sharing a OneDrive file grants access; it does not change ownership, quota accounting, or the deletion lifecycle. A OneDrive file shared with fifty people is still one departure away from the recycle bin.

Governance basics

• Default sharing settings: the tenant-level sharing configuration (Anyone links, expiration, default link type) applies to both services and is set in the SharePoint admin center under Policies, per manage sharing settings. OneDrive sharing can be set more restrictive than SharePoint, not less.
• Storage management: OneDrive quotas are per user (default, security-group, or individual limits); SharePoint draws from the tenant pool, monitored per site under Active sites. Both are administered from the same admin center.
• Departure process: confirm access delegation is enabled and a secondary owner is set, and decide the retention value deliberately rather than accepting 30 days by default.

Site-level administration — permissions, storage, sharing reports, lifecycle policies — is covered in our SharePoint admin center guide; for the platform itself, start with what SharePoint is.

FAQ

Is OneDrive just personal SharePoint?

Functionally, yes. Each OneDrive is a personal SharePoint site with a single document library, administered through SharePoint tooling. The product differences — private-by-default permissions, per-user quota, deletion on departure — follow from the single-owner model, not from different technology.

Does OneDrive count against SharePoint storage?

No. OneDrive quotas are per user (1 TB default on most plans) and separate from the SharePoint tenant pool of 1 TB plus 10 GB per licensed user. Moving files from OneDrive to SharePoint moves the storage consumption from the user's quota to the tenant pool.

Can I recover a departed employee's OneDrive files?

Within the retention period (default 30 days after account deletion), the assigned manager or secondary owner has direct access. For the following 93 days, a SharePoint Administrator can restore the OneDrive with the Restore-SPODeletedSite cmdlet. After 123 days total, the content is unrecoverable unless a Purview retention policy preserved it.