OneDrive for Business vs SharePoint storage: quotas and gotchas

The Architecture of Separation: OneDrive vs. SharePoint 🏗️

Navigating the Microsoft 365 ecosystem requires a fundamental understanding of how data is siloed. While OneDrive for Business and SharePoint Online share the same underlying architecture (OneDrive is technically a personal SharePoint site collection), their storage governance models are diametrically opposed. For the IT administrator, mistaking one for the other often leads to "Quota Exceeded" tickets or unexpected invoices for extra storage add-ons.

The primary distinction lies in the ownership of the data. OneDrive is designed for the individual—files that are "mine" until I choose to share them. SharePoint is for the organization—files that belong to a project, a department, or a function. This distinction dictates how Microsoft allocates space. OneDrive provides a dedicated bucket for every user, whereas SharePoint provides one giant pool for the entire organization to share.

Strategic Insight: Treat OneDrive as your "Desktop and Documents" in the cloud, and SharePoint as your "Company File Server." Misplacing department data in a personal OneDrive is the most common cause of data loss during employee offboarding.

OneDrive for Business: Understanding User-Based Quotas 👤

OneDrive storage is deceptively simple but has layers of "if/then" logic. Most Enterprise licenses (E3, E5) start every user with 1 TB of space. However, this is not a hard ceiling. If a user reaches 90% of their 1 TB capacity, the administrator can increase that limit to 5 TB via the Microsoft 365 Admin Center or PowerShell.

• The 5 TB to 25 TB Jump: For users who exceed 5 TB, Microsoft allows expansion up to 25 TB, but this requires a manual support ticket and proof of need.
• Beyond 25 TB: If a user needs more than 25 TB, Microsoft provisions the additional space as individual 25 TB SharePoint sites, which is a management nightmare.
• Plan 1 vs. Plan 2: Business Basic and Standard plans (Plan 1) are capped at 1 TB with no path to 5 TB. Only "Plan 2" (included in E3/E5) allows the expansion.

The "Gotcha": Many admins assume the 5 TB limit is automatic. It is not. You must manually change the default storage limit for the tenant or the specific user. Furthermore, if you downsize a user's license from E3 to Business Standard, their 5 TB OneDrive will become read-only until the data is reduced below the 1 TB threshold.

SharePoint Storage: The Pooled Resource Trap 🌊

SharePoint Online storage calculation is the most frequent source of "sticker shock" for CTOs. Unlike OneDrive, which scales linearly with every user, SharePoint uses a Pooled Storage Model. Your total tenant storage is calculated as follows:

[1 TB Base] + [10 GB x Total Number of Licensed Users]

For an organization with 100 users, your total pool is 2 TB (1 TB base + 1,000 GB). This pool is shared across all Communication Sites, Team Sites, and Private Channels. If one department migrates a massive legacy archive into a Team site, they could potentially starve the rest of the company of storage.

Key SharePoint Storage Components:

1. The Recycle Bin: Items in the recycle bin count against your quota until they are purged (usually after 93 days).
2. Version History: This is the "silent killer." Every time a user hits 'Save' on a 50 MB PowerPoint, SharePoint stores a version. If 500 versions exist, that single file is consuming significantly more space than expected.
3. Site Limits: By default, SharePoint sites are set to "Automatic" storage management, meaning a single site can grow to 25 TB.

Practical Tip: Switch your SharePoint storage management to "Manual" in the Admin Center. Set quotas for high-growth sites (like Marketing or Legal) to ensure they don't consume the entire tenant's pool without a formal request for more space.

The 'Hidden' Cost of Versions and Retention 🔐

Managing cloud storage is not just about capacity; it’s about the cost of growth. When you run out of SharePoint space, you have two choices: delete data or buy more. Microsoft sells "Extra File Storage" add-ons, but the pricing is notoriously high compared to Azure Blob storage.

To avoid these costs, admins should implement Microsoft Purview Retention Policies. Instead of letting data sit in SharePoint indefinitely, set policies to move "cold" data to cheaper storage or delete it after its legal usefulness expires.

The Versioning Gotcha: In 2024, Microsoft introduced new controls for SharePoint versioning. Previously, the minimum was 500 versions. Now, admins can set "Smart" versioning or lower limits (down to 100). Reducing the version count on high-traffic libraries can instantly reclaim terabytes of space without deleting a single unique file.

Storage Efficiency Checklist:

• Audit site collections with "Storage Used" vs. "Last Activity Date."
• Identify "Abandoned" sites (sites with no owners or no activity for 180+ days).
• Check the "Large Files" report in the SharePoint Admin Center.
• Apply a tenant-wide versioning limit of 100-200 versions unless compliance requires more.

Lifecycle Management and the 'Orphaned Data' Problem 👻

A major operational risk occurs when an employee leaves the organization. Since OneDrive is tied to the user identity, the data's "timer" starts the moment the account is unlicensed or deleted. By default, you have 30 days to recover or move that data before it is permanently purged.

SharePoint, conversely, is "orphaned-proof." Because the data belongs to a site, the departure of the site owner doesn't affect the data's availability. This is why critical departmental workflows should never be hosted in a user's "My Documents" or OneDrive.

The Wrong Way: Giving a new hire the password to a former employee's account to access their OneDrive. This is a security risk and violates most licensing terms regarding shared accounts.

The Right Way: Use the "OneDrive Access" feature in the M365 Admin Center to grant a manager a temporary link to the former employee's files. Better yet, use a "Pre-provisioning" script to move those files to a designated SharePoint Archive site during the offboarding process.

Summary and Strategic Recommendations 📊

Choosing between OneDrive and SharePoint isn't just a technical decision—it's a financial and architectural one. For small teams, the pooled SharePoint storage might feel infinite. For large enterprises with millions of files, it becomes a line item that needs aggressive management.

To summarize the path forward: 1. Use OneDrive for draft work, personal notes, and volatile data. Leverage the 5 TB expansion for power users to keep that data out of the shared SharePoint pool. 2. Use SharePoint for finalized documents, team projects, and "Gold Source" information. 3. Implement Manual Quotas on SharePoint to prevent "runaway" sites. 4. Audit Version History settings quarterly—this is the most effective way to save storage costs without impacting user experience.

By treating these two storage types as complementary tools rather than interchangeable buckets, IT leaders can maintain a lean, cost-effective Microsoft 365 environment while ensuring data remains accessible and secure.

📊 Comparison