Why SharePoint Isn’t a File Server: How to Avoid SharePoint Storage Limits and Read-Only Lockouts

SharePoint is one of the most useful platforms in Microsoft 365. It supports collaboration, document control, secure sharing and structured information management. But it was never designed to be an unlimited dumping ground for every file a business has ever created – and Microsoft is now enforcing that more firmly.

When SharePoint storage is full, sites can drop into read-only mode. Staff can still open files, but they can’t upload, edit or save until storage is reduced or more capacity is purchased. For a Perth business, that isn’t IT housekeeping. It’s a work stoppage, and it’s usually discovered at the worst possible moment.

The right response isn’t automatically to buy more storage. It’s to understand what’s consuming capacity, clean up what’s no longer needed and put each type of data on the platform best suited to it.

What’s changed: Microsoft is enforcing storage limits more strictly

There are two separate limits, and businesses often confuse them.

Your organisation’s SharePoint storage pool. Every SharePoint site – including the files behind every Microsoft Teams channel – draws from one shared pool. Microsoft’s SharePoint Online limits set that pool at 1 TB plus 10 GB per eligible licence, plus any extra storage you buy. When the pool is exceeded, Microsoft’s out-of-storage guidance confirms sites go into read-only mode and changes can’t be saved.

Each user’s OneDrive storage. From mid-2026, Microsoft began re-aligning every user’s OneDrive quota with the storage their licence includes. Users who are over that amount – for example because an admin once set a higher custom quota, or the user was moved to a cheaper licence – can have their OneDrive set to read-only until usage is reduced.

Both end the same way: people who can see their files but can’t work on them.

How much SharePoint storage do you actually have?

A worked example: a 50-person business on eligible Microsoft 365 business licences gets 1 TB + (50 × 10 GB) = 1.5 TB of pooled SharePoint storage. Migrate 3 TB from an old file server and you’re 1.5 TB over before anyone saves a new document.

Some licence types contribute less to the pool, or nothing, so check your real entitlement in the SharePoint admin centre rather than assume.

Also, what you see isn’t always what you’re using. Displayed library sizes can understate consumption because storage also includes:

• Version history – every saved version of every file
• Recycle bins – both stages, until they’re emptied
• Retention and preservation hold libraries – copies kept for compliance
• Teams files – every channel is a SharePoint site
• Inactive sites – old projects and Teams nobody has touched in years

Your options when SharePoint storage is full

Microsoft recommends three responses: buy more capacity, archive inactive content that must be retained, or delete data that’s no longer needed. In practice there’s a fourth that’s often the biggest win: trimming version history. The best result usually comes from a planned combination rather than a rushed purchase after users lose write access.

1. Buy more storage

The quickest fix, but extra SharePoint storage is billed per gigabyte every month, indefinitely. It treats the symptom and, without governance, the bill keeps growing.

2. Archive inactive content with Microsoft 365 Archive

Microsoft 365 Archive moves inactive sites into a cold storage tier that stays inside SharePoint. Archived content no longer counts toward your active storage quota, keeps its Microsoft Purview retention and compliance settings, and can be reactivated when needed. Microsoft puts the saving at up to 75% compared with buying additional storage, and you only pay for archive storage once your total storage exceeds your tenant’s quota.

For completed projects, closed client matters and old financial years that must be kept but are rarely opened, this is often the most cost-effective answer.

3. Trim version history

Every time a file is saved, SharePoint keeps a version. A large presentation edited weekly can generate gigabytes of history over a year. Microsoft’s automatic version history limits keep the versions most likely to be needed and progressively remove older intermediate ones – Microsoft reports roughly 94–96% less version storage compared with count-based limits.

The catch: changing the setting only affects new versions. Existing versions stay until an administrator runs a version trim job. Check retention policies first, as they can require versions to be kept.

4. Delete what no longer needs to be kept

Duplicate exports, abandoned backups, superseded media and copies of copies. Remember to empty the recycle bins afterwards, as deleted files continue to count until they’re permanently removed.

