Microsoft 365 Now Lets You Archive Individual SharePoint Files — Here's What It Means for You

If your SharePoint environment is anything like most organizations', a significant share of what is stored there has not been touched in years. Completed project folders, old versions of templates, documents from initiatives that ended long ago, reference materials nobody opens — all of it sitting in active storage, consuming quota, showing up in search results, and influencing what Microsoft Copilot surfaces when your team asks questions.

Until recently, Microsoft 365 Archive could only solve this problem at the site level: archive an entire SharePoint site, take everything offline, or leave it all active. For sites with a mix of old and current content — which describes most real-world SharePoint environments — that was not a practical option.

That changed on March 30, 2026. Microsoft released file-level archiving for Microsoft 365 Archive in public preview. You can now archive individual files within an active SharePoint site, moving them to a cold storage tier at a fraction of the cost — while the rest of the site stays fully active. General availability is targeted for July 2026, with policy-based automatic archiving expected later in the year.

This is a meaningful improvement in how Microsoft 365 handles storage lifecycle management. Here is what it actually does, what it costs, and what your organization should be thinking about.

What File-Level Archiving Actually Does

Microsoft 365 Archive has been available since May 2024, but it only worked at the site level — you could archive an entire SharePoint site, moving all of its content to cold storage. That made it useful for clearly concluded projects or decommissioned sites, but not for the more common scenario: a SharePoint site that is still actively used but contains a large amount of dormant historical content alongside the active files.

File-level archiving solves this. When you archive an individual file in a SharePoint document library, that file moves to a cold storage tier within Microsoft 365. The site stays active. Other documents in the same library stay accessible and editable. Users can still see the archived file in its original location — it shows up with a distinct archive icon overlay — and any user with read access can reactivate it when needed.

What gets preserved when a file is archived

• All file metadata — title, author, tags, properties — is retained exactly as it was
• Full version history is archived alongside the file and fully restored on reactivation
• All existing permissions carry through — the access controls set on the file before archiving remain intact
• Compliance and data governance coverage through Microsoft Purview remains active — archived content is still searchable by administrators using Purview and admin search, and all retention policies remain intact

What changes when a file is archived

• The file moves to cold storage and is no longer accessible to regular users without reactivation — they see the archive icon but cannot open the file directly
• The file is removed from Microsoft 365 Copilot's active index — it no longer influences Copilot responses
• The file is removed from standard SharePoint and Microsoft 365 search results for end users (though admins can still find it through Purview)
• The storage cost for that file shifts from the active SharePoint rate ($0.20/GB/month) to the archived rate ($0.05/GB/month)

💡  Reactivation is straightforward — any user with read access can reactivate an archived file directly from the SharePoint web interface. After a 7-day window, reactivation can take up to 24 hours. After reactivating, there is a 30-day cooldown before the same file can be archived again.

The Storage Cost Question — What This Does and Does Not Change

The pricing is simple: archived storage is charged at $0.05/GB per month, compared to $0.20/GB per month for active SharePoint storage. That is a 75% reduction in cost per gigabyte. Microsoft frames this as saving up to 75% compared to purchasing additional SharePoint storage.

However, there is an important nuance that is easy to misunderstand, and getting it wrong will lead to unexpected results:

⚠️  File-level archiving does not reduce your total storage consumption — it reclassifies it. Archived files still count toward your tenant's total storage. The difference is that archived storage is billed at the lower rate instead of the active storage rate. If your SharePoint site is hitting its storage quota, archiving files will not free up site-level space. The quota relief happens at the tenant level only.

What this means in practice:

• The benefit is a lower monthly bill for storing data you need to retain but rarely access. Not a way to make room for new content within a constrained storage quota.Cost reduction, not capacity expansion:
• Archived storage is only charged when your tenant has exceeded its included storage quota. If your total active and archived storage stays within your licensed allocation, there are no additional charges at all — the archiving benefit is still realized through better Copilot and search relevance, even if the cost saving is not immediate.Only applies beyond your licensed allocation:
• Microsoft 365 Archive runs on a pay-as-you-go billing model tied to an Azure subscription. This needs to be configured before the feature is available. Always Beyond can help you set this up if it is not already in place.Pay-as-you-go billing required:

The Copilot Angle — Why This Matters Beyond Storage Costs

