Purview archive mailboxes past 1.5 TB: GCC, GCC High, DoD

Oct 15, 2026 · Insights

Microsoft has published release communications records for upcoming Microsoft Purview changes that name three U.S. government clouds: GCC, GCC High and DoD. Two of them concern archive mailboxes: auto-expanding archives that can grow past 1.5 TB, and Microsoft Graph access to archive mailboxes. Both list estimated general availability in November 2026. A third record, on permissions audit logs, lists October 2026.

What Microsoft announced

The records are titled with the Microsoft Purview “Data Lifecycle Management” feature area and carry the status “In development.” Each one gives only a short description.

Feature 573702, auto-expanding archive beyond 1.5 TB. The record says auto-expanding archive mailbox expansion was previously supported only up to 1.5 TB, after which mailboxes would become inoperative. Archive mailboxes can now automatically expand beyond that limit, and the capability will be available to customers with eligible E5 licenses. Estimated general availability: November 2026.
Feature 573701, Graph API support for archive mailboxes. The record describes access to archive mailboxes (main plus auxiliary) through Microsoft Graph, so users get a single Archive view even though archive data may sit across several auxiliary mailboxes. Its text also mentions EWS Graph APIs being deprecated. Estimated general availability: November 2026.
Feature 573447, permissions audit log improvements. The record describes enhanced audit logs that give administrators clearer visibility into role and scoped-role access decisions when users reach the Microsoft Purview portal. Estimated general availability: October 2026.

None of the three records lists a preview date or any further information links, so there is no preview guidance yet. Because the status is still “In development,” read the word “now” in the archive description as a plan, not as something already available. We report the records as written and do not guess at settings or rollout details they do not contain.

Who is affected

Each of the three records lists the same cloud instances: GCC, GCC High and DoD. They do not name commercial Microsoft 365 tenants. If your organization uses a commercial tenant, these particular records do not identify your tenant.

The archive expansion record also ties the capability to eligible E5 licenses. The Graph record does not mention licensing, so do not assume the same condition applies to it.

What to do

Confirm which cloud hosts your tenant. Ask your Microsoft 365 administrator or Microsoft account team whether the tenant is in GCC, GCC High, DoD or a commercial cloud.
List mailboxes near 1.5 TB. For government-cloud tenants, make a list of mailboxes whose archives are approaching 1.5 TB, with the name of each mailbox owner.
Check licensing. The archive expansion record says eligible E5 licenses. Confirm whether the affected users hold them, and plan for any gap.
Name a contact for each large archive. Record who in compliance or legal should be told when the change reaches your tenant.
Hold off on pilots. No preview date is listed. When Microsoft publishes preview or general availability guidance, test on a small set of nonproduction mailboxes first.
Review capacity and maintenance plans. Larger archives are likely to affect storage, backup windows and e-discovery export time, so look at those assumptions and at any vendor agreements or maintenance windows tied to them.
Leave scripts alone for now. The Graph record mentions EWS Graph APIs being deprecated but gives no timeline, so wait for Microsoft’s guidance before rewriting integrations.

What can wait

If your tenant is a commercial Microsoft 365 tenant, these records do not list your cloud instance and you do not need to act on them. Government-cloud tenants can also wait on any change to scripts, third-party tools or automation until Microsoft publishes more detail. The permissions audit log item needs no preparation beyond knowing it is coming.

Why plan before the date

Mailboxes that stopped at 1.5 TB became inoperative, so a limit that moves is good news for heavy archive users. It also means archives can keep growing, and that is worth planning for before it happens rather than after. Sizing, backup and export assumptions are cheaper to revisit while nothing is urgent.

The records do not say whether administrators will be able to cap expansion, or how auxiliary mailboxes will show up in searches. Those are questions to put to your Microsoft account team, and answers should come from Microsoft’s documentation once it exists, not from guesswork.

A simple way to organize the work

Small offices tend to handle this kind of change best when one person owns it. Pick that person now, give them the list of large archives, and ask them to keep a short note of what Microsoft has published and when. A one-page summary is enough: which cloud you are in, which mailboxes are large, who owns each one, which licenses are in place and what questions are still open.

Keep the note somewhere your administrator and your compliance or legal contact can both read it. When Microsoft moves a feature from “In development” to preview or general availability, the note tells you at a glance what to check first. If your organization handles regulated records, add the retention policy owner to the list so that nobody learns about a change after the fact.

It also helps to write down the questions you cannot answer from the records, such as how expansion is controlled and how archives appear in searches. Bring that list to your Microsoft account team. A clear list gets a clearer answer than a general request for an update.

When to get help

If you manage a GCC, GCC High or DoD tenant with large archives or regulated retention needs, ask your Microsoft account team about licensing and preview timing. Our engineers can help with an archive inventory and a pilot plan; for related checks on your mail setup, see our email security check. To talk it through, contact Summit Networks.

Sources

← All insights