Keeping storage inside M365: When offloading content helps or hurts

If your Microsoft 365 storage bill is climbing, you’ve probably already seen the pitch. Move your SharePoint content to external storage, drop your quota, cut costs by 50% or more. The numbers are real. Tools in this space deliver exactly what they promise on the cost side.

But there’s a cost that doesn’t show up on the invoice. For most organizations, it’s the one that matters most.

SharePoint charges $0.20/GB/month for storage beyond your base tenant pool (1 TB plus 10 GB per licensed user). Version history, legacy migrations, and orphaned content push tenants over that line faster than expected. We cover those patterns in Why SharePoint and OneDrive storage turns into a cost surprise. The pressure is real, and it’s exactly why a whole category of third-party tools has been built to move content outside M365 entirely.

Before you evaluate any SharePoint archiving solutions, it's worth understanding what they actually do, and what they quietly take away.

What SharePoint storage externalization tools actually do

These tools physically move file content from SharePoint to external storage: Azure Blob, Amazon S3, or a vendor-hosted destination. A stub file or metadata pointer stays behind in the SharePoint library, so the item still appears to exist. Click the stub and it retrieves the file from external storage, sometimes seamlessly, sometimes with a delay.

From a storage reporting perspective, the file is gone from M365 and your quota drops. That's how SharePoint storage offloading works on the surface. What changes underneath is where the real consequences sit.

What you lose when content leaves the Microsoft 365 boundary

When content moves outside M365, it exits the compliance and intelligence perimeter that your Microsoft licensing pays for. The consequences are specific.

Microsoft Search stops working on file content

Microsoft Search indexes content within M365. Externalized files are outside that scope. Stub files keep the filename and basic metadata, but full-text search inside documents fails entirely. At least one vendor in this space acknowledges this directly on their own site: file content is not indexed while stored externally, and search is limited to metadata only.

Copilot can’t reach externalized content

Microsoft 365 Copilot works from the Microsoft Graph, which covers content within M365. Content sitting in Azure Blob or S3 is completely invisible to it. If your organization is investing in Copilot, moving content outside the tenant directly undermines that investment. Those files don’t exist from Copilot’s perspective the moment they leave.

Purview retention, DLP, and eDiscovery stop applying

Microsoft Purview retention works through a Preservation Hold Library mechanism built into SharePoint. Content in external storage is outside that scope. You can’t apply a retention label, litigation hold, or eDiscovery hold to content your compliance tooling can’t reach. DLP policies scan inside SharePoint, OneDrive, Exchange, and Teams. External storage requires entirely separate tooling. eDiscovery can’t discover or place a legal hold on content outside M365. For regulated industries, these aren’t minor caveats.

Security and governance shift to the vendor

SharePoint permissions, conditional access, and audit logging apply inside M365. Once content leaves, you’re relying on the third-party tool’s security model and continued availability. 

There's also a vendor lock-in risk that doesn't get discussed enough. Your data is accessible only as long as you're paying. If you want to stop using the tool, you have to pay to rehydrate everything back into SharePoint before you can do anything with it. If you want to switch platforms, you're facing the same cost again, plus migration friction on top. What looks like a storage saving today can become a retrieval bill tomorrow. 

Microsoft’s own M365 Archive FAQ says it plainly: the benefits of keeping content in SharePoint are ones not possible when data is migrated elsewhere, including intact compliance tooling, admin search indexes, and no need to manage a separate security domain.

SharePoint storage alternatives that keep you inside the compliance boundary

Microsoft has built tools specifically to reduce storage costs without exiting the compliance perimeter. Here's how Microsoft 365 Archive pricing compares to standard overage and external storage:

*Azure Blob cool tier approximate rate, consistent with Azure public pricing.

Microsoft 365 Archive: site-level cold storage (available now)

Site-level Microsoft 365 Archive  moves entire inactive SharePoint sites into a SharePoint cold storage tier at $0.05/GB/month. That’s 75% cheaper than standard overage storage. Retention policies and eDiscovery still apply. Content stays inside the compliance boundary.

