Microsoft is switching off EWS in Exchange Online: what stops working, and what to do before April 2027

Since October 2026 Microsoft has been turning off Exchange Web Services in Microsoft 365 organisations one by one. Backup tools, migration tools, Apple Mail on the Mac and older Outlook builds can stop working with little warning. How to tell whether it has happened to you, how to switch it back on for now, and what has to change before April 2027.

Published Facts checked 7 min read
The EWS retirement in Exchange Online. From 1 October 2026 Microsoft builds an allow list of the apps it saw using EWS in the last 60 days and then turns EWS off for organisations on the default setting, after a 7-day Message Center warning. Until 1 April 2027 administrators can turn it back on themselves. From 1 April 2027 EWS is off for good, with no exceptions. Exchange Server on-premises is not affected.
Microsoft calls this the first stage. The switch to turn EWS back on lasts only until April 2027.

Exchange Web Services (EWS) is the old interface that many programs use to read and write mail in Microsoft 365: backup and archiving products, migration tools, CRM add-ons that file emails, scripts, Apple’s Mail and Calendar on the Mac, and older Outlook builds. Microsoft announced in 2023 that EWS in Exchange Online would retire, and it is now happening.

In short:

  • It has started. Microsoft’s Exchange Team says organisations on the default setting get a 7-day warning in Message Center, and then EWS is turned off: “This process has now started.”
  • You can turn it back on, for now. An administrator can re-enable it in a few clicks. Microsoft support cannot do it for you.
  • It ends for good on 1 April 2027. Microsoft’s FAQ: “There will be no exceptions past April 2027.”
  • On-premises Exchange is not affected. “There are no changes to EWS in Exchange Server.”

What is EWS, and what uses it

EWS is how many non-Microsoft programs talk to an Exchange mailbox. Microsoft’s own list of things that can break when it is turned off, from its post for administrators whose apps stopped working, is:

  • Apple Mail and Calendar on macOS;
  • classic Outlook on macOS (the new Outlook for Mac is not affected);
  • some Outlook desktop add-ins;
  • outdated versions of Outlook for Windows (Microsoft says to be on the August 2026 build 16.0.20430.20092 or later);
  • “various other applications such as backup applications that our customers purchase from various software vendors”.

Add to that migration tools, archiving and e-discovery products, CRM and helpdesk integrations that save or send email, and in-house scripts written years ago. The replacement is Microsoft Graph, but some EWS features have no Graph equivalent yet, which is why some vendors are late.

The timeline

WhenWhat happens
2023Microsoft announces the retirement of EWS in Exchange Online.
Late July 2026Administrators can keep EWS on for chosen apps only, with an allow list (EWSAllowedAppIDs).
From 1 October 2026Enforcement begins. For organisations on the default setting, Microsoft fills the allow list “based on 60-day usage” and then turns EWS off, after a 7-day warning in Message Center.
Until 1 April 2027Administrators can turn EWS back on themselves.
1 April 2027“Full retirement begins.” No exceptions.

Organisations that had already set EWS to on with an allow list are left alone until April 2027: “If the tenant is already set to EWSEnabled = True, Microsoft will not make changes to EWS availability until April 2027.”

One detail catches people out. Microsoft builds the allow list from what it saw in the last 60 days. A tool that runs quarterly, a year-end export, or a rarely used integration may not be on it, and it stops working the next time it runs.

How to tell whether this has happened to you

1. Check Message Center. In the Microsoft 365 admin center, search Message Center for posts titled “Action may be required: EWS will be disabled in your tenant in 7 days” or “EWS has been disabled in your tenant”. These are the subjects Microsoft gives in its post.

2. Run the EWS usage report. Microsoft’s EWS usage report is in the admin center: “On the Usage page, under Reports, select Exchange. On the report page, select the EWS usage tab.” It lists the applications that used EWS, filtered over 7, 30 or 90 days. Usage is “aggregated weekly, not daily”, and “it can take up to 10 days for usage to show in the report”, so a tool used yesterday may not appear yet.

3. Ask the vendor. For backup, migration and archiving products, the vendor knows whether its product uses EWS and whether a Graph-based version exists.

What it looks like when an app is blocked. Microsoft’s developer documentation says Exchange Online then returns “HTTP 403 Forbidden with diagnostic information in the X-EWS-Policy-Reason response header”. To users, Microsoft warns, it can look like almost anything: apps “might give you various errors when EWS is turned off”.

