Microsoft is extending Microsoft 365 Archive with a capability that has been a long time coming: the ability to archive individual files, and not just entire SharePoint sites. The feature reaches general availability in July 2026 and gives organisations a far more granular way to move inactive content into a low-cost storage tier, without having to take a whole site offline to do it.
On the surface it reads like a technical refinement. In reality, it is first and foremost a cost-optimisation lever: a way to stop paying active-storage rates for the documents nobody opens anymore, while keeping that content compliant, governed and recoverable. Below, we look at what actually changes, what stays exactly as it is, and how to make the most of it.
Until now, archiving in Microsoft 365 was an all-or-nothing affair at the site level. If you wanted to move content into cold storage, you had to archive an entire SharePoint site, which is rarely practical when most of that site is still in daily use. File-level archiving removes that constraint entirely: from July, you can archive a single document, or a whole folder, directly inside a live document library while the rest of the site carries on exactly as before.
What matters most is that archived files do not actually go anywhere. They stay visible in their original location and keep everything that made them governable in the first place:
their metadata, permissions and compliance attributes remain untouched;
the file simply cannot be opened until someone reactivates it;
the rest of the site stays fully active and unaffected.
It helps to think of archiving less as deletion and more as moving a box down to the basement: the content is still yours, still under control, simply parked somewhere cheaper. In short, this is neither a deletion mechanism nor a retention policy, but a change of storage tier.
This is the part of the announcement that deserves the most attention, because it is where the business case sits. Microsoft 365 Archive runs on a pay-as-you-go model, billed per gigabyte per month, and the charge only applies once your tenant goes over its included storage quota. The mechanics are simple:
Below quota: archiving content costs you nothing extra.
Above quota: archived data is billed at roughly a quarter of the active-storage rate.
To make that concrete, picture a tenant sitting 2 TB over quota, where around 1.5 TB is old project content that almost never gets touched. Moving that volume into the archive tier could cut the overage cost on it by something in the region of 75%, with no migration project to run and nothing ever leaving Microsoft 365. The precise figure depends on your own rates and quota position, so it is worth modelling against your real numbers, but the lever is genuinely easy to pull.
One clarification matters before anyone gets carried away, because it is the single most common misunderstanding around this feature: archiving does not free up space. Archived files still count towards your total footprint, and your tenant-level consumption stays exactly the same. What changes is the classification of that storage, as the volume shifts from "active" to "archived". The benefit shows up on the invoice, not on the quota.
This is the trade-off teams most often overlook, and it is an important one. Once a file is archived, it leaves the everyday knowledge layer of Microsoft 365:
it is removed from default search results;
Copilot no longer uses it to generate answers;
it remains reachable only through admin and compliance tools such as Microsoft Purview.
That changes the nature of the decision. Choosing what to archive is no longer only about which files are cheap to keep, but about which ones still need to surface when someone goes looking. Archive a document a team is quietly relying on, and the saving comes at the cost of findability. Handled thoughtfully, this is as much a question of knowledge management as of storage.
Reassuringly, this is where nothing changes, which is exactly what makes the feature safe to adopt, even for sensitive or controlled content. Archiving a file leaves permissions untouched, does not interfere with retention policies, and does not interrupt eDiscovery. Every action is logged, and the data never leaves the Microsoft 365 compliance boundary.
The one operational detail worth passing on to your support teams concerns getting files back:
files archived within the last 7 days reactivate instantly;
older files can take up to 24 hours to become available again.
This is normal cold-storage behaviour rather than a limitation, but it is the kind of thing that generates a help-desk ticket if nobody is expecting it.
General availability rolls out worldwide across July 2026 and will be enabled by default wherever Microsoft 365
Archive is already active, so the PowerShell activation step the preview required simply disappears. The only prerequisites are that Microsoft 365 Archive is switched on and that pay-as-you-go billing is configured.
That makes the coming weeks a sensible moment to prepare, and the preparation is more of a conversation than a configuration:
identify which content is genuinely cold and inactive;
decide which content must stay discoverable in search and Copilot, regardless of cost;
brief your storage governance and help-desk teams on the new Archive action and reactivation timings.
Used deliberately, file-level archiving is one of the easier ways to take cost out of SharePoint without disrupting the people who use it every day. The only real mistake is to treat it as a purely technical switch, because the moment content is archived, it also leaves the everyday knowledge layer your teams depend on.
If you'd like to understand
how much file-level archiving could realistically save your organisation,
which content is safe to archive without losing it from search and Copilot,
or how to roll it out cleanly before and after the July 2026 GA,
our teams are happy to help you review your Microsoft 365 storage and governance setup.
👉 Feel free to reach out for tailored advice.
|
Thomas Vanvinckenroye |