Microsoft is continuing its long-term shift toward modern, secure APIs and Exchange Web Services (EWS) is officially on the path to deprecation. While this change won’t happen overnight, the direction is clear: Microsoft Graph API will become the primary and eventually the only supported method for Exchange-based access and data transfers.
For many organizations, this transition will be manageable.
For others, particularly those still relying on Public Folders, the impact could be significant.
What’s Changing with EWS?
EWS has been a foundational service for Exchange integrations for well over a decade. It has powered everything from email access to mailbox migrations and Public Folder migrations.
Microsoft’s phased deprecation strategy will:
- Gradually limit and retire EWS functionality
- Shift supported data access and migration paths to Microsoft Graph API
- Encourage customers and vendors to modernize integrations
This transition aligns with Microsoft’s broader cloud and security strategy. However, feature parity does not yet exist across all workloads, creating real-world migration challenges.
The Public Folder Problem
The most pressing issue for many organizations is Public Folders.
At this time, Microsoft has not committed to support Public Folder migrations via Graph API once EWS deprecation is fully enforced. That creates a narrowing window for organizations that still rely on Public Folders to take action.
If your environment includes Public Folders, waiting carries real risk:
- Future migration options may be limited—or unavailable
- Projects may require complex workarounds or costly redesigns
- Timelines could be dictated by Microsoft’s deprecation schedule, not your business priorities
Once EWS-based migration paths are gone, Public Folders could effectively be stranded.
Why Acting Now Matters
Even though deprecation is phased, proactive planning is the smartest path forward. Organizations that begin migrating Public Folders to modern alternatives such as Shared Mailboxes benefit from:
- Proven, supported migration paths while EWS remains available
- Greater flexibility in timing and execution
- Reduced risk of rushed or incomplete projects later
For MSPs and IT teams managing multiple customer environments, this is especially critical. The closer EWS gets to retirement, the more unpredictable legacy Public Folder projects become.
Migrate Public Folders with Confidence
Not all migration tools support Public Folder migrations, and that window is closing.
MigrationWiz remains one of the few proven solutions that fully supports Public Folder migrations while EWS-based pathways are still available. Whether you’re modernizing collaboration, consolidating infrastructure, or executing a broader tenant-to-tenant migration, using the right licensing combination ensures a secure, predictable, and disruption-free transition.
To support a complete migration strategy, customers should leverage:
- MigrationWiz Public Folder licenses to securely migrate Public Folder data while EWS-supported pathways remain available
- Mailbox or UMB licenses to migrate associated user mailboxes, archives, and related data as part of a complete modernization effort
- Migration Agent to automate workstation and Outlook profile reconfiguration during full-project migrations, minimizing disruption and ensuring a smooth end-user cutover
The key is acting before EWS limitations begin impacting project timelines. Organizations that plan early retain control over scope, sequencing, and modernization strategy rather than reacting to Microsoft’s deprecation schedule.
A Clear Call to Action
If your organization or your customers still rely on Public Folders, now is the time to assess and begin migration planning.
Microsoft’s direction is clear: Graph API is the future. But until Public Folders are supported within that modern framework, EWS remains the only viable bridge and that bridge won’t be there forever.
Start planning your Public Folder migration today with MigrationWiz and secure a supported path forward before your options narrow.