Microsoft’s SharePoint Online now includes file-level archiving for every site that has Microsoft 365 Archive enabled—and it’s turned on by default. Any employee with edit permissions can archive a document, pushing it into cold storage where it may take up to 24 hours to become accessible again. For organizations that haven’t prepared governance, training, or support workflows, this sudden default creates an immediate permissions and retrieval challenge, not merely a new storage toggle.

The Feature That Arrived On by Default

File-level archiving is the latest addition to Microsoft 365 Archive, a service designed to move inactive SharePoint content to cheaper cold storage. Microsoft made the feature generally available through a phased rollout that began in mid-2024 and accelerated with Roadmap item 477371. The documentation is clear: once an administrator enables Microsoft 365 Archive for the tenant and configures pay-as-you-go billing,

every SharePoint site defaults to allowing users to archive individual files.

Users with edit rights see an “Archive” action on the file menu. After archiving, the file can’t be opened or downloaded until someone reactivates it. Users with read access—even those who didn’t originally archive the file—can trigger reactivation. Microsoft states that reactivation may take up to 24 hours, with one exception: files archived within the previous seven days reactivate instantly.

Administrators have three PowerShell levers to control the feature, all of which default to $true (on).

  • Tenant-level kill switch: Set-SPOTenant -AllowFileArchive $false (requires SharePoint Online Management Shell version 16.0.26714.12000 or later) disables all new file archiving across the tenant but doesn’t affect existing archived files.
  • Site-level overrides: Set-SPOSite -Identity <site_url> -AllowFileArchive $true/false (needs version 16.0.26211.12000 or later) lets you re-enable archiving on specific pilot sites even when the tenant toggle is off.
  • Defaults for new sites: Set-SPOTenant -AllowFileArchiveOnNewSitesByDefault $false prevents future sites from automatically inheriting the archiving feature.

A fourth cmdlet, Get-SPOSite, now includes an ArchivedFileDiskUsed property that reports, in bytes, how much archive storage a site is consuming.

Microsoft also requires that pay-as-you-go billing be set up for the tenant and that the Microsoft 365 Archive service itself be enabled. Without both prerequisites, the archive controls won’t function even if the PowerShell flags are set to $true.

Why Uncontrolled Archiving Is an Admin Problem

At first glance, file-level archiving looks like a welcome housekeeping tool—users can tidy up old documents and reduce active storage costs. But the immediate side effects turn it into a governance, support, and compliance issue that IT must address before the first employee clicks Archive.

Permissions carry an unexpected weight. The same edit permission that lets a colleague update a budget spreadsheet now lets them make that spreadsheet inaccessible for up to a day. A project manager may archive a final draft thinking the work is done, while another team member still needs it as a template for the next quarter. A contributor might archive incident-response guides because they appear unchanged, not realizing operations depends on immediate access.

Retrieval delays create helpdesk calls. Users who encounter a “file archived” message will contact support. Unless the helpdesk has a clear script—pointing users to the reactivation process in SharePoint Online and explaining the time window—tickets multiply. Worse, the seven-day instant-reactivation grace period can mask the real experience: a file archived weeks ago will genuinely take up to 24 hours to return, causing frustration during audits, financial close, or urgent meetings.

Compliance workflows can break. Microsoft notes that retention labels and eDiscovery still apply to archived files, but that doesn’t mean those processes run at the speed legal teams expect. A compliance officer who needs to collect evidence for a security incident or a litigation hold may discover that key documents are in a “reactivating” state. The preserve-and-hold logic remains intact, but practical access is delayed. Organizations with strict SLAs around legal hold execution or audit readiness should test exactly how eDiscovery behaves with archived files before allowing widespread use.

Billing can surprise you. Archive storage is cheaper than hot storage, but it’s not free. If hundreds of users begin archiving files across dozens of sites, the cumulative cost adds up—especially if the “archive” action is seen as a cleanup gesture rather than a cost-aware decision. Finance and IT need to review pilot results together, set alerts for unusual archive growth, and establish a baseline against which to measure savings.

The default puts you on a clock. Because AllowFileArchive and AllowFileArchiveOnNewSitesByDefault are set to $true, any site created after the feature lights up automatically gives users the Archive button. Put off governance, and you’ll face a growing fleet of sites where archiving is active and untracked.

How We Got Here

Microsoft 365 Archive launched as a site-level capability in 2023, letting administrators move entire SharePoint sites to cold storage. File-level archiving extends that concept downward, placing the same cold-storage logic directly in the hands of end users. Roadmap item 477371, first reported in early 2024, signaled the change, and the management cmdlets began appearing in SharePoint Online Management Shell updates through the spring. By the time the feature reached general availability in mid-2024, the on-by-default behaviour was baked into the service.

The move parallels broader industry trends toward tiered storage and “archive anything” philosophies, but it also reflects Microsoft’s push to make Microsoft 365 Archive a standard component of data lifecycle management. The same architecture now serves Government Community Cloud (GCC) and GCC High tenants, meaning public-sector entities face the same default-on challenge.