Use SharePoint for what it does best

SharePoint delivers the most value when it’s used as a business information platform, not merely as a network drive in a web browser. Its strengths include:

• Document management: controlled libraries, co-authoring, permissions and structured collaboration.
• Version control: the ability to review and restore earlier versions, when version settings are managed sensibly.
• Compliance and retention: policies that support record keeping, legal obligations and information governance.
• Metadata: meaningful labels and columns that make content easier to organise, filter and find.
• Workflow and automation: approvals, notifications and business processes built around documents and lists.

If a business copies an old file server into SharePoint without redesigning permissions, removing obsolete data or deciding how information should be classified, it may gain little beyond remote access. It can also carry years of duplication and poor folder structures into a platform where additional storage has a direct cost.

Three terabytes of data probably doesn’t all belong in SharePoint

A business with around 3 TB of data should pause before moving it all into SharePoint. Some of that information may be active Office documents that teams collaborate on every day. Some may be completed projects, backups, exported system data, raw images, video, software installers, CAD files or records retained only for historical reasons. These categories have different performance, cost, access and compliance requirements.

The right question isn’t “Can SharePoint hold this?” It’s “What business outcome do we need from this data, and which platform provides it securely and cost-effectively?” That question should be answered before a SharePoint migration begins, not after.

Where should each type of data live?

Better options for large or specialised datasets

Ignite for engineering and CAD workloads

Large CAD files and engineering datasets can create challenges for synchronisation, performance and storage cost. A purpose-suited platform such as Egnyte – Egnyte: AI Context Layer & Content Cloud for Enterprises -may provide SharePoint-like access and collaboration for these workloads at a lower storage cost than continually adding SharePoint capacity. Suitability should be assessed against file behaviour, integrations, security and the way project teams work – something we see regularly with engineering, architecture and construction clients.

Azure Files for archives and large repositories

Azure Files can be a strong option for large data repositories or archive workloads that need cloud-based file access without SharePoint’s collaboration layer. It suits organisations that want to stay within the Microsoft ecosystem and can replace or supplement an on-premises file server. Design still matters, including identity, access, backup, performance, data location and ongoing Azure consumption costs – see our cloud computing services.

A traditional file server still has a place

Cloud-first doesn’t mean cloud-only. Organisations with very large datasets, specialised applications, demanding local performance requirements or limited internet connectivity – common at regional WA sites – may still be well served by a properly managed file server. In some environments, a server may also support local infrastructure roles. The decision should be based on workload and risk, not fashion.

Box, Wasabi and other cloud storage platforms

Alternative cloud platforms can offer lower-cost storage and useful sharing or archive capabilities. However, moving data outside Microsoft 365 can introduce separate identity, management, compliance, support and integration considerations. A lower per-terabyte price is only one part of the total cost and risk assessment.

Clean up before you migrate or buy more storage

Data clean-up is usually the fastest way to improve a migration plan and reduce future storage costs. Organisations commonly discover obsolete project folders, repeated exports, employee copies of the same material, superseded media, abandoned backups and historical data with no clear owner. Keeping everything can feel safer, but unmanaged retention creates cost, search clutter and additional exposure if sensitive information is compromised.

A practical clean-up should involve business owners, not only IT. Each department understands the context, legal value and operational importance of its records. Your managed IT services provider can supply reporting, identify large sites and file types, review version history and recommend platforms, but the business should approve what is deleted, archived or retained.

SharePoint storage clean-up checklist

1. Confirm the tenant entitlement. Check total capacity, current consumption and any purchased add-ons in the SharePoint admin centre.
2. Check OneDrive users against their licence. Identify anyone over their licensed quota before Microsoft sets them to read-only.
3. Identify the largest sites. Review active sites, ownership, growth trends and business purpose.
4. Investigate version history. Apply automatic version limits and trim existing versions where retention rules allow.
5. Review inactive content. Decide what can be deleted, archived in Microsoft 365 Archive or moved to lower-cost storage.
6. Classify specialised data. Separate CAD, video, backups, application data and long-term archives from everyday collaboration documents.
7. Check retention obligations. Avoid deleting records that must be preserved for legal, contractual or industry reasons.
8. Assign owners. Every important site and data repository should have a current business owner.
9. Set governance rules. Define where new data belongs, how long it is retained and who reviews storage growth.
10. Monitor before the limit becomes urgent. Regular reporting is cheaper and less disruptive than recovering from read-only sites.

