If your organization runs any custom email automation, CRM integration, calendar synchronization, or third-party backup tools connected to Microsoft 365, you have a hard deadline to hit. Microsoft is retiring Exchange Web Services, and the clock is already running.
Phased blocking of EWS begins October 1, 2026. The service is permanently retired on April 1, 2027. Microsoft recommends migrating to Microsoft Graph, its modern API platform, before those dates. Organizations that miss them will not get a grace period.
What is Exchange Web Services?
EWS launched in 2007 as Microsoft’s primary API for programmatic access to Exchange data, email, calendars, contacts, mailbox management, and task automation. For nearly two decades, it became the backbone of an enormous range of enterprise tools: migration platforms, backup solutions, CRM connectors, compliance software, and custom-built internal applications.
The reason EWS became so embedded is simple. It worked, it was well-documented, and for a long time it was the only serious option for developers who needed deep Exchange access. Many enterprise applications built on it never moved because the incentive to migrate was low and the risk of breaking something was real.
That calculation has now changed.
Why Microsoft is Retiring Exchange Web Services?
EWS uses legacy authentication protocols that conflict with modern security requirements. As Microsoft has pushed toward Zero Trust architecture and conditional access policies across Microsoft 365, EWS has become increasingly difficult to secure consistently.
Microsoft Graph was built from scratch with OAuth 2.0, modern authentication, and a REST-based design that aligns with how cloud APIs are built today. It covers the majority of what EWS offered, email, calendar, contacts, mailbox data, with better permission scoping, stronger audit trails, and ongoing investment from Microsoft’s developer platform teams.
EWS, by contrast, has been in maintenance mode for years. No new features. No meaningful security improvements. The retirement is less a surprise than a formalization of a trajectory that has been clear since at least 2020.
What Replaces Exchange Web Services?
Microsoft Graph is the official replacement. It provides REST APIs with modern authentication for accessing the same Exchange Online data that EWS historically served, alongside broader Microsoft 365 integration, Teams, SharePoint, OneDrive, and more.
For most EWS use cases, a direct equivalent exists in Graph. The migration is not always simple, but the destination is well-supported. Microsoft has published migration documentation and provides tooling to help developers map EWS calls to Graph endpoints.
One important distinction: Exchange Server on-premises is not affected. The retirement applies specifically to Exchange Online within Microsoft 365. Organizations running hybrid or fully on-premises Exchange deployments can continue using EWS on those systems.
Who is Affected with the Retirement of Exchange Web Services
The scope is wider than most IT teams initially assume.
Businesses and enterprise IT teams running any of the following should treat this as urgent:
- Custom-built internal applications that access Exchange mailboxes
- CRM platforms with Exchange calendar or email sync (Salesforce, Dynamics, HubSpot integrations).
- Email migration tools, almost all major migration platforms use EWS.
- Backup and archiving solutions from vendors like Veeam, Barracuda, or Mimecast.
- Compliance and eDiscovery tools.
- Help desk software with Exchange integration.
- Mail automation scripts written by internal developers.
Developers with applications in production that authenticate against Exchange Online via EWS need to begin the migration to Graph endpoints now. Test environments should be validated against Graph before October.
SaaS vendors and Microsoft partners whose products connect to customer Microsoft 365 tenants via EWS face the most urgent pressure, they need to update their products and notify customers before October 1, not after.
Timeline
Date | What Happens |
Now | Audit all EWS-dependent applications and integrations |
October 1, 2026 | Microsoft begins phased EWS blocking in Exchange Online |
April 1, 2027 | EWS permanently retired from Exchange Online |
Post-April 2027 | On-premises Exchange Server unaffected; continues to support EWS |
The phased blocking from October onward is worth understanding carefully. Microsoft has not published a precise rollout schedule for which tenants or scenarios get blocked first. That uncertainty means organizations should not treat October 1 as the moment to begin preparation, it should be treated as the moment preparation must be complete.
What Organizations Should Do Now
- Audit first: Many IT teams genuinely do not know every application touching their Exchange environment via EWS. Start by pulling application access logs from the Microsoft 365 admin center. The EWS usage report in Exchange Online shows which applications are making EWS calls and how frequently.
- Contact your vendors: Third-party software providers whose products use EWS should already be working on Graph migration. If your backup vendor, CRM provider, or migration tool has not communicated a roadmap, ask for one in writing now.
- Prioritize by risk: A backup solution that stops working post-retirement is a more serious problem than a low-volume reporting script. Rank your EWS dependencies by business impact and migrate accordingly.
- Build in testing time: Graph behaves differently from EWS in several areas, throttling policies, permission models, and response formats. Applications rewritten for Graph need proper integration testing before they touch production data.
- Train IT staff: Teams that have spent years working with EWS will need to build familiarity with Graph’s authentication flow and API structure. Microsoft Learn has free Graph documentation and training paths.
What Happens If You Miss the Deadline
This is where the stakes become concrete.
Email automation workflows stop functioning. CRM platforms lose calendar and contact synchronization. Migration tools, already in active use during a project, fail mid-transfer. Backup jobs that have been running nightly begin returning authentication errors. Compliance software loses the ability to pull mailbox data.
None of these failures announce themselves with a clear error message pointing to EWS retirement. Some will surface as authentication timeouts. Others as silent data gaps that only become visible during an audit or incident. The organizations most at risk are those that inherited legacy systems and lack full visibility into what connects to their Exchange environment.
Industry Impact
Email migration vendors are particularly exposed. Companies like BitTitan, Quest, and Cloudiway have built substantial product lines around EWS. Most are already working on Graph-based replacements, but the transition affects customers mid-project who might be running migrations that span the October or April deadlines.
Security and compliance vendors have similarly complex dependencies. eDiscovery tools that rely on EWS for mailbox crawling need full re-architecture in some cases, not just an endpoint swap.
For Microsoft partners reselling managed services, this is also a customer communication obligation. Clients running Microsoft 365 environments managed by an MSP should expect proactive outreach, if it has not arrived yet, that itself is useful information about the readiness of their provider.
Conclusion
Microsoft has given organizations a workable runway. The April 2027 retirement date means there is time to migrate properly, if the audit starts now.
The organizations that will experience real disruption are not those with complex EWS dependencies. They are the ones that assume someone else is handling it, or that the deadline will move. Microsoft has retired legacy Exchange features before and held to its announced dates.
Graph is the path forward. The documentation exists, the tooling is available, and the APIs cover the vast majority of what EWS provided. The transition is work, but it is finite work with a clear end state.
Start the audit this week.
FAQs
What is the Microsoft EWS retirement date?
Phased blocking begins October 1, 2026. Exchange Web Services is permanently retired from Exchange Online on April 1, 2027.
Does EWS retirement affect on-premises Exchange Server?
No. The retirement applies only to Exchange Online within Microsoft 365. Organizations running Exchange Server on-premises can continue using EWS on those deployments.
What replaces Exchange Web Services?
Microsoft Graph is the official replacement. It provides REST APIs with modern OAuth 2.0 authentication for accessing Exchange Online data including email, calendar, contacts, and mailbox management.
How do I find out if my organization uses EWS?
The Microsoft 365 admin center and Exchange Online admin center include EWS usage reports that show which applications are making EWS calls against your tenant. Third-party application inventories and developer audits should supplement this.
What happens if we do not migrate before the deadline?
Applications relying on EWS for Exchange Online access will stop functioning after April 1, 2027. This includes email automation, CRM integrations, backup tools, migration platforms, and any custom applications built on EWS.
