Microsoft has quietly rolled out file-level archiving in SharePoint to all worldwide standard multi-tenant tenants. Marked as launched on July 15, 2026, the feature under Roadmap ID 477371 lets organizations move individual inactive files into SharePoint’s archive tier—without touching the rest of the site.

The change marks a significant shift from the blunt instrument of site-wide archiving. Now, a single Word document, Excel spreadsheet, or PDF can be frozen in place, preserving its metadata, permissions, and location while reclaiming active storage space. But the shiny new capability comes with a list of gotchas that every IT administrator needs to read before letting users loose with the Archive button.

From Whole Sites to Single Files: How It Works

On any SharePoint site where file-level archiving is enabled, users with edit permission see a new Archive action when they select a file. Clicking it instantly moves the document into an archived state. The file remains visible in the library—you can see its name, icon, and metadata—but you can’t open it, preview it, or read its contents until you explicitly reactivate it.

Microsoft designed the feature for granularity. A busy project site can keep live proposals and working drafts active while older deliverables, closed-case records, or exported reports are shifted to lower-cost archive storage. There’s no need to move them to a separate document repository or risk losing SharePoint’s access controls and compliance hooks. The data stays right where it belongs, just in cold storage.

Folder-level actions are also supported—with a twist. Archive a folder, and every file inside it (and all its subfolders) gets archived recursively. The folders themselves, however, don’t receive an archive state. They’re just containers. Reactivating a folder works the same way, thawing all files nested inside.

Importantly, recently archived files can be reactivated immediately. Microsoft’s documentation doesn’t define “recently,” but the practical implication is clear: if a user accidentally archives the wrong quarterly report, they can undo the action right away without waiting for a backend process. For older archives, reactivation may take longer.

What You Can (and Can’t) Archive

File-level archiving isn’t a universal switch. Microsoft has drawn explicit boundaries around what qualifies.

Files you can archive:
- Standard Office documents (Word, Excel, PowerPoint)
- PDFs, images, and other common file types stored in document libraries
- Any file in a non-excluded location where you have edit rights

Files you cannot archive:
- OneNote notebooks
- SharePoint pages (the modern pages that make up your site’s structure)
- SharePoint agents (the AI-powered assistants)
- Files in the Site Assets library, which stores images, scripts, and other site-resource files

Those exclusions make sense operationally—archiving a live page would break navigation, agents are still experimental, and Site Assets are typically needed for site rendering—but they guarantee that the feature won’t quietly cripple a site if a well-meaning employee archives something critical.

The Admin Playbook for File-Level Archiving

If your tenant has Microsoft 365 Archive enabled, file-level archiving is on by default. That means every SharePoint site in your organization could already offer users the Archive option unless you’ve deliberately shut it off. For admins, the first order of business is a review of the following settings.

Check your tenant’s archive configuration. File-level archiving becomes active only when Microsoft 365 Archive itself is turned on. If you’ve never touched archive settings, now is the time to visit the admin center and confirm the toggle. Without the Archive service, the file-level actions won’t appear.

Control availability per site. Through SharePoint Online PowerShell, you can disable file-level archiving for individual sites by setting the AllowFileArchive property to false. You can also change the default for newly created sites, ensuring that only approved collaboration spaces get the feature. Admins can audit archive consumption with the ArchivedFileDiskUsed property, which reports how much storage a site has parked in the archive tier.

Understand the storage math. This is where many organizations will trip up. Archived files still count against a site’s storage usage and quota. If a site is close to its 25 TB limit, archiving files doesn’t buy it more headroom. At the tenant level, the data is reclassified from active SharePoint storage to archived storage, which likely carries a lower per-gigabyte cost, but the tenant’s total consumption doesn’t drop. Microsoft’s FAQ explicitly warns that “archived files continue to count toward a site’s storage usage and quota.” Plan accordingly.

The 30‑day re‑archive lockout. A reactivated file cannot be archived again for 30 days. This stops users from ping-ponging documents between tiers and racking up transaction costs. But it also means that if a user reactivates a file to check a single paragraph and then wants to put it back into cold storage, they’re stuck waiting a month. Inform your teams so they don’t treat archiving like a temporary “sleep” mode.

