Microsoft is preparing to give organizations a new way to handle the growing pile of old documents in OneDrive and SharePoint: a built-in, policy-driven archive button. The company has updated its Microsoft 365 roadmap to show that a “Archive” retention action will enter preview in August 2026 and become generally available in September 2026, allowing administrators to automatically move stagnant files to lower-cost cold storage while keeping them compliant and discoverable.
A New Archive Action Joins Retention Policies
Microsoft Purview Data Lifecycle Management has long been the control panel for deciding how long emails, files, and other content must be kept. Until now, the main outcomes were simple: retain items, delete them after a set period, or retain them first and then delete. The upcoming release adds a fourth option—archive—directly into the retention policy workflow.
Here’s the concrete change: admins will be able to configure a Purview retention policy that, after a file becomes inactive, moves it from the usual SharePoint or OneDrive storage into Microsoft 365 Archive. This is a purpose-built cold tier that costs less per gigabyte than standard SharePoint storage. The file remains governed by the same compliance rules, but it no longer consumes active storage quotas in the same way.
Key technical details from the roadmap and related documentation:
- Roadmap ID: 561208, last updated July 20, 2026.
- Preview: August 2026.
- General availability: September 2026 for worldwide standard multi-tenant environments.
- Scope: Files in SharePoint Online document libraries and OneDrive for Business accounts.
- Billing: Archive storage is metered at $0.05 per GB per month when a tenant’s combined active plus archived data exceeds its licensed allocation. (Current pricing; subject to change.)
- Reactivation: An archived file can be restored, but for SharePoint, a 120-day waiting period applies before it can be re-archived. OneDrive behavior may differ and will be clarified during preview.
This is not a silent, background change. Administrators must explicitly define the conditions that qualify a file for archiving and associate those with a retention policy. Microsoft will not automatically archive existing content simply because the feature is turned on.
How This Affects Different Teams
For IT Administrators and Storage Planners
If your organization is bumping up against its SharePoint storage limit, this feature offers a new lever. Instead of buying more expensive active storage or running manual cleanup campaigns, you can set rules that automatically push rarely touched documents into archive. The savings can be meaningful: 10 TB of excess data billed at $0.05/GB/month would cost roughly $512 per month, compared to standard additional SharePoint storage that runs several times higher.
But there’s a catch: archived data still counts toward your total consumption. You won’t get free space; you’re just paying less for the cold tier once you exceed your included capacity. And the archive meter only kicks in if your total (active + archive) is above the tenant’s licensed limit. Good housekeeping still matters.
You’ll also need to keep a close eye on the billing setup. Microsoft 365 Archive requires pay-as-you-go billing. If that subscription lapses or becomes unhealthy, no new archives will be processed, and existing archived content might unexpectedly count as active storage—driving up costs.
For Compliance and Legal Teams
Archived files remain inside the Microsoft 365 compliance boundary. They are discoverable through Content Search and eDiscovery, and any existing holds, retention labels, or records declarations continue to apply. The archive action is layered on top of preservation, not a replacement for it.
That said, discovery is not the same as instant access. A user cannot simply open an archived document from Teams or the Office desktop app. It must be reactivated first, which can take some time. Legal teams should test eDiscovery workflows during the preview to understand how long exports take and whether any metadata changes. Chain of custody considerations mean you’ll want to log every archive and reactivation event, and to clearly document which policy triggered the move.
For End Users
For most employees, the change will be invisible—until they try to open a file that has been archived. They might see an error or a message that the content isn’t available. Microsoft’s existing documentation for file-level archives already notes that some clients (older Office builds, mobile apps, certain web scenarios) don’t handle archived items gracefully. Help desks should be ready for tickets that look like corruption or permission problems but are really just archive status.
For Finance and Operations
Because the billing is consumption-based, there’s a direct relationship between policy design and the monthly invoice. Overly aggressive archiving could trigger excessive reactivations (and waste the effort), while too-loose criteria might not save enough to justify the administrative overhead. Finance teams may want a seat at the table when retention and archive policies are being written—especially in large organizations where SharePoint storage growth is a seven-figure line item.
The Backstory: From Site Archives to Smarter Storage
Microsoft 365 Archive debuted as a way to move entire inactive SharePoint sites into colder storage. That works well for completed projects or abandoned team sites but misses the reality that most active sites contain a mix of current and historical documents. A finance site, for example, might hold this year’s budget alongside contracts from a decade ago.
File-level archiving was the next step, letting admins target individual documents. The Purview integration announced here closes the loop: it ties archiving to the lifecycle rules that organizations already rely on for compliance. Instead of two separate processes—one for retention, one for storage management—they become one.
The timing is no accident. As Microsoft 365 Copilot becomes more embedded in daily work, the quality of AI responses depends heavily on the freshness and relevance of the data it sees. Archived content will be excluded from Copilot’s active index, meaning old drafts, superseded policies, and obsolete reports won’t pollute the answers. That’s a strong operational incentive beyond just saving money.
Five Steps to Get Ready Now
With preview still weeks away, there’s time to lay the groundwork. The organizations that benefit most will be those that understand their data before they start archiving it.
-
Inventory your inactive content. Not just last-modified dates—track last-accessed patterns, document types, site purposes, and any existing retention labels. A file that hasn’t been touched in three years but is still referenced by an active workflow might not be a good archive candidate.
-
Define what “inactive” means for your business. A simple “last modified older than X days” rule is rarely enough. Consider: Does the document still have an owner? Is it part of a legal hold? Is it a template, a policy, or a technical standard that should stay readily available? Build exclusion lists for files that are rarely edited but still vital.
-
Run a pilot with non-critical content. Pick a well-understood SharePoint library. Enable the archive action with conservative thresholds, then test everything: Can users still find the files? Does eDiscovery work as expected? What happens when you reactivate a document? How do the Office clients behave? OneDrive merits its own separate pilot because personal work patterns and sync behavior differ from team sites.
-
Train your support staff. They should know how to check if a file is archived, which policy governed it, and how to request a reactivation. Avoid a situation where every random “file won’t open” ticket requires escalation to a global admin.
-
Set up billing alerts and cost tracking. Since the archive meter depends on your total consumption over the licensed limit, small changes in active storage can swing the bill. Configure budget notifications in Azure and assign someone to review them monthly.
What We’ll Learn During Preview
The August preview should answer the biggest open questions:
- Policy conditions: Exactly which signals can trigger archiving? Is “last accessed” reliable enough across all clients, or will Microsoft offer composite inactivity metrics?
- OneDrive specifics: Existing archive docs focus mainly on SharePoint. The roadmap explicitly includes OneDrive, so we’ll need clarity on sync behavior, departed-employee handling, and any difference in reactivation fees or cooling periods.
- Copilot exclusion mechanics: Microsoft says archived files won’t be indexed by Copilot. But how quickly does that take effect? Are there cached references that might linger? Good reporting tools will be essential to verify that you’re actually improving AI answer quality, not just hiding documents.
- Recovery and rollback: Accidental mass-archiving is a real risk. Admins will need dashboards that show what’s queued, what’s been moved, and a straightforward way to freeze or reverse a policy that’s too aggressive.
Microsoft’s move is a logical—and overdue—step toward uniting compliance and storage management. When it works well, policy-driven archiving will cut costs, reduce clutter, and make both search and AI smarter. But the difference between a governance win and a user-productivity disaster will come down to careful planning, clear communication, and a solid understanding of your organization’s data landscape. The preview period is your chance to get all three right.