Microsoft has laid out a timeline for the disablement and shutdown of Exchange Web Services (EWS) in Microsoft 365 and Exchange Online.

[1]October 1, 2026, is when EWS will be disabled by default , although tenants can keep the lights on a little longer by setting the EWSEnabled flag to true by August, but the service will be shut down entirely on April 1, 2027.

EWS has long been deprecated, and Microsoft announced its retirement in [2]2023 . The noose tightened in 2025, with [3]confirmation that certain license types (F1 or F2) would be blocked from using it.

[4]

The service is an API that allows applications to access mailboxes and data stores in Exchange Online and Exchange Server. It dates back to Exchange Server 2007, and has proven popular with integrators and third parties (as well as in-house applications such as Outlook Classic). It is also popular with miscreants. Following the [5]Midnight Blizzard security incident , Microsoft "elevated the urgency" of pushing the tech out to pasture.

[6]Microsoft declares 'reliability' a priority for Visual Studio AI

[7]Microsoft sets Copilot agents loose on your OneDrive files

[8]Satya Nadella decides Microsoft needs an engineering quality czar

[9]Microsoft actually does something useful, adds Sysmon to Windows

The retirement only applies to Microsoft 365 and Exchange Online. Nothing will change regarding EWS in Exchange Server.

The timeline means affected administrators who have not yet begun or completed a migration will need to get moving. Microsoft's preference is a move to Microsoft Graph. However, it noted the service is just at "near-complete" feature parity and even Microsoft itself had yet to conclude the migration of all its impacted applications.

[10]

To focus minds, Microsoft also said it "may perform temporary 'scream tests'" where it turns EWS off and on to expose hidden dependencies. It did not disclose how an administrator would differentiate a "scream test" from one of the [11]depressingly regular outages that plague its online services . Was it deliberate, or did someone screw up a configuration file again?

Microsoft said: "We will provide more information in the coming weeks."

[12]

For administrators hoping Microsoft might blink and allow the service to run past the termination date, it said: "There will be no exceptions past April 2027." ®

Get our [13]Tech Resources



[1] https://techcommunity.microsoft.com/blog/exchange/exchange-online-ews-your-time-is-almost-up/4492361

[2] https://devblogs.microsoft.com/microsoft365dev/retirement-of-exchange-web-services-in-exchange-online/

[3] https://www.theregister.com/2025/12/03/microsoft_exchange_web_services_mailboxes/

[4] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/applications&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=2&c=2aYYeNjTVGpasd3I8RggI4QAAAsc&t=ct%3Dns%26unitnum%3D2%26raptor%3Dcondor%26pos%3Dtop%26test%3D0

[5] https://www.theregister.com/2024/01/27/microsoft_cozy_bear_mfa/

[6] https://www.theregister.com/2026/02/05/microsoft_visual_studio_ai/

[7] https://www.theregister.com/2026/02/05/microsoft_onedrive_agents/

[8] https://www.theregister.com/2026/02/05/microsoft_appoints_quality_chief/

[9] https://www.theregister.com/2026/02/04/microsoft_adds_sysmon_to_windows/

[10] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/applications&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44aYYeNjTVGpasd3I8RggI4QAAAsc&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0

[11] https://www.theregister.com/2026/01/23/microsoft_365_outage/

[12] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/applications&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44aYYeNjTVGpasd3I8RggI4QAAAsc&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0

[13] https://whitepapers.theregister.com/