For organizations that are using — or preparing to use — Microsoft 365 Copilot, file-level archiving has a benefit that goes beyond storage billing: it improves the quality of Copilot's responses.

Microsoft 365 Copilot draws on your SharePoint content when generating responses. A SharePoint environment filled with outdated proposals, expired contracts, superseded policy documents, and legacy project files gives Copilot a noisy, low-quality pool to draw from. Copilot does not know that the 2019 version of a strategic plan is outdated — it just sees a document that looks relevant to a query about strategy.

Archived files are excluded from Copilot's active index. This means archiving old content directly improves the relevance of what Copilot surfaces — without requiring any model configuration, retraining, or Copilot-specific settings.

✅  If your Copilot responses are surfacing outdated proposals, legacy project documents, or old reference materials, archiving that content is one of the fastest ways to improve relevance. It removes the noise from Copilot's source pool without deleting anything or changing any Copilot settings.

Site-Level vs. File-Level: Choosing the Right Tool

Microsoft 365 Archive now supports two distinct archiving approaches, and they serve different use cases. Understanding when to use each one helps you build a practical archiving strategy rather than applying the same approach everywhere.

For most organizations, the practical archiving strategy will use both: site-level archiving for sites where the work is genuinely concluded, and file-level archiving for active sites carrying years of accumulated historical content.

What You Can — and Cannot — Archive Right Now

During the public preview, there are limitations to be aware of before rolling this out:

Supported

• Individual files in SharePoint Online document libraries
• Folders — you can select a folder and choose to archive all files within it
• All file types except: OneNote notebooks, SharePoint pages, and SharePoint agents
• Files on group-connected sites (Teams-connected SharePoint sites)

Not yet supported or limited

• OneDrive files — file-level archiving is currently SharePoint Online only. OneDrive is not supported in the current preview.
• Teams channel sites — private and shared channel sites cannot be archived
• Clipchamp and Power BI — these applications fail entirely when trying to import or open archived content. Do not archive files that are regularly pulled into Power BI reports or Clipchamp without a plan for user communication.

App compatibility during public preview

This is the most important operational consideration before rolling out file-level archiving. Several common Microsoft 365 applications do not yet display a clear 'this file is archived' message when a user tries to open an archived file. Instead, they show generic or confusing error messages:

• Word Online and PowerPoint Online — show generic error messages instead of indicating the file is archived
• Microsoft Teams — does not display the archive state clearly
• OneDrive mobile app and SharePoint mobile app — do not surface the archive status
• OneDrive sync client on macOS and Windows 10 — limited archive state visibility

🚨  Before enabling file-level archiving and letting users archive content, make sure your team knows what to expect when they encounter an archived file. Users who try to open an archived document in Teams or Word Online will see an error — not a helpful 'this file is archived, click here to reactivate' message. Microsoft is working on this before GA, but during preview it requires proactive user communication.

What to Archive: A Practical Framework

The most common question when file-level archiving is enabled is simply: where do I start? Microsoft notes that files not accessed in more than two years have a greater than 95% probability of never being accessed again. That is a useful baseline for identifying candidates.

Strong candidates for archiving

• Files in a document library that have not been opened in 12–24 months or more
• Completed project deliverables on active team sites — final reports, handoff documents, archived proposals that were accepted and delivered
• Older versions of templates and policies that have since been replaced — still needed for audit trail, but not in active use
• Reference documents from concluded initiatives — background research, analysis files, vendor assessments from decisions that have already been made
• Large media files (presentations, video recordings, training materials) from past sessions that are no longer in active rotation

Files to be cautious with

• Anything regularly imported into Power BI dashboards or reports — archiving will break those imports
• Source files for recurring deliverables — if a document gets updated quarterly, archive the old versions but leave the current one active
• Files referenced in SharePoint pages or embedded in Teams tabs — the reference will break when the file is archived
• Anything accessed via the OneDrive sync client on older Windows devices — the archived state may not display correctly

✅  Start with a pilot: identify one or two document libraries where the content is clearly historical, enable the feature for those sites, archive a test batch, and verify user experience before rolling out organization-wide. Always Beyond can help you identify the highest-impact sites to start with based on your SharePoint usage data.

The Roadmap: What Is Coming Next

