Microsoft has quietly filled a critical gap in its Exchange Online modernization plan. On July 7, 2026, the company added a new feature to its Microsoft 365 Roadmap (ID 567313) that will let Microsoft Graph APIs reach into both primary and auxiliary archive mailboxes—the sprawling storage used by auto-expanding archives—under a single, seamless view. The catch? General availability is pegged for August 2026, just two months before Exchange Web Services (EWS) begins its phased retirement in October 2026. For organizations clinging to EWS for compliance, backup, or migration tasks that touch archived mail, this release is not a luxury. It’s a lifeline.

Inside the feature: One archive, no more hidden compartments

For years, Exchange Online has silently distributed old mail across multiple auxiliary mailboxes when an auto-expanding archive outgrows its initial container. End users never notice—Outlook shows a unified view. But behind the scenes, tools that relied on EWS had to navigate a maze of storage locations, often requiring custom logic to discover and export all content. The new Graph capability, tied to Microsoft Purview Data Lifecycle Management, promises to fix that. According to the roadmap, applications will see “a single, seamless archive view” even when data physically lives in separate auxiliary mailboxes.

This is more than a developer convenience. When you apply a retention policy, run an eDiscovery search, or migrate archived email to a new system, you need to be certain every relevant item is accounted for. Missing a subset of data because an API didn’t know where to look isn’t a minor bug—it’s a compliance failure.

Who feels the impact most

IT administrators, compliance officers, and third-party vendors all have skin in this game.

For IT admins, this feature turns a nagging worry into an actionable deadline. If your organization uses auto-expanding archives—and many large tenants do—you’ve probably been wondering how to move archival workflows off EWS before the cutoff. Now you have a concrete target: August 2026. That’s when you can start testing Graph-based access to archives, but the hard work of inventorying your EWS dependencies and validating replacements needs to happen now.

Compliance teams get something equally valuable: consistency. A retention label that fails silently on an auxiliary mailbox undermines the entire lifecycle program. Purview’s deep integration means retention, deletion, and legal hold actions should hit every corner of the archive, not just the easy-to-reach parts.

Vendors of backup, archiving, and governance tools face a moment of truth. Many have been telling customers they’re “migrating to Graph” while still leaning on EWS for archive-heavy scenarios. With a first-party Graph path available before the EWS disablement wave, those claims will be tested. Customers should start demanding specific answers: Does your product handle auxiliary archive redirects? Have you tested against large, fragmented archives? What cloud environments—commercial, government, sovereign—are supported?

How we got to this point

EWS has been the backbone of Exchange programmability since Exchange 2007. It powered everything from Outlook add-ins to enterprise backup suites. But Microsoft has been signaling its demise for years. In early 2026, the timeline tightened: EWS disablement begins October 1, 2026, with full retirement by April 2027. The rationale, as Microsoft’s documentation states, is security and modernization—EWS relies on legacy authentication methods that are harder to secure and govern.

The migration to Graph hasn’t been trivial. Graph is a modern REST API designed for Office 365 productivity, not for deep Exchange operations. Microsoft had to close numerous parity gaps, including the recent general availability of Graph-based mailbox import and export APIs in May 2026. Those APIs already handle some archive complexities through “redirect” mechanisms: when an export requests an item that lives in an auxiliary mailbox, the API returns a target location for the application to retry. The new roadmap item aims to wrap that complexity into a simpler, more intuitive experience—one where the application doesn’t need to care about physical storage.

The timing is no coincidence. With the EWS disablement looming, every Graph enhancement that touches mail becomes a forced migration milestone. Archive support was one of the last major blind spots.

Your action plan before October

The clock is loud. Here’s what you need to do right now:

  1. Run a full EWS inventory. Microsoft provides EWS usage reports and an analyzer tool in the Exchange admin center. Know every application, script, and integration that still calls EWS. Pay special attention to those that touch mailboxes with auto-expanding archives turned on.
  2. Classify your workloads. Not everything needs to move to Graph. Some old integrations can be retired. For the ones that must stay, determine if they already use Graph for archive access, or if they’re waiting on this August release. Create a migration timeline with clear test and cutover dates.
  3. Test archive access thoroughly. Once the Graph feature is generally available, don’t assume it works perfectly at scale. Pick real-world mailboxes—ones with years of accumulated mail, unusual folder structures, and active auto-expansion. Validate that Graph-based tools can discover, export, and apply lifecycle operations to all content, including items in auxiliary mailboxes.
  4. Press your vendors. Ask for written statements confirming that their product supports Graph-based access to auto-expanded Exchange Online archives, including auxiliary mailbox handling. Verify the supported cloud environments. If they can’t answer, factor that risk into your contingency plans.
  5. Tighten permissions during the migration. Graph’s permission model is stricter than EWS. Use this transition as a chance to reduce over-privileged access. Archive data is sensitive; grant only the minimum required permissions (e.g., Mail.ReadWrite, Mail.Export) to applications that truly need them, and use application access policies if needed.
  6. Brief your compliance and legal teams. API changes aren’t just IT plumbing. If your organization faces regulatory retention requirements, the move from EWS to Graph directly impacts how email is preserved and produced. Make sure the stakeholders understand the timeline and your validation plan.

What to watch next

Microsoft has a habit of shipping features right before a deprecation deadline, and that can leave little room for error. August 2026 GA is currently on track for worldwide standard multi-tenant clouds, but sovereign and government clouds may lag. If you operate in those environments, follow Microsoft’s Message Center updates closely and be prepared for a possible scramble.

Also keep an eye on the import/export API documentation for updates around archive handling. The roadmap item promises a seamless view, but developers will still need to understand redirects for debugging. Watch for updated guidance on the Microsoft 365 Developer Blog.

Finally, remember that the October 2026 EWS disablement is not a full shutdown immediately; it’s a phased process where administrators can re-enable EWS for specific applications until April 2027. That gives you a limited safety net, but don’t count on it for archive-critical workloads. Use it only for last-mile remediation.

In the end, this roadmap item is a quiet but pivotal piece of Microsoft’s Exchange Online modernization puzzle. It means that by late summer 2026, Graph will finally be able to reach every corner of your email archives. The catch—and there’s always a catch—is that you have to be ready to use it. The months between August and October are your window. Don’t waste them.