SharePoint File-Level Archiving Hits GA: The July 2026 Admin Guide

0

SharePoint file-level archiving officially reached general availability in July 2026, and it quietly changed the storage math for every Microsoft 365 tenant. For the first time, admins can push individual files — not entire sites — into Microsoft 365 Archive’s cold tier, keep them fully discoverable, and pay a fraction of the standard overage rate. However, the feature ships with a few sharp edges around quotas, app compatibility, and reactivation locks that will trip up any team that flips the switch without a plan.

This guide breaks down what SharePoint file-level archiving actually does, how to configure it, and the gotchas Microsoft buried in the fine print of message MC1381114.

What SharePoint File-Level Archiving Actually Is

Microsoft 365 Archive is Microsoft’s cold storage tier for SharePoint. Until this year, it worked only at the site level: you archived an entire site, users lost access, and the site’s data moved to cheaper storage. That was fine for retired projects, but useless for the far more common problem of stale files inside otherwise active libraries.

SharePoint file-level archiving fixes that gap. Now, admins and end users with the right permissions can archive individual documents from any supported SharePoint site. Archived files remain visible in search results, eDiscovery, and Purview content search. Consequently, the file stays “on the shelf” for compliance and knowledge purposes while its bytes move to a cheaper tier.

Microsoft published the general availability notice as MC1381114, with rollout beginning early July 2026 and completing worldwide (including GCC) by late July. For tenants that already have Microsoft 365 Archive enabled, the feature turns on by default.

[IMAGE NEEDED: Microsoft 365 Archive overview diagram from learn.microsoft.com showing hot vs. cold tier for SharePoint sites and files]

Why Microsoft Built SharePoint File-Level Archiving

The business case is simple: most SharePoint libraries contain a heavy tail of old files that nobody edits, but nobody wants to delete either. Compliance teams need them retrievable. Business owners fear losing them. Meanwhile, storage bills grow every quarter.

Before file-level archiving, admins had three unattractive options. Firstly, they could archive entire sites, which broke user access. Secondly, they could pay the standard overage rate on stale content. Thirdly, they could migrate the tail to a separate archive tenant or third-party tool. Each option added complexity or cost.

File-level archiving offers a fourth path. Additionally, because Copilot is not trained on archived content, cold-tiering unused files also sharpens Copilot response quality by removing outdated noise from the retrieval pool. As a result, this feature is as much a Copilot governance play as it is a cost play.

The New Storage Math: $0.05 vs. $0.20 per GB

Here is the number that will get every finance team’s attention. Files in the SharePoint file-level archiving cold tier cost $0.05 per GB per month. In contrast, the standard SharePoint storage overage rate is $0.20 per GB per month. That is a 75% reduction on the archived portion of your storage footprint.

For a tenant sitting 5 TB over its allocated quota with 3 TB of that footprint eligible for archive, the monthly savings math looks like this:

  • Without archiving: 5,000 GB × $0.20 = $1,000/month in overage.
  • With 3 TB archived: (2,000 GB × $0.20) + (3,000 GB × $0.05) = $400 + $150 = $550/month.
  • Annual savings: approximately $5,400.

Multiply that across large enterprise tenants and the number quickly justifies a formal archiving program. However, the savings only materialize if you actually reduce active hot-tier consumption — which is where the biggest gotcha comes in.

The Storage Quota Caveat Every SharePoint Admin Should Understand

Read this section twice. Archived files still count toward site storage quotas. Microsoft’s own documentation is explicit: “File-level archive doesn’t change site storage usage or quota behavior. Archived files are accounted for in site storage the same way as active files.”

In other words, if a site is bumping against its quota, archiving files inside it will not create headroom for new uploads. The billing tier changes, but the quota accounting does not. This is different from site-level archiving, where the entire site’s storage moves out of the tenant’s active pool.

Consequently, file-level archiving is a billing optimization, not a capacity relief valve. If your problem is “we are out of SharePoint storage,” this feature will not fix it. For quota relief, admins still need to archive whole sites, move content to a separate site, or purchase additional storage.

[IMAGE NEEDED: Screenshot of Microsoft 365 admin center pay-as-you-go billing configuration page from learn.microsoft.com]

Configuring SharePoint File-Level Archiving in Your Tenant

To use SharePoint file-level archiving, three prerequisites must be in place. First, Microsoft 365 Archive must be enabled for the tenant. Second, pay-as-you-go billing must be configured in the Microsoft 365 admin center — this is how Microsoft meters the $0.05/GB rate. Third, the tenant must have a linked Azure subscription for the pay-as-you-go charges.

Once those are in place, the feature is on by default. If you would rather not expose the Archive action across every site — for example, during a controlled pilot — use PowerShell to scope it. The relevant SharePoint Online Management Shell cmdlet is:

# Disable file-level archive across the whole tenant
Set-SPOTenant -AllowFileArchive $false

# Or scope it per site (once feature parity ships)
Set-SPOSite -Identity https://contoso.sharepoint.com/sites/finance -AllowFileArchive $true

Only SharePoint Administrators or Global Administrators can manage archive settings. Furthermore, Microsoft recommends using SharePoint Administrator rather than Global Administrator wherever possible, in line with least-privilege guidance.

Permissions and Governance for SharePoint File-Level Archiving

