
A practical guide to achieving substantial storage savings without moving governed content outside Microsoft 365.
|
75% |
$0.05/GB |
Governance |
Pricing Disclaimer
Pricing in this article is planning guidance only. Actual charges can vary by agreement, billing channel, tenant quota, region, currency, feature availability, and future Microsoft pricing changes. Validate current rates and eligibility in the Microsoft 365 admin center, Azure billing configuration, and official Microsoft documentation before making budget decisions.
The False Choice Between Cost and Compliance
In the first two posts of this series, we explored how organizations can dramatically reduce SharePoint storage spend—first by understanding the cost of extra storage, then by tiering content to Azure Files and Blob Storage. That architecture achieved roughly 75% cost savings on a 10 TB environment, bringing a ~$2,048/month bill down to approximately $550/month.
Every time I share that story, the same question comes up:
“That’s a compelling architecture—but Legal, Compliance, Records Management, Sensitivity Labels, DLP, and eDiscovery are the entire reason we keep this data in Microsoft 365. We can’t move it outside the tenant.”
That is a completely valid concern. And it leads us to a third option that many organizations overlook entirely.
Microsoft 365 Archive offers a native cold-storage tier that lives inside your SharePoint environment. You don’t export data to Azure. You don’t rebuild permissions. You don’t recreate a governance model from scratch. The content stays in Microsoft 365—at a fraction of the cost.
What Is Microsoft 365 Archive?
Microsoft 365 Archive is a pay-as-you-go cold-storage tier built directly into SharePoint Online. Rather than moving inactive content to an external system, archived sites and files remain within your tenant—just in a lower-cost storage state.
As of July 2026, Microsoft 365 Archive supports archiving at two levels:
- Entire SharePoint sites (site-level archive — available since initial GA)
- Individual files and folders (file-level archive — reached General Availability in July 2026)
Governance Caveat: File Archive Is Now an End-User Action
File-level archive reached General Availability in July 2026, with rollout beginning in early July and completing by late July. In tenants where Microsoft 365 Archive is enabled, file-level archive is enabled by default for SharePoint sites, and an Archive action appears in SharePoint on the web for users with edit permissions. This makes archive governance more important, not less: organizations should decide where file-level archive belongs, whether sensitive sites should be excluded, how site owners should communicate archive behavior, and how support teams will handle reactivation questions.
The file-level capability is a significant expansion. Organizations no longer need to take an entire site offline to benefit from archive pricing—individual documents, folders, or file sets can be moved to the cold tier independently. Because the Archive action is exposed directly in SharePoint on the web, governance planning must include end-user behavior, not just administrator-led archive waves.[2]
The Cost Math: 75% Savings Inside Microsoft 365
Microsoft 365 Archive is billed at $0.05 per GB per month, compared to the standard extra SharePoint storage rate of $0.20 per GB per month. That is a 75% reduction in per-GB cost.
|
Storage Tier |
Rate (per GB/month) |
Annual Cost (per TiB / 1,024 GB) |
Savings vs. Active |
|
SharePoint Extra Storage (Active) |
$0.20 |
$2,457.60 |
— |
|
Microsoft 365 Archive |
$0.05 |
$614.40 |
75% |
Using the same 10 TB scenario from Post 1 of this series, calculated consistently as 10 × 1,024 GB:
|
Scenario |
Active Storage |
Archived Storage |
Est. Monthly Cost |
Est. Savings |
|
Baseline — All Active |
10 TB |
0 TB |
$2,048/mo |
— |
|
Archive 5 TB of inactive sites |
5 TB |
5 TB |
$1,280/mo |
37.5% |
|
Archive 8 TB of completed projects |
2 TB |
8 TB |
$819.20/mo |
60% |
|
Archive 9 TB — retain minimal active |
1 TB |
9 TB |
$665.60/mo |
67.5% |
The Billing Nuance Most Administrators Miss
Microsoft 365 Archive only charges for archived storage when your combined active + archived storage exceeds your tenant’s included SharePoint quota. If your organization is still within its licensed quota, archived content may cost nothing additional at all. Verify your tenant’s quota before assuming you will incur archive charges.
Additionally, as of March 31, 2025, Microsoft eliminated reactivation fees for archived SharePoint content. Site reactivation is now free, though site-level archive includes a four-month re-archive restriction after reactivation. File-level archive should be documented separately because file reactivation behavior and cooldown timing differ from site-level archive and should be validated against current Microsoft guidance before publishing operational policy.
The Closed Project Problem: Your Best Archive Candidates
The biggest challenge with Microsoft 365 Archive is not enabling the feature. The challenge is identifying the right content to archive. For many organizations, the answer is hiding in plain sight.
Think about the SharePoint sites currently consuming storage in your environment. How many of them look like this:
- Completed construction or infrastructure projects
- Closed client engagements
- Concluded M&A or due diligence workspaces
- Resolved litigation or regulatory matter sites
- Legacy department sites from restructured teams
- Former product lines or sunset initiatives
- Historical HR, Finance, or Audit workspaces
Nobody collaborates in these sites anymore. But:
- Legal requires retention
- Auditors require access
- Records management requires preservation
- eDiscovery may require searchability
This is precisely where Microsoft 365 Archive is designed to operate. The sites remain in SharePoint. Permissions are preserved. Retention policies continue to apply. But the storage billing shifts from active to archive rates.
Governance Preserved: The Compliance Case
This is the section that matters most to Legal, Compliance, and Records Management stakeholders. Archived content in Microsoft 365 Archive is not a governance exception. It is governed content at a lower price.
|
Governance Capability |
Active SharePoint |
M365 Archive |
|
Microsoft Purview Retention Policies |
✓ Enforced |
✓ Enforced |
|
Sensitivity Labels |
✓ Applied |
✓ Applied |
|
Data Loss Prevention (DLP) |
✓ Active |
✓ Policies Remain, Enforced on Reactivation |
|
eDiscovery Search |
✓ Indexed |
✓ Searchable |
|
eDiscovery Export |
✓ Standard |
✓ Supported (may take longer) |
|
Legal Hold |
✓ Honored |
✓ Honored |
|
Records Management |
✓ Active |
✓ Active |
|
Permissions / RBAC |
✓ Preserved |
✓ Preserved |
|
Site Metadata |
✓ Preserved |
✓ Preserved |
Microsoft Purview retention policies and retention labels continue to honor their configured periods on archived content. eDiscovery tools can still search and export from archived sites and files.[6] You can apply retention holds to archived content without reactivating it, and you can archive content that is currently under retention hold without breaking the hold.
What Archived Content Cannot Do
The user-access restrictions differ between archive types:
Site-level archive: Archived sites are not immediately available for day-to-day user access. Reactivation is required before users can browse, edit, or collaborate on archived site content. For completed projects and historical compliance workspaces, this is generally an acceptable trade-off.
File-level archive: Archived files remain visible in their original SharePoint location with a visual indicator, but must be reactivated before they can be opened or read. Users with read permissions can trigger reactivation themselves without admin involvement.
The Copilot Optimization Dividend
There is an increasingly relevant benefit that does not appear on any cost spreadsheet: Microsoft 365 Copilot optimization.
Microsoft’s wording that “Copilot is not trained on archived content” is useful framing, but the practical mechanism is more specific: archived content remains in the Microsoft 365 search index for Purview Content Search, eDiscovery, and end-user search, while it is excluded from Copilot grounding. That means stale, outdated, or completed project content can still be discovered through the appropriate search and compliance tools, but it is not used as grounding material when Copilot generates responses for users.
For knowledgeable governance and search stakeholders, this distinction matters. Microsoft 365 Archive does not make archived content disappear from Microsoft 365 search experiences or compliance discovery. It changes whether that content participates in Copilot grounding, which is exactly why archive can improve Copilot relevance without weakening retention, search, or eDiscovery coverage.
For organizations deploying Copilot, this creates a virtuous cycle:
- Archive inactive content → Reduce storage cost
- Archived content excluded from Copilot grounding → Improve Copilot relevance
- Better Copilot results → Faster user adoption
- Broader adoption → Greater ROI on Copilot licensing
The archive program pays for itself in storage savings and improves the AI investment simultaneously.
The Content Lifecycle Model: A Framework for Decision-Making
One of the most valuable things a consultant can provide is a structured lifecycle model that gives governance, IT, and business stakeholders a common framework for archive decisions. Below is a practical four-stage model:
|
Stage |
Status |
Storage Strategy |
Governance Action |
|
1 |
Active Collaboration |
SharePoint Active Storage |
Site owner assigned; access reviewed quarterly |
|
2 |
Inactive — Under Review |
SharePoint Active Storage (short-term) |
Owner confirmation requested; archive review initiated |
|
3 |
Archived — Retained |
Microsoft 365 Archive |
Retention labels applied; eDiscovery scope maintained |
|
4 |
Eligible for Disposal |
Purview Records disposition |
Disposition review completed; content deleted or transferred |
In practice, lifecycle frameworks often make archive discussions easier because stakeholders can immediately identify where their content sits in the lifecycle, rather than debating whether content is “too important to archive” without a clear definition of importance. When everyone uses the same stage definitions, the conversation shifts from a debate about value to a question of classification.
M365 Archive vs. Azure Blob: Choosing the Right Architecture
Microsoft 365 Archive and Azure Blob Storage are not competing alternatives—they serve different governance profiles. The right answer depends on organizational requirements.
|
Requirement |
M365 Archive |
Azure Blob Archive |
|
Content stays in Microsoft 365 tenant |
✓ Yes |
✗ No |
|
Purview retention enforced natively |
✓ Yes |
Requires separate design |
|
Sensitivity labels preserved |
✓ Yes |
Manual process required |
|
Existing permissions preserved |
✓ Yes |
Must be rebuilt |
|
eDiscovery alignment |
✓ Strong |
Additional planning required |
|
Site metadata preserved |
✓ Yes |
Not preserved |
|
Reactivation cost |
Free (as of March 2025) |
Retrieval charges apply; early deletion penalty can apply before 180 days |
|
Storage cost (per GB/mo) |
$0.05 |
Approx. $0.002/GB-mo storage, plus retrieval/operation costs |
|
Absolute lowest cost |
No |
Yes |
|
Governance simplicity |
Excellent |
Moderate to Complex |
|
Best for regulated content |
✓ Yes |
With additional design work |
|
Best for unstructured bulk data |
Secondary option |
✓ Yes |
The Azure Archive storage rate can look dramatically lower on paper, but it is not the whole cost model. Microsoft’s Azure Blob Storage guidance treats archive cost as a combination of writing data, storing data, and rehydrating or retrieving data. Retrieval charges can be materially higher than storage charges, and data moved out of the archive tier before the 180-day minimum retention period can trigger a prorated early deletion fee. In Microsoft’s own sample scenario, archive retrieval is modeled at $0.022 per GB and includes an early deletion component when data is moved out before the 180-day threshold.
The decision framework is straightforward:
- If governance, Purview, eDiscovery, and compliance are the primary requirements: Microsoft 365 Archive is the right answer.
- If lowest possible storage cost is the primary requirement, content is not governed by Microsoft 365 compliance requirements, and retrieval is expected to be rare: Azure Blob Archive can deliver maximum storage-rate savings, but the business case must include retrieval charges, operation costs, rehydration timing, and any 180-day early deletion exposure.
- For many enterprise environments: a tiered approach is optimal—M365 Archive for governed compliance content, Azure Blob for bulk unstructured data without active governance requirements.
Governance Readiness Checklist
Before deploying Microsoft 365 Archive, work through the following checklist with your governance and IT stakeholders:
|
# |
Checklist Item |
Status |
|||
|
1 |
Azure subscription configured for pay-as-you-go billing (required for M365 Archive) |
☐ |
|||
|
2 |
Microsoft 365 Archive enabled in SharePoint admin center |
☐ |
|||
|
3 |
Tenant SharePoint storage quota reviewed — understand billing threshold |
☐ |
|||
|
4 |
Site lifecycle policy defined (active / inactive / archive / disposal stages) |
☐ |
|||
|
5 |
Archive candidate sites identified — completed projects, closed teams, historical workspaces |
☐ |
|||
|
6 |
Site owners notified prior to archiving — communication plan in place |
☐ |
|||
|
7 |
Purview retention labels and policies validated against archive behavior |
☐ |
|||
|
8 |
eDiscovery team briefed on archive search and export timelines |
☐ |
|||
|
9 |
Legal Hold requirements reviewed — confirm no conflict with archiving |
☐ |
|||
|
10 |
Reactivation SLA defined — how quickly can users request content restoration? |
☐ |
|||
|
11 |
Reactivation and re-archive rules documented separately for site-level archive and file-level archive — confirm current Microsoft guidance for the four-month site-level restriction and any file-level cooldown behavior |
☐ |
|||
|
12 |
Copilot optimization impact communicated to Copilot stakeholders |
☐ |
|||
|
13 |
File-level archive governance reviewed — confirm whether default tenant/site enablement is appropriate, identify sensitive sites to exclude, and document who may archive files through the SharePoint web Archive action |
☐ |
|||
|
14 |
Helpdesk and records-management teams briefed on file reactivation behavior, including user-triggered reactivation, expected restore timing, and any applicable file-level cooldown period |
☐ |
|||
|
15 |
Monthly archive storage cost estimated and added to IT budget forecast |
☐ |
|||
Practical Consultant Recommendations
After working through the cost model, governance analysis, and lifecycle framework, here is how I typically approach Microsoft 365 Archive conversations with clients:
Start with the Quick Win: Completed Project Sites
Run a SharePoint site activity report filtered for sites with no activity in the past 90–180 days. In many environments, a significant percentage of SharePoint sites fall into this category. Present that list to business stakeholders and ask a simple question: “Which of these are completed projects that still require retention?” That list becomes your first archive wave.
Validate the Billing Model Before Committing
Check your tenant’s current active storage against your licensed SharePoint quota. If you are already well below quota, your first archive deployments may cost nothing. If you are significantly over quota, the savings calculation is immediate and compelling.
Bring Compliance into the Conversation Early
The archive discussion is substantially easier when Legal and Compliance understand that Purview retention, sensitivity labels, eDiscovery, and Legal Hold all function normally on archived content. Position Microsoft 365 Archive as a cost optimization that does not require a governance exception—because it does not.
Use the Three-Post Series as a Business Case
The progression of this series maps directly to the conversation most IT leaders need to have with Finance and Legal:
- Post 1 established the cost problem — SharePoint extra storage is expensive at scale
- Post 2 showed the maximum savings available — Azure tiering achieves ~75% reduction for eligible content
- Post 3 addresses the governance objection — M365 Archive achieves comparable savings for regulated content
Together, these three scenarios cover the full landscape of enterprise SharePoint storage optimization. The right architecture for most organizations will be a combination of all three approaches, matched to the governance profile of the content.
The Bottom Line
Microsoft 365 Archive represents a third path between buying more SharePoint storage and exporting content to Azure storage. Organizations can preserve SharePoint permissions, retention policies, sensitivity labels, metadata, and compliance controls—while achieving up to 75% storage savings. For inactive project sites, completed client engagements, historical Teams workspaces, and long-term records that rarely require user access, Microsoft 365 Archive provides the best balance between cost optimization and governance.
References
Overview of Microsoft 365 Archive
Microsoft 365 Archive Product Page and FAQ
M365 Cost Management: How to Justify Storage Spend.
Pricing model for Microsoft 365 Archive
Compliance features in Microsoft 365 Archive
Note: Pricing figures are based on Microsoft published list rates as of August 2026. Actual costs vary based on enterprise agreements, region, and tenant storage quota. Verify current pricing at microsoft.com/en-us/microsoft-365/microsoft-365-archive before making financial projections.
About the Author

Michael C. Korting is a Senior Microsoft 365 Consultant at Sycomp with more than 15 years of experience helping organizations modernize their technology platforms through cloud adoption, security transformation, and digital workplace solutions. He specializes in Microsoft 365, Copilot, identity and access management, endpoint management, compliance, and Zero Trust security architectures, with extensive experience leading enterprise migrations, modernization initiatives, and governance programs
Throughout his career, Michael has partnered with organizations ranging from small businesses to enterprise clients, delivering solutions that improve security, collaboration, operational efficiency, and user experience. As a recognized Microsoft technology expert, he regularly shares practical insights on Microsoft 365, security, compliance, AI, and emerging cloud technologies through his professional blog and industry content
Other Resources

Act Before September 1: Microsoft Entra’s Passkey Auto-Migration

Microsoft 365 Licensing Changes in July 2026: Why Business Premium, E3, and E5 Deserve a Fresh Look

Technology Means the World: Sycomp Capabilities Overview

