After nearly two decades of service, Exchange Web Services (EWS) is officially on its way out. Microsoft has announced that the EWS API for Exchange Online will be fully shut down on April 1, 2027, marking the end of a technology that once powered countless integrations with Outlook, calendars, and enterprise mailboxes.
The Retirement Timeline
- October 1, 2026 → Default blocking of EWS begins.
- August 2026 → Admins must configure allow lists to maintain temporary access.
- September 2026 → Microsoft auto-populates allow lists for tenants that haven’t acted.
- April 1, 2027 → Final shutdown of EWS in Exchange Online.
Microsoft may also run “scream tests”—temporary shutdowns—to expose hidden dependencies before the final cutoff.
Why EWS Is Going Away
EWS was introduced with Exchange Server 2007 and became a cross-platform API for accessing mailbox items like emails, meetings, and contacts. But after 20 years, it no longer aligns with modern requirements for security, scale, and reliability.
Instead, Microsoft is pushing developers toward the Microsoft Graph API, which now offers near-complete feature parity with EWS and is designed for today’s cloud-first ecosystem.
What This Means for Businesses
- Microsoft 365 / Exchange Online → EWS will be retired. Apps must migrate to Graph.
- On-Premises Exchange → EWS continues to function.
- Hybrid Scenarios → On-prem mailboxes can still use EWS, but cloud mailboxes must move to Graph. Only Exchange SE will support Graph calls to Exchange Online.
Action Items for IT Teams
- Audit dependencies → Identify apps and services still using EWS.
- Plan migration → Transition integrations to Microsoft Graph API.
- Prepare allow lists → Configure by August 2026 to avoid disruption.
- Test resilience → Watch for Microsoft’s “scream tests” to uncover hidden reliance.
- Educate developers → Ensure teams are trained on Graph API.
Client-side impact
Microsoft’s retirement of Exchange Web Services (EWS) for Exchange Online will affect Outlook clients differently depending on platform and version. Outlook for Windows, Mac, Android, and iOS are being updated to remove EWS dependencies and transition to Microsoft Graph, but older versions or third-party apps may lose functionality if they rely on EWS.
Impact on Outlook Clients by Platform
| Client | Impact | Action Required |
|---|---|---|
| Outlook for Windows | Minimal impact for current versions (Microsoft 365). Legacy versions may rely on EWS for calendar sync and add-ins. | Ensure latest Outlook version is deployed. Migrate add-ins to Graph. |
| Outlook for Mac | Older versions (pre-Outlook 2021) use EWS for mailbox access. Newer builds use REST/Graph. | Upgrade to latest Outlook for Mac. Validate mailbox access. |
| Outlook for Android/iOS | Mobile clients already use REST/Graph APIs. EWS retirement has no direct impact. | No action needed for native Outlook mobile apps. |
| Third-party apps | Many rely on EWS for calendar, contacts, and mail access. These will break after April 2027 unless migrated. | Developers must switch to Microsoft Graph API. |
Final Thoughts
The retirement of EWS is more than a technical change—it’s a signal of Microsoft’s broader shift toward Graph as the universal API layer for Microsoft 365. For IT leaders, this is the time to map dependencies, plan migrations, and embrace Graph as the future of Exchange Online integrations.
EWS served well for 20 years, but the future of Microsoft 365 connectivity is Graph.
Leave a Reply