The news
Microsoft (MSFT) began switching off Exchange Web Services (EWS) in Exchange Online on October 1, 2026, starting the final phase of a retirement it first announced in 2023. Any app that still reads mail, calendars or contacts through EWS can stop working unless an administrator has explicitly allowed it.
EWS is an older programming interface that lets software connect to Exchange mailboxes. It sits behind many integrations businesses rarely think about: CRM email sync, archiving and backup tools, meeting-room booking systems, and custom scripts. According to The Register, Microsoft stopped building new features for EWS in 2018.
The rollout works through a tenant setting called EWSEnabled. The Register reported that Microsoft is changing tenants where that setting was never configured from null to false, which blocks EWS. Microsoft's own message center notice (MC1447678) says tenants with the setting unconfigured follow Microsoft's phased rollout, while tenants that set it to false are fully blocked.
For organizations that need more time, Microsoft introduced an allow list called EWSAllowedAppIDs. Administrators set EWSEnabled to true and list the application IDs that may keep using EWS. According to Microsoft's notice, from October 2026 a tenant with EWSEnabled set to true but no allow list will see all EWS traffic blocked, except cross-tenant organization relationships.
The allow list is a bridge, not an exemption. Microsoft has set April 1, 2027 as the date when EWS is permanently retired in Exchange Online, with no way to turn it back on. The Register quoted Microsoft as saying there will be no exceptions to that deadline. The change does not affect EWS in on-premises Exchange Server.
The numbers
- Phased EWS shutdown began
- October 1, 2026
- Permanent retirement in Exchange Online
- April 1, 2027
- Retirement first announced
- 2023
- New EWS feature development stopped
- 2018
Why CEOs should care
For CIOs and IT directors, the immediate risk is a quiet outage. An app that depends on EWS will not announce itself until calendar sync breaks or a mailbox archive stops running. Markus Müller, Boomi's global field CTO for API management, told The Register that many organizations lack a complete inventory of their EWS dependencies. The first job is to find them: Microsoft's notice tells admins to inventory EWS usage, build and test an allow list, and confirm connectivity.
For buyers and procurement teams, every third-party vendor that connects to Exchange Online should be asked a direct question: does your product still use EWS, and when will it run on Microsoft Graph? Get the answer in writing with a date before April 1, 2027. If a vendor cannot commit, that is a reason to plan a replacement now rather than in March.
For CISOs, the allow list is also a control. Listing only named, approved application IDs narrows which software can reach mailboxes through an older interface. Treat the list as temporary, review who owns each entry, and track each one to a Graph migration or a shutdown date.
The bigger picture
Microsoft's stated reason is that EWS no longer fits its current security, scale and reliability requirements, according to The Register. Its replacement is Microsoft Graph, the company's main API for Microsoft 365 data. Microsoft's February 2026 notice (MC1227454) describes Graph as offering near-complete API parity with EWS, while The Register reported that some capability gaps remain. Teams with heavy custom integrations should test their specific functions against Graph rather than assume a one-to-one swap.
What’s next
The next fixed date is April 1, 2027, when EWS is retired in Exchange Online for good. Between now and then, any app that is not on a tenant's allow list, or not yet moved to Microsoft Graph, is at risk of being blocked as Microsoft's phased rollout reaches more tenants.
What “Fact-checked” means
Fact-checking means testing a story’s facts against the evidence before it is published. This story went through at least two separate checks before this version was published.
- What we checked
- Its names, figures, dates, job titles, quotes and who said what were checked against the story’s sources, including its main source where it could be opened. The headline was checked for accuracy and overstatement.
- How
- A first check reviewed the whole story. If it passed, a second, skeptical check went back to the sources to look for mistakes in the most important facts. If a check flagged the story, it was edited to fix the problems found, and a separate re-check then reviewed the whole story again.
- Who
- The checks are made by our newsroom, as steps kept separate from the writing, under rules set by our editor, Hussein Mukhtar. A story the checks still flag is held for the editor, who decides whether it is fixed, published or dropped.
- If something is wrong
- “Fact-checked” does not mean error-free. If a material error is found after publication, we correct the story and add a note saying what changed. Report an error
Companies in this story








