Microsoft 365 Archive: what it does, how it works and whether it's worth it

Microsoft 365 Archive has been positioned as Microsoft's answer to the ever-growing storage problem inside Microsoft 365 tenants. The pitch is clean: instead of paying full active storage rates on sites that nobody uses anymore, you move them to a cheaper archived tier and pay less. Simple enough in theory. In practice, there are real operational trade-offs that admins should understand before treating this as a quick win on storage costs.

This article covers what Microsoft 365 Archive is, how it works technically, its real limitations, where it genuinely helps, and where you might be better off looking elsewhere.

Microsoft 365 Archive is a Microsoft-managed archiving feature for SharePoint content. At its core, it allows tenant admins to move inactive SharePoint sites out of active storage into a lower-cost archived state, without deleting the content. The sites remain in the tenant, the data is preserved, and the content can be retrieved if needed.

For a long time, the unit of archiving was the entire SharePoint site. That is still the primary, generally available workflow. However, Microsoft has been expanding the feature scope: file-level archiving is currently in public preview as of early 2026, meaning you can archive individual files within SharePoint and not just whole sites. This is a meaningful shift in what the product can do, though the file-level capabilities should be evaluated before building operational processes around them.

The feature is available through the SharePoint admin center. Management can also be handled via PowerShell tools, giving admins flexibility in how they identify and process content for archiving, whether that is a list of dormant sites or, in preview, specific files within active libraries.

How Microsoft 365 Archive works

When you archive a site through Microsoft 365 Archive, it moves from active SharePoint storage to an archived storage tier. Here is what that means operationally: 

• The site is no longer accessible to end users by default. Anyone trying to open it will see a message indicating the site is archived.
• The content is still stored and preserved, it is not deleted.
• Archived storage is billed at a lower rate than active SharePoint storage. 
• Admins can reactivate archived sites. When reactivation is triggered, there is a warm-up period before the site becomes fully accessible again. This is not instant.
• The admin retains control over which sites are archived and which are reactivated, via the SharePoint admin center or PowerShell.

For file-level archiving the mechanics will work at the individual file scope within a SharePoint library. An archived file is moved out of active storage and becomes inaccessible to users in place, similar to site-level archiving but without taking the whole site offline. Reactivation at the file level follows the same principle: admin-initiated, with a delay before the file is accessible again. During the preview period, admins should treat it as a capability to watch and test, not something to build critical workflows around just yet.

From a governance standpoint, archived content remains subject to your existing retention policies and compliance configurations in Microsoft Purview. Archiving does not remove content from the scope of eDiscovery or legal hold. If content is under a retention policy, that policy still applies in the archived state.

Setup itself is relatively lightweight. You enable the feature in the Microsoft 365 admin center and manage archiving operations from the SharePoint admin center. PowerShell (PnP PowerShell and the SharePoint Online Management Shell) is available for bulk operations and automation scripting. There is no complex agent deployment or infrastructure to configure.

Storage cost reduction. If your tenant is carrying a significant amount of inactive SharePoint storage, moving those data to the archived tier reduces your per-GB cost meaningfully. For organizations that have accumulated years of project sites, departmental sites, and abandoned collaboration spaces, this can add up.

Content preservation without deletion. One of the persistent problems with SharePoint lifecycle management is that admins often face a binary choice: keep everything active and pay for it, or delete it and risk losing something important. Microsoft 365 Archive introduces a middle tier. The content survives, policy coverage continues, and the cost is lower.

Expanding granularity. Site-level archiving covers the broad lifecycle scenario well. The file-level archiving capability will extend that logic to a more surgical level. What is useful for active sites that contain a mix of current and dormant content within the same library. 

Compliance continuity. Because archived data remain in the tenant and under existing retention and compliance configurations, you do not lose governance coverage by archiving. This matters for regulated industries and organizations with active legal or compliance obligations.

Admin-controlled reactivation. Admins can bring archived data back when needed. This is not a one-way operation, which removes some of the anxiety around archiving sites that might occasionally be needed.

 Flexible management tooling. Between the SharePoint admin center UI and PowerShell support, admins have practical options for both manual management and scripted bulk operations. 

File-level archiving is still in preview. Site-level archiving is generally available and production-ready. File-level archiving, the ability to archive individual files within SharePoint libraries, is in public preview as of early 2026. That means it is not yet GA, feature behavior may still change, and it should not be the foundation of production workflows until it reaches general availability. Watch the roadmap closely if this is a key requirement.

Reactivation is not instant. When you need content from an archived site or file, you initiate reactivation and wait. Microsoft does not publish a hard SLA for this warm-up period, but it is not a matter of seconds. For scenarios where users might occasionally need archived content quickly, this latency is a real operational consideration.

Users cannot self-serve. End users cannot request or trigger reactivation themselves. It requires admin action. Depending on your support model, this creates a workflow dependency that needs to be planned for.

Cost is additive. Archived storage costs less than active storage, but it is not free. If you are already within your included storage allocation, archiving inactive content adds cost rather than reducing it. The economics only work in your favor if you are paying for storage overage or have a significant volume of content to move out of active storage.

Limited automation at launch. Microsoft 365 Archive does not include built-in automated lifecycle policies, for example, automatically archiving any site that has been inactive for 12 months. You identify and select content for archiving manually, or build that logic yourself via PowerShell or a third-party tool. This is a gap worth noting if you are hoping for a zero-touch lifecycle engine out of the box.

Not a replacement for a real archiving strategy. Microsoft 365 Archive solves specific problems cleanly within its scope. It does not replace a broader information governance approach, records management configuration, or retention policy framework.

This is the practical question most admins face when cleaning up inactive data: archive or delete?

Deleting a SharePoint site removes the content. It goes to the site collection recycle bin for a period, then it's gone. It stops counting against storage immediately. It costs nothing to keep deleted.

Archiving preserves the content at a lower cost tier. You keep access to that content for compliance, historical reference, or potential reactivation. You continue paying for it, just less.

The decision comes down to whether the content has ongoing value, compliance, legal, historical, or business continuity, or whether it is truly safe to delete. If content has no retention requirement, no legal hold, and no foreseeable future use, deletion is often the cleaner and cheaper outcome. If you are not certain, or if compliance obligations exist, archiving is the safer call.

Do not treat archiving as a substitute for making hard decisions about what to keep. Archive what you need to preserve. Delete what you genuinely do not. The worst outcome is paying for archived storage indefinitely on content that should have been deleted.

• If you need production-ready file-level archiving right now and cannot wait for the feature to reach general availability, you will need to look at retention labels, Microsoft Purview records management, or a third-party archive solution in the meantime.
• If your storage problem is within active sites and you need something more sophisticated than what the current preview offers, a dedicated governance platform will give you more control.
• If you need fast access to archived content without admin intervention, the reactivation latency and process may not meet your needs.
• If your inactive sites have no compliance or legal hold requirement and simply represent old content, a proper deletion process with appropriate recycle bin management is faster and cheaper.
• If you need automated, policy-driven lifecycle management, you will need to layer additional tooling or scripting on top of Microsoft 365 Archive, or evaluate a purpose-built governance platform.

Microsoft 365 Archive can be a good solution for reducing storage space. A lack of storage space is a particularly important issue for large organizations. When it comes to saving on the enormous costs of storage or archiving, ShArc is a good solution. In addition to cost savings of at least 61% on extra storage, the tool offers end users restore and automated policy based archiving.