If something stopped working: switch EWS back on for now

Only an administrator can do this; “Microsoft support cannot perform these steps for you.” Microsoft’s easiest option uses the Baseline security mode page in the Microsoft 365 admin center:

  1. Open Baseline security mode and select Block access to Exchange Web Services.
  2. Untick Block your entire organization from using EWS and select Apply change.
  3. Tick the same box again and select Apply change again.

Confusingly, the result is that EWS is allowed for the apps on the allow list. Microsoft explains that “while you have checked / selected the ‘Block’ setting, the underlying setting on your tenant is now actually set to allow EWS (EWSEnabled = True) with a specific app(s) in the EWS allow list.” The same page shows which apps are on the list.

In Exchange Online PowerShell the equivalent is:

Set-OrganizationConfig -EWSEnabled $true

The change “usually takes less than an hour to start working”, up to 4 hours in rare cases. Adding or removing an app on the allow list takes 24 hours. And this works “only temporarily (until April 2027)”.

What has to change before April 2027

  • For each tool on the report, get a date from its vendor for a version that uses Microsoft Graph. If there is none, plan a replacement.
  • Apple Mail and Calendar on the Mac: the new Outlook for Mac, Outlook on the web, or Apple’s own fix if one arrives.
  • Classic Outlook for Mac: switch to the new Outlook for Mac.
  • In-house scripts: rewrite them against Microsoft Graph. Microsoft’s Graph mailbox import and export APIs move items between mailboxes, but Microsoft says these APIs “aren’t designed for mailbox backup and restore”, and the exported data is meant to be imported again, not read as files.

Where PST files come in

If an EWS-based tool was how you exported mailboxes or kept copies, it is worth taking those copies now, while the tool still works or EWS can still be turned back on. Microsoft’s own routes for mailbox data in PST form, eDiscovery export in Microsoft Purview and the PST Import service, are documented without any mention of EWS, and Microsoft does not list them among the things affected. For one mailbox at a time, classic Outlook’s own export also still writes a PST (our guide to exporting Outlook to PST).

Once you have PST files, check them before relying on them: open them, compare folder counts and spot-check messages, as our article on checking an export is complete describes. Mailtria’s PST Viewer opens a PST in the browser without Outlook or an account, which is useful for checking an export on any computer; it reads the file and never connects to your mailbox, so EWS plays no part in it.

Decision tree for an app that stopped working. Did a Message Center post say EWS was disabled in your organisation? If yes, turn EWS back on in Baseline security mode, then ask the vendor for a Microsoft Graph version. If no: does the app appear in the EWS usage report? If yes, check it is on the EWS allow list; changes take 24 hours. If no: was it last used more than 60 days ago? If yes, it may have been left off the allow list Microsoft built; add it. If no, the problem is probably not EWS.

Frequently asked

When exactly is EWS turned off? It depends on the organisation. Microsoft began turning it off from 1 October 2026 for organisations on the default setting, after a 7-day Message Center warning. Organisations that had set EWS to on with an allow list keep it until April 2027. From 1 April 2027 it is off everywhere in Exchange Online.

Can Microsoft support turn it back on for us? No. Microsoft says only the tenant administrator can re-enable it, using Baseline security mode or PowerShell, and only until April 2027.

Does this affect Outlook on Windows? Current Outlook for Windows keeps working; Microsoft says to be on the August 2026 build 16.0.20430.20092 or later. Outdated builds and some add-ins can break.

Does it affect our on-premises Exchange Server? No. Microsoft: “there are no changes to EWS in Exchange Server. EWS will continue to be fully supported for Exchange on-premise mailboxes.” Hybrid setups vary, so check any app that reaches cloud mailboxes.

Can we get an extension past April 2027? No. Microsoft’s FAQ answers that question directly: “There will be no exceptions past April 2027.”

Our backup tool uses EWS. Are our backups at risk? New backups stop once the tool is blocked. Turn EWS back on for now if needed, ask the vendor for its Graph-based version, and make sure the backups you already have can still be restored or read without the old tool.

Sources

This article is general information, not legal, security or professional advice. Services change their rules and screens; check the official pages linked above before you act, and keep a backup before changing your mail.