When Everything Has to Stay, but Not Everything Should Stay Active
- 1 day ago
- 3 min read
Most SharePoint environments don’t become cluttered overnight. Instead, they gradually fill with completed projects, closed files, and “just in case” documents. In other words, the more likely culprit is content that nobody actively uses anymore, but nobody feels confident deleting either.
The problem isn’t that the content exists. It’s that it all lives in the same state.
Active collaboration sites end up carrying years of historical material. Over time, it becomes increasingly difficult to distinguish what’s still relevant, what’s finished, and what simply hasn’t been dealt with yet. Microsoft’s new file-level archiving capability in Microsoft 365 Archive addresses this problem with a deceptively small, but meaningful, change.
The Past: Site-Level Archiving Only
Until now, archiving in Microsoft 365 has largely operated at the container level. Organizations could archive an entire site, mailbox, or location. This worked well when something was truly complete, such as a closed project, retired team, or finished program.
From a records management perspective; however, this model never fully fit.
In the paper era, files were moved to a records centre, kept semiactive for a defined period, and eventually destroyed. SharePoint has struggled to support this same lifecycle digitally since its early days. Other platforms, such as OpenText, addressed this challenge through tiered storage, allowing organizations to move files to lower cost storage based on clear criteria.
But many real-world lifecycle scenarios don’t align neatly with container-level archiving.
A project site might remain active for years while individual deliverables, such as contracts or invoices, are finalized and never accessed again. A case management site might stay open while older case files need to be preserved, but not kept front and centre. Treating all content the same forces organizations into uncomfortable compromises.
That’s where file-level archiving comes in.
File-Level Archiving
With file-level archiving in Microsoft 365 Archive, organizations can archive individual files rather than entire sites or locations.
Archived files are preserved and governed, but they are no longer treated as active working content. The surrounding site continues to function normally, while specific files are clearly identified as inactive.
This capability does not replace retention policies, records management processes, or disposition workflows. Instead, it introduces a long missing state between “active” and “disposed”, which was historically referred to as semiactive within SharePoint.
There is also a cost implication worth noting. Content stored in Microsoft 365 Archive is significantly cheaper than keeping the same data active in SharePoint. Based on Microsoft’s published pricing, archived storage is typically a fraction of the cost of active SharePoint storage. At scale, this difference can become substantial, particularly for organizations managing large volumes of long-term, low access content.
What About Microsoft Purview?
The short answer: nothing goes away
Microsoft 365 Archive doesn’t replace Microsoft Purview, and it doesn’t bypass it either. Archived content remains within the same compliance and governance boundary as active content.
This distinction is important, as archiving is often misunderstood as either a separate system or a compliance loophole. It isn’t.
Archived content:
Remains searchable at the admin and Microsoft Purview level
Continues to be subject to Purview retention policies
Can be included in eDiscovery cases and legal holds
Stays within SharePoint rather than being exported elsewhere
In other words, archiving changes how content is accessed, not how it is governed.
Purview search, retention, and legal workflows continue to function as expected. For organizations with regulatory or legal obligations, this matters. Archiving isn’t an escape hatch. It’s a way to reduce operational noise while keeping compliance controls firmly in place.
A visual comparison of SharePoint storage versus Microsoft 365 Archive helps illustrate this distinction clearly. What’s more important, however, is what that distinction enables operationally.
File-level archiving doesn’t change how content is governed in Microsoft 365, but it fundamentally improves how it can be managed over time. By introducing a true semiactive state between “active” and “disposed,” Microsoft 365 Archive allows finished work to step out of day‑to‑day collaboration without losing compliance, discoverability, or legal integrity. The result is clearer collaboration spaces, reduced operational noise, and lower long‑term storage costs, all while remaining fully aligned with Microsoft Purview. It’s a small capability shift that quietly brings SharePoint closer to the content lifecycle models organizations have needed for years.
