Microsoft is starting the final retirement phase for Exchange Web Services, or EWS, in Exchange Online on October 1, 2026. If your business uses Microsoft 365, that does not mean Outlook or Exchange Online suddenly stops working. The real risk is quieter: an app, backup product, calendar tool, CRM integration, or custom script may still depend on EWS behind the scenes.
Microsoft's current guidance says EWS will start to be disabled globally in October 2026, with full disablement planned for April 2027. That gives businesses a shrinking window to find old dependencies before they become interruptions.
What is EWS?
Exchange Web Services is an older way for software to connect to Exchange Online. For years, applications used EWS to read mailboxes, work with calendars, access contacts, move messages, and automate Exchange tasks.
Microsoft has been steering developers toward Microsoft Graph, its newer API platform for Microsoft 365. EWS stopped receiving new feature development years ago, and Microsoft is now moving into the final retirement phase for Exchange Online.
What changes on October 1, 2026?
October 1 is the start of the rollout, not a single worldwide off switch. Microsoft says EWS starts being disabled across Exchange Online organizations as the deployment rolls out. Microsoft has also introduced controls that let administrators explicitly allow approved EWS applications during the transition.
The important part for a business owner is simple: if an application still requires EWS and nobody has identified it, that application can eventually stop communicating with Exchange Online.
This retirement applies to Exchange Online in Microsoft 365. Microsoft says EWS in on-premises Exchange Server is not part of this retirement.
What kinds of applications could be affected?
The applications worth checking are usually the ones that quietly connect to email or calendars in the background. Examples include:
- Backup, archiving, and mailbox management products
- Calendar, scheduling, and room-booking integrations
- CRM, ticketing, and line-of-business applications that read or send email
- Migration, discovery, or compliance tools
- Custom scripts and older internal applications
- Third-party add-ons that have not yet moved to Microsoft Graph
Not every product in these categories uses EWS. The point is to verify the connection method instead of assuming a product is safe because it still works today.
Does this mean email on iPhones will stop working?
No, not as a general rule. The EWS retirement is not a shutdown of Microsoft 365 email, Exchange Online, or mobile email. A specific mobile app or integration would only be at risk if it still depends on EWS.
If employees use Outlook, Apple Mail, or another mobile email app, the right question is not simply, "Is it on an iPhone?" The question is whether that specific app, account configuration, or supporting integration is making EWS calls.
Why this can be easy to miss
A legacy integration can run for years without anyone thinking about it. Maybe it syncs appointments once an hour. Maybe a legal or accounting application files email into a client record. Maybe a backup platform touches Exchange in the background and nobody sees the connection until a restore is needed.
That is why waiting for an error message is a poor migration strategy. Microsoft recommends reviewing the EWS footprint of internal and third-party applications now, then moving supported workloads to Microsoft Graph.
What businesses should do now
- Review actual EWS usage. Ask whoever manages Microsoft 365 to check Microsoft's EWS usage reporting rather than relying on a software inventory alone.
- Identify the application owner. For every EWS connection, determine whether it belongs to Microsoft, a third-party vendor, or an internal script.
- Contact vendors now. Ask whether the product supports Microsoft Graph and whether an update or configuration change is required.
- Test important workflows. Pay special attention to backup, archiving, scheduling, CRM, compliance, and automated mailbox processes.
- Do not treat October 1 as the finish line. It is the beginning of the global disablement rollout. Microsoft currently lists April 2027 as the point when EWS is fully disabled in Exchange Online.
A good Microsoft 365 review should look beyond EWS
EWS is a useful reminder that cloud environments change continuously. A Microsoft 365 tenant can accumulate old applications, unused accounts, weak sign-in settings, stale permissions, and integrations that nobody remembers installing.
Iron Core helps businesses review Microsoft 365 configuration, security, licensing, and integrations as part of a broader managed IT and managed cybersecurity strategy. The goal is not just to react to Microsoft's next deadline. It is to know what is connected to your environment and why.
Microsoft sources: Deprecation of Exchange Web Services in Exchange Online and Exchange Online EWS, Your Time is Almost Up.
Stay up to date with Iron Core
Get practical guidance on Microsoft 365, cybersecurity, AI, and business technology. Add Iron Core as a preferred source on Google to see more of our articles in Search.