Last updated: April 9, 2026
Microsoft 365 Archive has been positioned as Microsoft's native solution to managing growing storage volumes in SharePoint Online. Instead of paying full active storage rates, you move inactive data out of active storage and reduce costs. Important note: the effectiveness of Microsoft 365 Archive depends on how it is used, what type of data is archived, how often users need to access archived content, and how critical immediate access to archived data is. It also depends on whether restoring content requires IT involvement or can be handled directly by end users.
This article shows what Microsoft 365 Archive does, where it can help your organization, and where you should use an alternative solution.
When using Microsoft 365 Archive is resonable
Microsoft 365 Archive works best in a narrow set of scenarios. It is a good solution when you are dealing with entire SharePoint sites that are no longer actively used and are unlikely to be accessed again: completed projects, legacy team spaces, or outdated departmental sites. This content needs to stay preserved for compliance or reference. The archive can function as a long-term storage with minimal operational impact .
In those cases, the risk of users needing immediate access is low. The moment data is still relevant to work, or users expect to access a file without a helpdesk ticket and waiting, the limitations show up fast.
How Microsoft 365 Archive works
When you use Microsoft 365 Archive, it moves data from an active storage to an archive storage. There are two levels of archiving:
- Site-level archiving, general availability
- File-level archiving, currently in preview
These two models are different in how they are managed and how users interact with archived data.
Site-level archiving: controlled by IT
Site-level archiving is entirely managed by IT through the SharePoint admin center. You move a whole site into the archived state, and it changes to read-only. Users are locked out until an admin reactivates it. That structure is the strength here. IT controls what gets archived and when, the process is predictable, and it fits into governance workflows for inacive workloads.
The trade-off is reactivation. It is not immediate, it requires admin involvement, which limits its suitability for data that needs to be accessed.
File-level archiving: flexible, but user-dependent
File-level archiving aims to provide more flexibility. Instead of archiving entire sites, individual files can be archived and later restored directly by end users within the SharePoint interface. In theory, this is a strong advantage. Users can access their files without IT involvement. In practice, there are two major limitations:
-
The responsibility for archiving data to end users. Users do not think in terms of lifecycle management or storage optimization. They archive inconsistently, they react to full storages rather than preventing them, and they make decisions based on convenience instead of governance. Admins and organizations lose control of what actually gets archived. Cost savings these organizations were counting on become unpredictable.
-
File-level archiving is still in preview. That means errors on restore are a real possibility, not an edge case. Running a preview feature in a production environment is a risk most admins would rather avoid.
Restore experience and operational limitations of Microsoft 365 Archive
Restore speed is where Microsoft 365 Archive shows its operational limits, and it is worth understanding these before you commit.
Files archived for less than seven days restore quickly. Beyond that seven days threshold, the restore process can take up to 24 hours. For users who need a document now that wait is a serious problem. It reduces user acceptance of the archive solution and that will become a problem for IT teams.
Reactivation also is not reversible on demand. Once you restore content, cooldown periods apply before it can be archived again. For file-level archiving, that period is 30 days. For sites, it can be up to four months.
The consequence is: every time you restore archived content, it moves back into active storage and stays there for a significant period. That affects your active storage amount, your cost projections, and your ability to keep the environment clean. If archived project data gets pulled for a legal request and you cannot re-archive it for four months, that is not a minor inconvenience. It is a gap in your storage management strategy that you need to plan around.
Archive costs: a complex pricing model
Archiving data does not automatically reduce storage consumption from a billing perspective. Archived content still counts toward the overall tenant storage usageMicrosoft 365 Archive is consumption-based and billed at about €0.05 per GB per month, depending on region. Archived content still counts toward your total tenant storage. The archive pricing only applies to the storage that exceeds your included storage quota. If your tenant stays within its baseline, archiving costs you nothing extra. If you are already over the limit, only the overage is billed at the archive rate.
Microsoft 365 Archive is not a cheap storage tier that immediately lowers your bill the moment you start archiving. It is a secondary pricing mechanism once your storage baseline has already been exceeded.
Where Microsoft 365 Archive reaches its limits
Microsoft 365 Archive works well when your requirements are simple and access is rare. Limitations become visible when organizations require more flexibility.
-
The solution does not provide automated, policy-driven archiving based on metadata. You can not use rules that trigger archiving when a file has not been modified in months, exceeds a certain size, or stored in a specific location. You are identifying and acting on content manually or scripting your own logic.
-
Restore is neither fast nor flexible enough for content that might be needed immediately. Cooldown periods means you cannot treat this as a dynamic storage management tool. Once you archive something and restore, it will be in active storage for weeks or months before you can archive again.
-
For anything more complex than straightforward site archiving with low access expectations, you will be working around its constraints rather than with them.
When you need an alternative solution and when you don't
-
If your requirement is archiving entire inactive SharePoint sites and staying in your Microsoft eco system, Microsoft 365 Archive can be a good solution.
-
If you need to identify inactive files across the tenant, apply metadata-based archiving policies, guarantee fast and predictable restore for users, or re-archive content without running into cooldown restrictions you should evaluate alternative solutions.
Frequently asked questions about Microsoft 365 Archive
Here we'll answer the most common questions about Microsoft 365 Archive.
When you archive data with Microsoft 365 Archive content will be moved to an archived storage tier. Archived data still counts toward your lower-cost "cold" storage tier.
You can setup your Microsoft 365 Archive in the admin center. You enable Microsoft 365 Archive under the SharePoint admin settings, which activates the feature for your tenant. Once activated, administrators can manage archived sites directly within the same interface. It is important to define clear responsibilities for archiving and reactivation. Organizations should establish processes for who is allowed to archive content and how restore requests are handled.
No. Archiving does not reduce your SharePoint storage immediately. Archived data still counts toward your total tenant storage consumption. Costs are only reduced if archiving helps you avoid exceeding your included storage quota.
Restored files can not be re-archived immediately in Microsoft 365 Archive. Files are locked out of archiving for 30 days after restore, and larger structures like SharePoint sites can face restrictions of up to four months.
