Microsoft 365 Archive is a records decision with a storage meter attached

Microsoft 365 Archive usually arrives as a line in a storage conversation. The tenant is over quota, someone finds the FAQ, and the numbers look good: Microsoft Learn lists archived storage at $0.05 per GB per month against a standard SharePoint storage rate of $0.20.

Those numbers are real. They're also the smallest part of the decision. Archiving changes who can reach content, how quickly, and whether Copilot sees it at all. Someone in the organization has to own that, and in our view it isn't the person watching the storage meter.

What archiving does to a site

Archive moves a site, or individual files, into a colder storage tier without taking it out of SharePoint. The same security and compliance tooling keeps working, and there's no second repository to govern. A site keeps its document libraries, folder structure, lists, metadata and permissions, and on reactivation it returns to its prearchival state, with two exceptions covered below.

While it's cold, though, nobody can open it. End users can still find archived content: SharePoint web search has an Archived option under File type, OneDrive web search has an Archived pill, and results stay permission-trimmed. Purview Content Search and eDiscovery search it as normal, though exports can take longer. Copilot doesn't use archived content at all.

That last point cuts both ways. Archiving stale project sites can sharpen Copilot's answers. Archiving the wrong site hides the one document a team still relies on.

Reactivation: time, people and fine print

Archived content moves through states. For seven days after archiving it's Recently archived, and reactivation is instant. After that it's Archived, and reactivation can take up to 24 hours.

Who can reactivate depends on what was archived. Any user with read access can reactivate an archived file. A whole archived site needs a SharePoint administrator. That asymmetry is the real operating cost: once a site has been cold for more than a week, a user who needs one file from it is looking at an admin ticket and up to a day's wait.

On money, Learn's pricing page says Microsoft eliminated the reactivation fee for archived SharePoint content on 31 March 2025, and that re-archiving newly reactivated content is restricted for four months afterward. Files specifically can't be archived again for 120 days. The fee change doesn't cover unlicensed OneDrive accounts, which are still billed per GB on reactivation. The Learn page on managing Archive still describes an estimated reactivation price in the confirmation step for sites in the Archived state, so check what your own admin center shows before you tell anyone it's free.

Where the bill actually sits

Archive runs on pay-as-you-go billing. An Azure subscription has to be linked in the Microsoft 365 admin center first; then a SharePoint Administrator or Global Administrator switches it on under Settings > Org settings > Pay-as-you-go services > Settings > Storage services > Archive.

The meter only runs when active plus archived storage exceeds the tenant's licensed SharePoint quota. A tenant under quota pays nothing extra for archived content. If the billing subscription goes unhealthy or Archive is switched off, archived content stays archived and can still be reactivated, but new archiving is blocked and archived content counts as active storage until billing is healthy again.

File-level archive doesn't save site storage at all. An archived file counts against its site's quota exactly as it did before. At tenant level the bytes are reclassified from active to archived; at site level nothing changes.

Who should be allowed to archive

Site archiving is an admin action in the SharePoint admin center. File archiving isn't: once Archive is enabled, any user with edit permission on a SharePoint file can archive it by default.

We'd switch that off at first. Learn lists clients that don't yet handle archived files well, including Word and PowerPoint for the web, the Teams, OneDrive and SharePoint mobile apps, and the OneDrive sync client on macOS, and those clients can show misleading errors. `Set-SPOTenant -AllowFileArchive $false` removes the Archive action from users while still letting admin-defined policies archive eligible files, and `-AllowFileArchiveOnNewSitesByDefault` controls the default for new sites. Turn manual archiving back on site by site once the site owner understands what users will see.

A few sites need planning before they can go cold. A hub site has to be unregistered as a hub first. A Teams-connected site with private or shared channels can't be archived from the SharePoint admin center. Publishing sites and some legacy templates aren't supported. And archiving a Teams-connected site doesn't archive the team; the two features are independent.

Archive is not disposition

This is where records discipline earns its keep. Archived content still honors every retention and deletion period from retention policies and labels. Holds still apply, files still move to the Preservation Hold Library when their retention settings require it, sensitivity labels still apply, and archiving, reactivation and deletion all land in the audit log. Recycle bin expiry and retention-driven deletion keep running while a site is archived, and they're the two exceptions to a clean reactivation.

So archiving never answers "should we keep this?" It answers "how quickly do we need to reach it?" In OpenText and SAP archiving work those questions sit with different people, and they should here too. If content is past its retention period and under no hold, the right move is disposition, not a cheaper shelf. An archived site can be deleted without reactivating it first.

The sign-off chain

The site owner nominates a site for archive. The records owner confirms it isn't due for disposition and isn't something people still need weekly. A SharePoint administrator archives it and handles reactivation requests within an agreed turnaround. Whoever owns the Azure subscription watches the meter. If you run inactive site policies, their final enforcement step can archive sites automatically after a read-only period, so the records owner signs off on that policy's scope before it runs, not after the first site goes cold.