Microsoft’s transition away from Exchange Web Services (EWS) is no longer a distant roadmap item it now has a definitive timeline. Microsoft has announced that EWS will begin to be disabled by default starting in October 2026, with full retirement planned for April 2027 as the company moves entirely toward Microsoft Graph.
For many organizations, this may seem like a routine platform modernization effort. But for MigrationWiz users and MSPs managing complex Microsoft 365 migrations, the implications are far more significant.
At this stage, Microsoft does not appear to have plans to fully support several critical migration scenarios through Microsoft Graph, including:
- Public Folder migrations
- Certain Microsoft 365 Group migration scenarios
- Archive Mailbox migrations
Organizations that still need to migrate any of these workloads should begin planning immediately and strongly consider accelerating migration timelines before October 1, 2026.
Why This Matters
EWS has been a foundational API layer for Exchange and Microsoft 365 migrations for years. Many migration tools including advanced migration scenarios have historically relied on EWS because of the deep mailbox and Exchange functionality it provides.
Microsoft Graph is the future direction for Microsoft 365 development and automation, but not all workloads currently supported through EWS have equivalent migration functionality in Graph today.
This creates a narrowing window for organizations that still depend on EWS-supported migration capabilities.
The Biggest Areas of Concern
Public Folders
Public Folders remain deeply embedded in many enterprise environments, particularly in:
- Government organizations
- Education institutions
- Healthcare environments
- Long-established enterprise Microsoft deployments
Despite their age, Public Folders continue to support operational workflows, shared mail-enabled data repositories, and collaborative communication models.
Currently, there does not appear to be full Graph-based parity for Public Folder migration scenarios. Organizations still relying on Public Folders should prioritize migration planning immediately.
Archive Mailboxes
Archive Mailboxes represent another area where long-term support questions remain.
Many organizations have:
- Large compliance archives
- Legal hold requirements
- Historical email retention mandates
Archive migrations are often deferred until late in projects because they are considered less urgent operationally. However, delaying these migrations could create serious risk if EWS functionality becomes unavailable before archive projects are completed.
Organizations should avoid treating archive migrations as “phase two” work that can wait indefinitely.
Microsoft 365 Groups
While Microsoft Graph supports many Microsoft 365 Group operations, certain migration scenarios still present limitations compared to traditional EWS-based workflows.
This becomes especially important in:
- Tenant-to-tenant migrations
- M&A consolidations
- Cross-tenant collaboration restructuring
- Long-term coexistence projects
Organizations with complex Groups migration requirements should validate their timelines and migration strategies well ahead of the EWS disablement schedule.
Why Waiting Is Risky
Many organizations assume they still have plenty of time because full EWS retirement is scheduled for April 2027. However, the more important milestone is likely October 2026, when Microsoft plans to begin disabling EWS by default.
That distinction matters.
Once EWS becomes disabled by default:
- Migration workflows may require additional exceptions or configuration changes
- Project complexity could increase significantly
- Microsoft support posture may shift toward Graph-only guidance
- Migration timelines could become compressed as organizations rush to complete projects simultaneously
Historically, major Microsoft platform transitions create a surge in late-stage migration demand. Organizations that wait too long may face:
- Resource shortages
- MSP scheduling delays
- Compressed testing windows
- Increased project risk
Why MSPs Should Be Proactive
For MSPs, this transition represents both a risk and an opportunity.
Customers who still have:
- Public Folders
- Archive Mailboxes
- Complex Microsoft 365 Group structures
will need guidance and migration planning sooner rather than later.
MSPs that proactively educate customers now can:
- Position themselves as strategic advisors
- Secure migration projects earlier
- Avoid last-minute project compression
- Better allocate engineering resources over the next 12–18 months
Waiting until 2026 will likely create operational bottlenecks across the industry.
Migration Planning Should Start Now
Organizations do not necessarily need to execute migrations immediately, but they should begin:
- Assessing EWS-dependent workloads
- Identifying unsupported Graph migration gaps
- Building phased migration plans
- Prioritizing legacy Exchange dependencies
- Validating coexistence requirements
This is especially important for enterprise environments where migration timelines may span many months.
The Role of MigrationWiz
MigrationWiz continues helping organizations modernize Microsoft 365 environments by simplifying mailbox, document, Teams, and collaboration workload migrations.
For organizations still relying on EWS-supported migration scenarios, MigrationWiz provides an opportunity to complete these projects while EWS functionality remains available.
However, organizations should avoid assuming these migration windows will remain open indefinitely.
Final Thoughts
Microsoft’s transition from EWS to Microsoft Graph represents a major architectural shift for the Microsoft 365 ecosystem. While Graph will continue expanding, there are still important migration scenarios that do not appear to have complete feature parity today.
For organizations with:
- Public Folders
- Archive Mailboxes
- Complex Microsoft 365 Group migration requirements
the safest strategy is clear: accelerate migration planning before October 2026.
The organizations that begin preparing now will have the greatest flexibility, the lowest risk, and the best chance of avoiding last-minute migration pressure as EWS retirement approaches.