Storage management is also a security issue

Excess data isn’t harmless. Every unnecessary file increases the amount of information that must be searched, protected, backed up, governed and potentially reviewed after a cyber incident. Old folders may also contain personal information, credentials, contracts or financial records that no longer need to be broadly accessible.

There’s a legal angle too. Under Australian Privacy Principle 11, businesses covered by the Privacy Act must take reasonable steps to destroy or de-identify personal information once it’s no longer needed. Holding it “just in case” increases what’s exposed in a data breach.

And if you’re rolling out Microsoft Copilot, stale, over-shared files matter more: Copilot can surface anything a user has permission to see, including outdated drafts and documents that should have been locked down years ago.

A good data strategy connects storage design with permissions, retention, business continuity and cyber security. Reducing clutter makes abnormal activity easier to investigate, lowers the volume of sensitive material at risk, and gives staff clearer locations and fewer outdated documents to navigate.

Build a data placement strategy, not another storage silo

SharePoint remains an excellent solution. It just isn’t the right solution for every file. Active collaborative documents belong in SharePoint. Personal working documents belong in OneDrive. Inactive records may fit Microsoft 365 Archive. Large engineering datasets may need a specialist platform. Large file repositories may suit Azure Files, and high-performance local workloads may still justify a file server.

The best outcomes are rarely based on a single product. They combine technology, governance and commercial planning so information stays available, secure and affordable. Businesses also need clear responsibility for classifying their data, approving retention decisions and following agreed storage practices.

Buying more storage can be part of the answer, but it shouldn’t replace good information management. An informed review can prevent disruption, reduce unnecessary costs and give staff a simpler, more reliable way to work.

Talk to Qbit IT Solutions about your SharePoint storage

If your SharePoint storage is growing quickly, your tenant is approaching its quota, staff are already seeing read-only warnings, or you’re planning a large data migration, Qbit IT Solutions can help you work out what belongs in SharePoint and what should be stored elsewhere.

We provide storage analysis, version history and archive clean-up, Microsoft 365 governance, data storage design, migration and ongoing management for businesses across WA – from Port Hedland to Busselton, West Perth to Kalgoorlie.

Contact Qbit IT Solutions or book an IT assessment to review your SharePoint and business data before storage limits disrupt your team.

Frequently asked questions

How much SharePoint storage does my business get? Most Microsoft 365 business and enterprise tenants get 1 TB plus 10 GB per eligible licence, pooled across all SharePoint sites and Teams. A 50-user business gets about 1.5 TB. Check the exact figure in the SharePoint admin centre.

What happens when SharePoint storage is full? Sites go into read-only mode. Users can open and download files but can’t upload, edit or save until storage is reduced or more capacity is purchased.

Why is my OneDrive suddenly read-only? Microsoft now aligns each user’s OneDrive quota with what their licence includes. If a user is storing more than their licensed amount, OneDrive becomes read-only until usage is reduced or the licence or quota is changed.

Does version history count toward SharePoint storage? Yes. Every saved version uses storage, which is why libraries often use far more space than their visible file sizes suggest. Automatic version limits and a version trim job can recover significant space.

What’s the cheapest way to free up SharePoint storage? Usually a combination of trimming version history, deleting genuinely obsolete content and moving inactive records to Microsoft 365 Archive, which Microsoft says costs up to 75% less than buying extra storage.

Should I move my file server to SharePoint? Move active, collaborative documents to SharePoint. Large CAD and engineering files, application data, backups and long-term archives are usually better placed on Azure Files, a specialist platform, archive storage or a managed file server.

Frequently asked questions