The permission model for SharePoint file-level archiving is fixed and cannot be reconfigured. Specifically, three roles matter:

  • Edit or Contribute permission: can archive a file.
  • Read permission: can reactivate an archived file.
  • SharePoint Administrator or Global Administrator: can toggle the feature on or off.

The read-permission-to-reactivate rule is deliberate. Microsoft wants any user who could have opened the file before it was archived to be able to bring it back. Additionally, this prevents scenarios where a file gets stranded because the person who archived it left the organization.

From a governance perspective, this permission model means end users can archive files on their own. Consequently, records management and helpdesk teams should be looped in before enabling the feature broadly. Users need clear guidance on when to archive versus when to delete, and helpdesk agents need a reactivation runbook for the inevitable “I archived it by mistake” tickets.

Reactivation Times, Fees, and the 120-Day Lock

Reactivation timing depends on how long the file has been archived. Files archived within the past seven days reactivate instantly. Beyond that window, reactivation can take up to 24 hours. However, there is no per-reactivation fee — Microsoft removed those fees back in March 2025 — so admins can plan reactivations without a per-transaction cost worry.

The important trap is the re-archive lock. Once a file is reactivated, it cannot be archived again for 120 days. Some earlier third-party coverage cited a 30-day lock; Microsoft’s official documentation now states 120 days. Therefore, teams should treat reactivation as a considered action, not a casual undo. Bouncing a file in and out of the archive is not possible on a monthly cadence.

[IMAGE NEEDED: Screenshot of the Archive/Restore action in the SharePoint document library ribbon from techcommunity.microsoft.com]

What SharePoint File-Level Archiving Doesn’t Support

Microsoft is upfront that not every application handles archived files gracefully yet. Admins should treat the following as known limitations for now:

  • Word and PowerPoint on the web may fail to open archived files cleanly.
  • Teams, OneDrive, and SharePoint mobile apps can display incorrect error messages when they encounter archived content.
  • The macOS OneDrive sync client is not fully aware of archived state.
  • Windows 10 and older OneDrive sync builds also lag on archive awareness.
  • Office desktop apps not updated since March 1, 2026 may misbehave on archived files.
  • Clipchamp and Power BI fail to import archived content.
  • OneNote notebooks, SharePoint pages, SharePoint agents, and the Site Assets library cannot be archived at all.

These limitations shape the rollout strategy. In particular, if your organization has a large macOS population or lags on Office update rings, communicate the feature and reactivation flow before archiving anything that active users might still touch.

How SharePoint File-Level Archiving Fits Into Copilot Governance

Microsoft 365 Copilot uses SharePoint content as one of its primary retrieval sources. As a result, the quality of Copilot answers depends heavily on the quality — and freshness — of the underlying documents. Older files that are technically still in libraries can push Copilot toward outdated policies, superseded pricing, or stale product info.

Copilot is explicitly not trained on archived content. Therefore, archiving stale files is a fast, low-risk way to raise Copilot response relevance without touching permissions, sensitivity labels, or restricted content discovery. It complements — rather than replaces — the governance work already underway with tools like Restricted Content Discovery and the SharePoint Advanced Management stack.

Moreover, this ties file-level archiving into the broader story of Copilot readiness that most Microsoft 365 shops are running through in 2026. It is a cheap, reversible lever to pull.

A 6-Step Plan to Roll Out SharePoint File-Level Archiving

For admins ready to move, this sequence keeps the rollout controlled:

  1. Confirm pay-as-you-go billing. Verify the Azure subscription is linked in the Microsoft 365 admin center and that pay-as-you-go is switched on for SharePoint.
  2. Baseline your storage. Use SharePoint admin reports and Microsoft 365 usage analytics to identify sites with the largest cold tails — files unmodified for 12+ months are prime candidates.
  3. Disable at the tenant level, then enable per site. Run Set-SPOTenant -AllowFileArchive $false, then enable it on a small pilot site with a cooperative business owner.
  4. Publish a user guide. Cover how to archive, how to reactivate, what applications do not yet support archived files, and the 120-day re-archive lock.
  5. Update helpdesk runbooks. Add a “user says file is missing” flow that checks archive state before treating it as data loss.
  6. Measure and expand. After 30 days, compare pay-as-you-go archive charges against the site’s previous overage line. If the delta is positive, expand to the next wave of sites.

[IMAGE NEEDED: Chart comparing $0.20 hot-tier overage vs. $0.05 file-level archive tier for a typical enterprise tenant]

What This Means for SharePoint Admins in 2026

SharePoint file-level archiving is the kind of feature that looks incremental in a message center post but reshapes an operational category. For years, “stale files” have sat in the too-hard basket, either burning overage money or triggering risky bulk-delete projects. Now, admins have a reversible, cheap, compliance-friendly middle path.

The catches — quota accounting stays the same, app support is uneven, and reactivated files stay hot for 120 days — matter, but none are dealbreakers. Instead, they shape how you communicate and pilot the feature. Admins who move deliberately in July and August 2026 will be well positioned when finance asks the inevitable Q4 question about SharePoint cost trends.

For more Microsoft 365 admin guides, Copilot governance breakdowns, and SharePoint operational deep-dives, keep an eye on SharePoint Monkey. Additionally, check out our recent coverage of Microsoft 365 Copilot Watermarks and Restricted Content Discovery for the two other governance levers every SharePoint admin should be pulling this quarter.

Sources

Discover more from SharePoint Monkey

Subscribe to get the latest posts sent to your email.