File-level archiving in public preview is the first step in a broader storage lifecycle management capability Microsoft is building out through 2026:

The late-2026 policy-based automation is significant. Right now, archiving is either done manually by users or triggered by admins through PowerShell. Once you can define rules — archive anything in this library not opened in the past two years — the ongoing maintenance of your SharePoint storage lifecycle becomes largely automatic.

Important Limitations to Understand Before You Enable It

• Microsoft 365 Archive is not a replacement for a backup. Archived files are still only stored within Microsoft's infrastructure — not an independent copy you control. If a file is deleted from archived storage and the recycle bin expires, it is permanently gone. You still need a separate backup solution to protect against accidental deletion.Not a backup solution:
• If a specific SharePoint site is hitting its storage limit, archiving files from that site will not fix the quota problem. Site-level storage calculations are not changed by archiving. The benefit is at the tenant level.Site storage quota is unaffected:
• If an archived file is copied or moved to another location, it stays archived. However, the archived state may not always be visually represented correctly in the OneDrive user interface.Archived files retain their archived state when moved:
• Compliance and legal hold protections remain in place for archived files — this is expected behavior, but worth noting for organizations managing active litigation holds.Files under legal hold cannot be deleted:

Frequently Asked Questions

Is file-level archiving available to all Microsoft 365 customers?

It requires Microsoft 365 Archive to be enabled, which runs on a pay-as-you-go billing model tied to an Azure subscription. You do not need any specific Microsoft 365 plan tier — the pay-as-you-go setup is what activates the capability. During the current public preview, it also requires a PowerShell command to enable for your tenant. At general availability in July 2026, it will be on by default for all tenants with Microsoft 365 Archive active.

Will my users know when they are looking at an archived file?

In the SharePoint web interface, yes — archived files show a distinct archive icon overlay. However, in several other Microsoft 365 apps during the current public preview — including Word Online, Teams, and mobile apps — the experience is not smooth. Users may see generic error messages rather than a clear 'this file is archived' indicator. Microsoft is working on improving this before general availability, but if you enable the preview now, it is important to communicate clearly with your users about what to expect.

Can any user archive files, or is it admin-only?

With file-level archiving, it is not admin-only. Site members and owners can archive individual files themselves, directly from the SharePoint web interface. This is one of the key design differences from site-level archiving, which is admin-only. Admins retain control over whether the feature is enabled at the tenant and site level, and can disable it per site if needed.

Does archiving a file affect its compliance coverage?

No. Archived files retain full coverage under Microsoft Purview — retention policies, eDiscovery, audit logging, and compliance features all continue to apply to archived content. Administrators can still find and access archived files through Purview and admin search. The archiving changes how the file is stored and billed; it does not change its compliance standing.

Should we wait for GA in July 2026 or enable the preview now?

For most organizations, waiting for GA is the more pragmatic choice. The preview has meaningful gaps — specifically around app compatibility and the user experience when encountering archived files in Teams and Word Online. If your IT team wants to get ahead of the configuration and test archiving behavior in a pilot site, the preview is available and usable. But broad user-facing rollout before July 2026 requires careful communication planning to manage the error message experience. Always Beyond can help you assess readiness and plan the rollout.

What This Means for Your Microsoft 365 Environment

File-level archiving closes a gap that has existed in Microsoft 365 storage management since the beginning. Until now, the choice was binary: keep everything active, or archive an entire site. For organizations with complex, long-lived SharePoint environments — which is most organizations that have been on Microsoft 365 for more than a few years — neither option served the real need.

The ability to archive individual files at a 75% cost reduction, while keeping the site active and improving Copilot relevance in the process, is a meaningful step forward. The storage cost savings are real but secondary. The Copilot quality improvement, the cleaner search results, and the foundation for policy-based lifecycle management later this year are the more significant longer-term benefits.

General availability arrives in July 2026. Now is a good time to assess your SharePoint environment, identify the highest-value archiving opportunities, and make sure your billing and infrastructure prerequisites are in place before the feature enables by default.

Want to know what file-level archiving could mean for your SharePoint environment? Always Beyond can assess your current SharePoint storage usage, identify the highest-value archiving opportunities, and set up Microsoft 365 Archive for your tenant — including the pay-as-you-go billing configuration and initial pilot rollout. Reach out to start the conversation.