The first time someone shows you an archive mailbox that has stopped accepting mail, there’s a moment of genuine confusion. The feature is called auto-expanding. It is sold, in spirit if not in writing, as bottomless. And yet here is a mailbox in your high-volume legal custodian group throwing errors because the archive hit a wall nobody mentioned in the pitch deck: 1.5 TB.
That wall is the story. An Office 365 for IT Pros post on 10 September flagged a roadmap item indicating that auto-expanding archives will grow past 1.5 TB for eligible E5 tenants, with rollout timed for October 2026. First real capacity bump since the feature became a thing. For the handful of organisations actually bumping against the ceiling — regulated finance, pharma, anyone under a multi-year litigation hold generating mail faster than they can cull it — this matters. For everyone else it’s a line item to note and forget.
Let me explain what the ceiling actually is, because the marketing language has fogged it for years. An auto-expanding archive is not one giant mailbox. When you enable it, Exchange Online provisions additional storage in chunks and stitches them together behind the scenes, so the user sees one continuous archive while the service quietly adds capacity as the current segment fills. The aggregate has always topped out around 1.5 TB. “Auto-expanding” describes the mechanism, not an absence of limits. Those are different claims, and the gap between them is exactly where admins get surprised.
“So they raised the number. Why is this worth a page?”
Because they haven’t told us the new number, and that silence is the interesting part.
“Past 1.5 TB” is not a specification. It’s a direction. It could mean 2 TB, it could mean 3 TB, it could mean a quota that expands until a different governor kicks in. Until Microsoft publishes the figure in the Message Center or the service description, planning against it is guessing. If you’ve got a retention model that depends on knowing your per-custodian ceiling three years out — and regulated shops do — a vague “more” doesn’t let you finish the spreadsheet.
So here’s my sceptical colleague, who has sat through four of these capacity announcements and is unimpressed.
“This is a non-event. Nobody hits 1.5 TB. You’re writing about an edge case.”
Mostly fair. The median archive isn’t close. But “nobody” is wrong, and the people who do hit it are precisely the people who can least afford a surprise — custodians on indefinite hold where nothing is ever purged. For them the archive isn’t a convenience, it’s the legal system of record. When it stops accepting mail, the failure mode isn’t “user annoyed.” It’s “items that should have been preserved weren’t,” and that’s the kind of sentence that ends up in front of a judge. An edge case with that blast radius gets a page.
“Fine. But it’s E5, so it’s a rounding error of a rounding error. Why does the licensing even matter?”
Because “E5” is not one thing, and the brief I’d give anyone is: don’t assume your E5 qualifies until the service description spells out the SKU. There’s Office 365 E5, Microsoft 365 E5, the standalone Exchange Online archiving add-on, and the compliance bundles that grant archiving rights without the full suite. Auto-expanding archives historically required a plan that includes Exchange Online Plan 2 or the archiving add-on — enabling the feature, not the expanded ceiling. Whether the higher ceiling tracks the same eligibility or gets fenced to specific top-tier SKUs is unconfirmed. Treat the “E5 tenants” framing as a headline, not a licensing contract. Read the fine print when it lands.
“And what happens to the custodian who’s already pinned at 1.5 TB right now? Do they just stay broken until October?”
This is the question worth asking, and the honest answer is: we don’t have Microsoft’s transition language yet. Capacity increases like this have historically been applied to the backend quota without the user doing anything — the ceiling moves, the next auto-expand segment provisions, mail flows again. But “historically” is not “guaranteed,” and there’s usually a staged rollout window rather than a flip-the-switch moment. If you have a mailbox sitting at the limit today, you do not wait for October and hope. You open a support case now, document the condition, and get the affected items routed somewhere that accepts them in the meantime. A roadmap date is not a remediation plan.
Find out if you’re anywhere near this before you care about it
Most of this anxiety evaporates once you look at real numbers, and almost nobody does. Before you spend a minute planning around a limit, find out how close your tenant actually is. This is read-only — no state changes, so no -WhatIf needed — but I’d still run it against a filtered scope rather than the whole directory on a whim.
Sort descending, look at the top row, and you’ll almost certainly exhale. If the biggest archive in your tenant is at 38% of the limit, the October roadmap item is trivia. If you’ve got custodians north of 85%, that’s your reviewed input list for the support conversation — and you keep it, because watching the rate of growth tells you more than any single snapshot.
The part Purview won’t save you from
Here’s where I’ll push back on the celebration. A bigger archive is not a retention strategy. It’s permission to defer having one.
Auto-expanding archives and Purview retention interact in a way people forget: retention holds and litigation holds prevent deletion, which means held content accumulates in the archive and never leaves. Raise the ceiling and you’ve extended the runway for an archive that only ever grows. That’s fine if it’s a deliberate choice. It’s a slow disaster if it’s an accident — the organisation that never built a defensible disposition process, kept everything forever because storage felt free, and now has a multi-terabyte archive of material it’s legally obligated to produce but operationally unable to review.
The honest read on October: it removes a hard stop that was hurting a small number of legitimately large custodians, and that’s a real fix for them. It also quietly rewards the habit of keeping everything, which is the habit that gets organisations into trouble when the subpoena arrives. More room is not the same as less risk.
Check your numbers this week. If you’re under half the limit, close the tab. If you’re near it, the roadmap date is the least interesting thing on your list — the support case and the disposition policy you’ve been avoiding are both overdue.
