From this autumn, this scene becomes possible: someone opens a three-year-old deck in PowerPoint online and gets an odd error. The file has not been deleted, it is not corrupt, and it is exactly where it was. It is archived. And nobody in IT decided to archive it: a retention policy set up months ago in another department did. The roadmap card frames it as a cost improvement, and it is one. It also changes who decides whether a file opens.
Microsoft 365 roadmap entry 561208 is titled "Microsoft Purview: Data Lifecycle Management – Archive SharePoint files under retention". It was published on 5 May 2026, last modified on 25 August, and is still marked In development: preview in September 2026, general availability in October 2026. The description states, verbatim, that retention-based file archiving "moves inactive content to low-cost storage, lowering costs with no compromise on Compliance, keeping data discoverable and making Copilot results highly relevant".
Look at what that sentence promises and what it does not. It promises cost, compliance, search and Copilot. It says nothing about whether the file opens. And that is precisely the part that will land on your desk.
Two caveats on timing and scope before we go on, because the sources do not quite line up. The dates above are those of the roadmap card in its 25 August version; the analysis by Office 365 for IT Pros, working from message centre notice MC1325441, points to a slightly earlier schedule (preview by mid-September and general availability by the end of September). As for scope, that notice mentions SharePoint Online and OneDrive for Business, while the file-level archive documentation says today that it is SharePoint only. We are saying so rather than picking whichever version suits us: until it ships we will not know.
What the cold drawer actually is
Microsoft 365 Archive has been around for a while for whole SharePoint sites, and since this summer at file level too. The official documentation puts it plainly: it moves content into "a cold storage tier within SharePoint", it stops consuming the tenant's active quota and starts counting as archive storage. End-user search, Purview Content Search and eDiscovery still find it. Copilot, on the other hand, is not trained on archived content — Microsoft sells that as an upside, and for answer relevance it is.
And then, on that same Microsoft Learn page, a single sentence halfway through a paragraph that sums up this whole article: "Content in this tier is no longer directly accessible to anyone." It sits in the body of the page, not in a footnote, and it describes how the cold tier normally works.
Myth 1: "archiving is a storage decision"
Archiving is an availability decision dressed up as a storage decision. The proof is in Microsoft's own list of file-level archive limitations. These applications, it says, may "display incorrect error messages, fail to load correctly, or fail actions taken with archived content":
- ✗Word and PowerPoint online. That is, what happens when someone clicks a document from Teams or from the browser.
- ✗The Teams, OneDrive and SharePoint mobile apps.
- ✗The OneDrive sync client on macOS, and on Windows 10 or earlier. Also on Windows devices that are not configured to receive frequent updates.
- ✗Desktop Office apps not updated since 1 March 2026. That date is a patching requirement hidden inside a compliance feature.
- ✗Clipchamp and Power BI, when trying to import archived content.
And that list is not closed. Microsoft heads it with "The list of known limitation includes but isn't limited to": it is what is known today, not an inventory of what can break tomorrow. Worth reading it that way before promising anyone anything.
Of the three things Microsoft says can happen, the first is the one that hurts: incorrect error messages. An error that says something else, not a notice that the file is archived. Multiply that by a workforce with no idea a cold tier exists and you get tickets describing a symptom that does not lead to the cause. That work does not show up in Microsoft's savings calculator.
Myth 2: "if it gets in the way, you just reactivate it"
Reactivation exists and, since 31 March 2025, it costs nothing in SharePoint: Microsoft removed the reactivation fee. But the way back is not symmetrical. The documentation is explicit: a reactivated file cannot be archived again for 120 days (the pricing page frames it as a four-month period, and notes that the fee removal does not apply to OneDrive accounts).
And there is a detail that comes before that one, and it sets your response time. Microsoft documents two states: for the first seven days the file is Recently archived and "reactivations are instantaneous"; from the seventh day it becomes Archived, where "reactivations can take up to 24 hours". In archiving driven by a retention policy, the file someone asks for will have been in the drawer for weeks or months. So: 24 hours, not minutes.
Put the two figures together and you have the full path back: 24 hours to return the file to whoever asked for it, and four months before the policy can archive it again. With that asymmetry, you roll this out site by site and in stages, not all at once across the tenant.
Who signs this off, and why it is not you
Two details here change how you plan this. First: according to the analysis published by Office 365 for IT Pros on 20 August, once you configure the archive action in a policy or label, it can take up to ten days before Purview's background processes start moving files, and — verbatim — "there's no way to trigger an immediate evaluation and move". There is no "do it now" button, and no "do it Saturday at three".
The second is organisational, and it weighs more. A Purview retention policy is usually not configured by the person who gets the tickets. It is signed off by someone in compliance, legal or management, on perfectly reasonable grounds — "projects closed more than three years ago, at low cost" — with no reason to know that those grounds now include the phrase "no longer directly accessible to anyone". Until now, that policy could only keep or delete. Once this ships it will also be able to change the state of live files.
We have been saying for years that the leading cause of serious outages is not hardware, it is changes someone pushes into production without anyone reviewing them. This is exactly that, in new packaging: a production change coming in through the compliance door, where there is no maintenance window, no canary and no fast way back.
And no, archiving is not backing up
One line, because we already wrote the long version: archiving moves the same copy somewhere cheaper, it does not create a second one. We covered it in a retention policy is not a backup and looked at it from the other side in the Microsoft 365 backup that never leaves Microsoft. Microsoft itself separates the two in its backup documentation: retention and deletion policies "don't affect the backup recovery window, which remains fully isolated from those policies". If they were the same thing, that sentence would not need to exist.
How we are going to roll it out
None of this is a reason not to use Microsoft 365 Archive. It is a reason to treat it as what it is. Our playbook:
- 1Client inventory first, policy second. How many Macs with the sync client, how many Windows 10 machines still alive, which desktop Office build people are on. That list decides whether you can switch this on or whether you have patching work first.
- 2A pilot site that is not finance. A closed-projects site, with a named owner and users you can phone. For file-level archive, the documentation asks you to ensure users know how to reactivate a file at its original location if they need access (for archiving a whole site, the wording is firmer: notify owners and end users first). We turn that into an email with screenshots of the error they are going to see.
- 3The ten days go into the plan. If the effect starts whenever Purview feels like it, you cannot promise a window. What you can do is have someone watching the ticket queue for the two weeks after you touch the policy.
- 4Exclude what we already know does not work. At file level: OneNote, SharePoint pages and agents cannot be archived, and the
Site Assetslibrary does not support file archive. And if archiving whole sites ever comes up, that is a separate list: sites with Teams private or shared channels are only partially supported. Better to know that up front than to find out through an error. - 5Who signs off goes in writing. If compliance proposes the policy, IT reviews it before it is applied. It is the same rule we apply to any change that touches production, and a retention policy with an archive action is now one of them.
When we would not switch it on
If your tenant is below its storage quota, do not switch it on. Microsoft's pricing page is blunt: the archive meter "is charged only when archived storage plus active storage in SharePoint exceeds the included or licensed allocated SharePoint storage capacity limit of the tenant". If you are not over quota, archiving saves you nothing and adds a layer that was not there before.
If you are above it, the maths changes, and changes a lot: $0.05 per GB per month of archive versus buying standard storage packs for the overage. In that case Microsoft 365 Archive is a good, cheap tool, and we say so without hedging. It is just that the invoice is not the only variable in the decision.
One warning buried in the small print that is worth surfacing: if archiving is turned off, or the associated billing subscription becomes unhealthy, archived content stays archived — it can still be reactivated — but in the meantime it "counts as active storage usage". That is, it consumes quota again without becoming accessible again. If you are going to depend on this, watch that subscription the way you watch any other production component.
What Microsoft did without saying so
Microsoft was right to wire retention and archiving together: it fits the data lifecycle and the maths works. What it also did, quietly, is give a compliance policy the ability to change how a file behaves for the person opening it. If those two things are signed off by different people who never talk to each other, the first to find out will be your support desk, and they will find out over the phone.
At everyWAN we manage Microsoft 365 tenants and run our clients' compliance and continuity policies with the same discipline we apply to a cluster: inventory, pilot, notice, and someone watching afterwards. And backups sit apart, with Backup 365: they are a different component and we treat them as one.
Sources (verified one by one): Microsoft 365 roadmap entry 561208, "Microsoft Purview: Data Lifecycle Management – Archive SharePoint files under retention" (created 2026-05-05, modified 2026-08-25, status In development, preview September CY2026, GA October CY2026) — microsoft.com/microsoft-365/roadmap; cold tier definition, per-application limitations, the 120-day reactivation rule and non-archivable file types — Learn: Overview of Microsoft 365 Archive; the seven days of Recently archived and the 24 hours of the Archived state — Learn: Archive states in Microsoft 365 Archive; $0.05/GB/month, billing only above quota, removal of the reactivation fee on 2025-03-31 and behaviour with unhealthy billing — Learn: Pricing model for Microsoft 365 Archive; isolation between retention policies and the backup recovery window — Learn: Overview of Microsoft 365 Backup; MC1325441, the ten-day background processing, the lack of immediate evaluation and the alternative timeline — Office 365 for IT Pros, 2026-08-20. The roadmap card was last modified on 25 August 2026; the dates we give are those of that version.
Do you know which retention policies your tenant has, and who signed them?
We review your Microsoft 365 before October: which policies exist, which clients are out of date, and what would happen if archiving switched on tomorrow. No hand-waving, documentation on the table.
Talk to everyWAN
Microsoft 365
ES 
CAT 
EN