Microsoft has officially postponed the full retirement of Exchange Web Services (EWS) to April 2027, with initial disablement as the default beginning in October 2026. At first glance, this feels like extra breathing room for IT teams and service providers managing Microsoft 365 migrations.
But there’s a critical nuance that MigrationWiz users need to understand:
Not all EWS-dependent workloads are guaranteed to be supported in Microsoft Graph.
The Real Risk: Feature Gaps in Microsoft Graph
Microsoft’s long-term direction is clear EWS is being phased out in favor of Microsoft Graph. However, as of today, there is no defined Graph replacement for several key workloads that many organizations still rely on:
- Public Folders
- Microsoft 365 Groups (certain migration scenarios)
- Archive Mailboxes
These workloads have historically depended on EWS for migration and access. Without equivalent Graph APIs, there is uncertainty around how or if these can be migrated seamlessly in the future.
Why This Matters for MigrationWiz Projects
MigrationWiz has long leveraged EWS to enable robust, scalable migrations across Exchange environments. For most standard mailbox and document migrations, the transition to Graph will be manageable.
But for the workloads listed above, EWS is not just a protocol, it’s a dependency.
Once EWS is disabled by default in October 2026:
- Access to these workloads may become restricted or inconsistent
- Migration timelines could become compressed and high-risk
- IT teams may face limited or no supported migration path
Waiting until the final retirement date in April 2027 is a gamble especially if Microsoft does not close these feature gaps in time.
What You Should Do Now
- Identify EWS-Dependent Workloads
Audit your environment and migration pipeline for:
- Legacy Public Folder usage
- Active Archive Mailboxes tied to compliance or retention
- Microsoft 365 Groups that may require cross-tenant or complex migrations
If any of these are in scope, they should be prioritized.
- Accelerate Migration Timelines
If you have planned migrations involving these workloads:
- Move them forward in your roadmap
- Avoid pushing them into late 2026 or beyond
- Build buffer time for testing and remediation
The safe window for EWS-based migrations is effectively now through mid-2026, not 2027.
- Validate Migration Paths with MigrationWiz
Ensure your current MigrationWiz configuration supports:
- The specific workload type
- Required permissions and endpoints (EWS-enabled)
- End-to-end testing before execution
Where possible, run pilot migrations to confirm there are no hidden blockers.
- Plan for Coexistence and Staged Transitions
If you can’t migrate everything immediately:
- Use coexistence strategies to segment and phase workloads
- Prioritize high-risk or unsupported workloads first
- Keep remaining migrations aligned with Graph-supported scenarios
Strategic Takeaway
The extension of EWS support is not a signal to delay it’s a limited opportunity to act.
Microsoft’s shift to Graph is accelerating, but gaps still exist. For MigrationWiz users, this creates a clear priority:
Migrate EWS-dependent workloads now, while the path is still fully supported.
Organizations that act early will avoid last-minute constraints, reduce migration risk, and maintain control over their timelines. Those that wait may find themselves navigating incomplete tooling, unsupported scenarios, or forced workarounds.
Final Thoughts
The migration landscape is evolving quickly, and protocol-level changes like the EWS retirement have real downstream impacts on execution.
If Public Folders, Archive Mailboxes, or Microsoft 365 Groups are part of your environment, this is not something to defer.