Client and service gaps. Microsoft’s preview documentation flagged incomplete support across its own ecosystem. Word and PowerPoint for the web, Teams, mobile apps, and macOS OneDrive sync all had limitations. While the general availability release may have closed some of those holes, IT teams should validate current behavior in their tenant before rolling out the feature widely. A file that looks safely archived in a browser might still behave unpredictably in a desktop client—or trigger sync errors for users running older Office builds.

What This Means for Your Organization

For content managers and records officers, file-level archiving is a long-awaited tool. Instead of creating sprawling “archive” subsites or writing custom retention scripts, they can now let SharePoint handle dormancy at the items level. The metadata stays alive, so search and audit operations still see the file; only its contents are frozen. That keeps compliance happy while clearing active dashboards.

For end users, the experience is straightforward: select a file, click Archive. But the real benefit is emotional—no one has to decide whether an entire team site is “done.” That project folder from 2023 can keep its living documents while the signed contracts from that year go to sleep.

For IT, the calculus is more complex. The cost savings from tiering data to archive storage are real, but they depend on how Microsoft bills for archived consumption versus active storage. If you’re already paying for SharePoint storage in fixed blocks, moving a few gigabytes to archive may not change your invoice. In elastic pricing models, the difference could add up quickly. Do the math with your licensing provider before promising any budget relief.

There’s also a governance dimension. File-level archiving is a user-initiated action—anyone with edit rights can archive a file. That democratization is powerful but risky. Without clear policies, you might find critical standard operating procedures archived because a new hire thought they looked “old.” Microsoft leaves the guardrails to you.

How We Got Here

Microsoft 365 Archive has been evolving since its initial launch, which focused on site-level archiving. That earlier capability allowed you to put an entire SharePoint site into a read‑only, lower-cost state, effectively pausing it. But for many organizations, a whole-site approach was too blunt. A legal department might want to preserve case files while still updating its internal wiki; an engineering group might store old design documents alongside current specs on the same team site.

The demand for file-level granularity grew alongside the broader industry push toward records management automation. Competitors like Box and Egnyte already offered file-level retention and archiving, and SharePoint’s built-in retention labels, while powerful, often confused users who just wanted a simple “archive” button. Roadmap item 477371 addressed that gap, moving from preview to general availability in July 2026.

What to Do Now

If you’re an IT administrator or SharePoint owner, here’s your action plan.

  1. Confirm your tenant’s Microsoft 365 Archive status. Log into the admin center and check that the Archive service is active. If it’s not, file-level archiving won’t appear anywhere.
  2. Audit critical sites. Use PowerShell to review the AllowFileArchive property on sites that host business-critical content. For those, consider disabling the feature until you’ve trained users and set guidelines.
  3. Test in a sandbox site. Archive a few innocuous files and then reactivate them. Note how long reactivation takes, and check whether users on mobile or in Teams see any anomalies.
  4. Draft a communication plan. Tell your SharePoint users what archiving means, what they can archive, the 30‑day lockout rule, and how to request reactivation if needed. Emphasize that archiving is not deletion—the file stays in place, just frozen.
  5. Review storage billing. Ask your Microsoft account team how archived storage is priced in your agreement. If savings are possible, create a policy encouraging routine archiving of stale files; if not, focus on the operational benefits of a cleaner library.
  6. Set up reporting. Monitor ArchivedFileDiskUsed across sites to spot unusual patterns and ensure the feature is being used as intended.

Outlook

File-level archiving is a foundational step, not a final destination. As Microsoft weaves its Copilot agents deeper into SharePoint, expect smarter archiving recommendations—perhaps an AI that flags files untouched for 18 months and offers to archive them automatically. The roadmap also hints at tighter integration with Microsoft 365 Backup and extended client support for archived files in native apps.

For now, the feature gives businesses a surgical tool to manage SharePoint bloat. Used wisely, it reduces noise without breaking the familiar library experience. Used recklessly, it can freeze files at inopportune moments and leave confused users in its wake. The difference is entirely in how you administer it.