Archived sites are removed from end-user search and Copilot’s index. Microsoft frames this as a benefit, not a drawback: it improves Copilot response quality by keeping outdated content out of its results. Your active tenant surfaces more relevant information. For teams evaluating SharePoint archive for Copilot readiness specifically, this is the mechanism that matters: content moves out of the index, not out of the compliance boundary.

Reactivation is free at any time. If you reactivate within 7 days there's no restriction on re-archiving. After 7 days, a four-month re-archive restriction applies. Best fits: completed projects, retired departments, legacy spaces that need to be retained but aren’t actively used.

File-level archive: granular control (public preview March 2026, GA July 2026)

File-level archiving in Microsoft 365 Archive enters public preview at the end of March 2026, with general availability expected in July 2026. It lets you archive specific files without moving an entire site. That solves the mixed-activity site problem, where one active document keeps an otherwise dormant space in hot storage.

One important distinction: file-level archive does not reduce storage costs. Per Microsoft’s own FAQ, archived files continue to count toward site storage quota exactly the same as active files. Its value is Copilot optimization and keeping inactive files accessible without cluttering active workspaces. Unlike site-level archive, full-text search works on file-level archived content for end-user search, Purview Content Search, and eDiscovery.

Version management: reduce the footprint before you archive anything

Version history is often the largest hidden driver of storage costs in M365 tenants. Setting version limits and trimming existing history reduces storage without moving or deleting content. We cover the mechanics in How version history affects SharePoint and OneDrive storage. Policy-driven cleanup keeps the problem from growing back after your initial effort.

The cost gap between external storage (~$0.018/GB/month) and M365 Archive ($0.05/GB/month) is real. The question is whether that extra ~$0.03/GB is worth keeping Purview, DLP, eDiscovery, and Copilot access on that content. For most organizations with active retention policies or Copilot investments, it is.

When does offloading content actually make sense?

To be completely transparent, there are scenarios where moving content outside M365 is a defensible call.

• Truly cold content that will never need to be searched, is not subject to any retention policy, and is not in scope for any current or anticipated legal hold
• Large binary assets like video files, media, or CAD files that don’t need M365 compliance tools applied to them
• Content in organizations that aren’t investing in Copilot and have no compliance obligations that would be affected

The filter before offloading anything is three questions. Does anyone need to search inside this content? Is it under a retention policy or legal hold? Could Copilot ever need to reference it? If yes to any of those, it stays inside M365.

How Orchestry helps you stay inside M365 and lower costs

Knowing that Microsoft 365 Archive exists isn’t the hard part. The hard part is having a repeatable way to identify what should move, get the right people involved in that decision, and keep storage under control as content ages.

Here’s what Orchestry does in practice:

• Surfaces inactive sites and libraries ready for archiving. Instead of running PowerShell scripts to find candidates, Orchestry gives you storage reporting across SharePoint, Teams, and OneDrive so you can see what’s stale and where the biggest savings sit.
• Automates version trimming at scale. Microsoft lets you set version limits going forward, but it doesn’t remove the history that’s already there. Orchestry runs asynchronous version purging jobs across hundreds or thousands of sites, without requiring manual scripts for each one.
• Routes archive decisions through workspace owners. IT shouldn’t be making judgment calls about content it doesn’t own. Orchestry’s Workspace Review automatically notifies owners, collects their input, and escalates if there’s no response, so decisions get made by the right people without creating a manual follow-up backlog.
• Applies archival policies on a defined schedule. You set the criteria for what moves to Microsoft 365 Archive (inactivity threshold, workspace type, content age), and Orchestry applies those policies consistently. Storage stays flat instead of spiking again six months after your last cleanup.

The platform value you’re paying for is worth protecting

If you’re paying for Microsoft 365, you’re paying for search, Copilot, compliance, and security. Tools that move content outside the platform don’t just reduce your storage bill. They reduce the value you get from the licenses you already have.

Microsoft 365 Archive cuts costs by 75% while keeping content inside the compliance boundary. File-level archiving in 2026 adds granular control over inactive files and improves Copilot response quality, without the risks that come with moving content outside M365. The right governance layer makes both tools practical to use consistently and at scale.

Next step: before evaluating any third-party storage tool, run an audit of your tenant’s largest inactive sites. You may find that Microsoft’s own tools get you most of the way there, without touching the compliance boundary.