What’s missing from the rollout is a pause button in the admin center. The only way to stop file archiving is PowerShell, which raises the bar for smaller organisations or those without dedicated SharePoint administrators.

Step by Step: Taking Control of File Archiving

A safe rollout doesn’t start by flipping a tenant-wide switch. It starts by locking things down, then opening doors deliberately.

1. Confirm the Prerequisites

Before touching PowerShell, verify that your tenant has pay-as-you-go billing enabled and that Microsoft 365 Archive is active. You can check the Archive status in the Microsoft 365 admin center under Setup > Microsoft 365 Archive. If either isn’t configured, end users won’t see the Archive action regardless of the PowerShell flags, and you can proceed with planning without urgency.

2. Update the SharePoint Online Management Shell

Run Get-InstalledModule -Name “Microsoft.Online.SharePoint.PowerShell” to see your current version. You need at least 16.0.26714.12000 to use the tenant-level kill switch. If your version is lower, update the module: Update-Module -Name Microsoft.Online.SharePoint.PowerShell. Many administrative workstations still carry older versions from site-level deployments; don’t assume you’re current.

3. Disable Archiving Everywhere—For Now

Turn off file archiving across the tenant:

Set-SPOTenant -AllowFileArchive $false

This prevents any new archival actions but leaves existing archived files intact and reactivatable. Next, set the default for new sites to off:

Set-SPOTenant -AllowFileArchiveOnNewSitesByDefault $false

Now, even if you later re-enable archiving on select pilot sites, any future site created outside the pilot will stay locked down until you explicitly allow it.

4. Identify Pilot Sites and Define the Rules

Choose a small group of sites with clear business ownership and responsive site admins. Favour libraries that contain genuinely inactive content—old project archives, closed contracts, or completed reports—rather than active collaboration spaces. Exclude policy repositories, operational playbooks, and any library that feeds real-time reporting or incident response.

Create a simple governance document that answers:

  • What kinds of files are candidates for archiving (e.g., items not accessed in 12 months, documents with a “final” status label)?
  • Who is authorized to archive (all editors, or a designated records manager)?
  • Which libraries are strictly off-limits?
  • How a user should request reactivation if they don’t have read access (or if they need expedited retrieval)?

5. Enable Archiving on the Pilot Sites

For each approved site, run:

Set-SPOSite -Identity https://contoso.sharepoint.com/sites/pilotproject -AllowFileArchive $true

Remember that the site-level -AllowFileArchive flag takes effect only if the tenant-level flag is also $true. Since you’ve set the tenant flag to $false, these site overrides become the only places where archiving is allowed.

6. Train Users and the Helpdesk

Brief pilot users on the business rules, not just the Archive button. Emphasize what not to archive, and walk through the reactivation process step by step. Prepare a helpdesk script that covers the common scenarios: “How do I get my file back?”, “How long will it take?”, and “What if it’s been over a week?”. Include the guidance that the user should not recreate the document locally—doing so creates duplication and version confusion.

Testing Before You Trust the Archive Button

A successful pilot tests the entire journey, not just the moment of archiving. Create a set of test files that mirror real-world usage:

  • A rarely opened reference document that no one has touched in 12 months.
  • A file that is still linked from a team’s SharePoint homepage.
  • A PDF that is primarily accessed through the organization’s standard search.
  • An Office document that users routinely open in desktop Word or Excel.

For each file, have an editor archive it, then have a reader try to access it immediately (within the 7-day grace window) and again after a week. Document exactly what the reader sees when clicking a saved direct link, searching, or browsing the library. Check if alerts or error messages are clear enough for a non-technical user.

Then scale up the compliance test. Archive a test file with an active retention label, run a Content Search or eDiscovery export, and confirm that the file is listed and collectible. Some organizations have found that search previews for archived files may return a placeholder or differ from the live preview—your legal team will want to know what evidence they’ll receive during a real collection.

Finally, involve finance: pull the ArchivedFileDiskUsed value from each pilot site, compare it against active storage usage, and project what would happen if all eligible files were archived across the organization. Set up billing alerts in Azure Cost Management for the Microsoft 365 Archive meter, and agree on a threshold that triggers a governance review.

The Bottom Line

SharePoint file-level archiving is a useful addition for cold storage, but it should not be treated as a benign productivity tool. The combination of default-on settings, permission-based triggers, and retrieval delays makes it a feature that demands deliberate control. The organizations that gain the most from it will be those that first disable it everywhere, run a tight pilot, prove the retrieval and compliance workflows, and only then expand the Archive button to the users and sites that can handle it responsibly.

Microsoft continues to refine the Archive service. Watch for future admin-center controls that may reduce the PowerShell dependency, and keep an eye on Purview integrations that could automate archiving based on classification labels. For now, the power is in your hands—just be sure you hold the PowerShell prompt before your users hold the Archive button.