You’ve done the hard part. You ran the reports, identified the bloated sites, and traced the growth back to version history and inactive content that’s been sitting in active storage for years. You know what’s driving the bill.
The next step isn’t technical. It’s a conversation with someone who doesn’t know what version history is and doesn’t need to. And if you’re honest, you’ve probably been putting it off.
Here’s the thing: your organization is already paying for this problem. Every month that storage stays unmanaged, the overage charge recurs. Leadership isn’t being protected by not knowing. They’re just being billed without context.
With Microsoft confirming broad-based M365 price increases for July 2026, cost conversations are happening at every level right now. Getting ahead of this one, with a clear frame and the right numbers, is a much better position than reacting to the next invoice.
You don’t need to teach your finance team how M365 storage works. You need one clear frame and the numbers that make it real.
Most storage conversations go wrong because IT tries to explain the mechanism. Tenant pools. Version limits. Quota mechanics. None of that is useful to a CFO or a department head.
There are only two things leadership needs to understand.
First: overages aren’t a one-time surprise. Once you cross your included storage quota, Microsoft charges you every month you stay over. The charge doesn’t go away on its own. It compounds as content grows. If you’re over today and nothing changes, you’ll be more over next quarter.
Second: the cause is manageable. This isn’t a capacity problem that requires buying more licenses or migrating to a new platform. It’s a lifecycle problem. Content that should be archived, trimmed, or removed has been accumulating in expensive active storage because no system exists to deal with it consistently at scale.
Think of it like a warehouse that never purges old inventory. You keep paying for floor space whether the shelves hold active product or archived specs from 2018. The cost isn’t a pricing problem. It’s a housekeeping problem.
What to leave out of this conversation: anything about tenant pools, SharePoint admin center views, or how versioning works. That’s for the people who need to act on it. For everything you’d want an admin to understand first, see our guide to why M365 storage turns into a cost surprise.
Abstract framing only goes so far. Here’s what makes the conversation land.
Microsoft’s official rate for extra SharePoint storage is $0.20/GB/month. That’s $2,400 per terabyte per year, every year, for as long as you’re over quota.
Microsoft 365 Archive costs $0.05/GB/month. That’s $600 per terabyte per year. Reactivation is free as of March 2025 for SharePoint sites.
Put those side by side:
| Storage type | Cost per TB/year | Cost for 10TB overage/year |
|---|---|---|
| Active SharePoint storage (overage) | $2,400 | $24,000 |
| M365 Archive | $600 | $6,000 |
| Savings with archive | $1,800 per TB | $18,000 per year |
For a mid-sized organization, 500 E3 users get 6TB of included storage (1TB base plus 10GB per licensed user). If that tenant is running 10TB of overage, that’s $24,000 a year in charges. Move that same content to M365 Archive and the cost drops to $6,000 a year. That’s an $18,000 annual saving, and it’s calculated with Microsoft’s own published pricing.
A single year’s snapshot understates the problem, so be sure to highlight growth trajectory as well. If storage grew 15% last year, that $24,000 becomes roughly $27,600 next year with no intervention. Showing leadership a projected 18-month trend, not just today’s figure, makes the cost of inaction concrete.
A note on version history: the visible file size isn’t the storage footprint. A single frequently-edited file can have hundreds of full-copy versions behind it, each counting against your quota. In many tenants, version history is the single biggest storage driver. For more on how that works, see our breakdown of how version history affects your M365 storage.
You may need to have this conversation with more than one person. The numbers are the same, but the frame that lands depends on who’s in the room.
Lead with the recurring vs. one-time framing. Finance understands penalty fees. What they need to hear is that this isn’t a surprise line item, it’s a pattern that recurs until the underlying content is addressed.
Translate it to budget language: “We’re currently spending $X per month on storage we could reduce by 75% with archive. The alternative is a one-time investment in lifecycle management that bends the cost curve permanently.”
The objection you’re likely to hear: “Can’t we just delete stuff?”
Answer: Deletion alone doesn’t fix the underlying patterns. Without lifecycle management, the number climbs back. You’re not asking for permission to clean up once. You’re asking for the tools to keep it clean.
Your procurement team will comparison-shop on price per GB. Get ahead of it.
Yes, third-party cold storage tools can be cheaper per GB on the surface. But content that leaves M365 exits the Search, Copilot, retention, DLP, and eDiscovery perimeter you’re already paying for. Retrieval costs, rehydration delays, and compliance overhead often close that gap quickly. The real comparison isn’t storage cost per GB. It’s total cost including access, compliance, and platform fragmentation.
The framing that works: “The cheapest storage is the storage that keeps working inside the tools your team already uses.” For a full breakdown of the tradeoffs, see our post on keeping storage inside Microsoft 365.
Skip the cost math. They’ll trust IT on the numbers. Lead with risk and platform readiness.
The framing: “We’re not asking for budget to fix a storage problem. We’re asking for alignment to fix the patterns before the next renewal conversation.”
Microsoft has confirmed broad-based M365 price increases effective July 2026. For organizations already running storage overages, this compounds the problem in two directions: the base subscription cost goes up, and any overage charges continue on top of that.
Here’s why that matters more than it might seem. Overage charges are calculated on top of your existing subscription cost. If your subscription goes up 10% and you’re still carrying the same storage overage, you now have a higher baseline and an unchanged overage burden. For organizations that have been absorbing overages as a line item without addressing the root cause, July 2026 is the point where that approach becomes visibly expensive.
There’s also a timing argument. Most organizations negotiate M365 licensing in annual cycles. If your renewal lands in late 2026 or early 2027, the negotiation will happen in the context of both the new pricing and your current storage footprint. Walking into that conversation with a storage reduction plan already in motion is a very different position from walking in with unresolved overages and no plan.
The organizations that will be best positioned at renewal are the ones who start the storage conversation now, get leadership aligned on the cost structure, and have a cleanup cycle already underway before the new pricing kicks in. That’s not a months-long project. A focused archive and version-trim effort on the highest-impact sites can move the needle significantly in a matter of weeks.
This is the moment to bring the storage conversation to leadership proactively, with numbers and a plan, rather than waiting until the next invoice makes it unavoidable.
When you go into this conversation, bring a one-page summary that answers three questions:
The third question is where the business case for tooling lives. If the answer is “we’re handling it manually with PowerShell scripts,” that’s also a risk and capacity argument for a better solution.
The challenge with building this report from native tools: the data exists, but not in a form that’s easy to turn into a leadership-ready summary.
The SharePoint Admin Center shows you total storage used across your tenant and a list of your top sites by size. That’s a useful starting point, but it doesn’t answer the questions that actually drive decisions.
It won’t tell you which of those top sites is growing fastest, which ones haven’t been touched in 18 months, or how much of each site’s footprint is version history versus active content. It won’t give you a growth projection. And it won’t tell you which sites are the best archive candidates based on a combination of size, inactivity, and ownership.
Microsoft 365 usage reports add some signal around activity, but correlating that with storage data requires manual cross-referencing. What you’re left with, if you’re doing this without additional tooling, is a spreadsheet exercise: export the site list, pull activity data separately, join them, sort by impact, repeat every quarter.
For a small tenant, that’s manageable. For a tenant with hundreds or thousands of sites, it’s the kind of task that either doesn’t get done or gets done once and then quietly abandoned.
That gap between “the data technically exists” and “we can actually produce this report on a cadence” is one of the clearest arguments for purpose-built tooling. Not because native tools are bad, but because assembling a leadership-ready storage narrative from raw admin exports isn’t a sustainable workflow.
Here's what that visibility looks like when it's consolidated in one place: storage used, quota consumed, active automations, and critical insights flagged automatically.
Microsoft gives you the levers: version limits, M365 Archive, lifecycle settings. The hard part is applying them consistently across a tenant with hundreds of sites, and then producing reporting that leadership can actually read.
That’s what Orchestry does.
Monash Health used Orchestry to save more than 3TB of M365 storage overnight, with more than 4x ROI on the cost of the platform. Read the full case study.
If you walk away from this post with one thing, make it this:
"Right now, we’re paying a recurring overage charge for content that should be archived or removed. We have a plan to fix the underlying patterns. The cost of fixing it is less than the cost of another year of doing nothing."
With July 2026 M365 price increases on the horizon, the window to get ahead of this conversation is now, not after the next invoice arrives.
If you want help building the numbers for that conversation, a storage health review is a good place to start.