Exchange Online is switching off EWS: what stops working and what to do
Vetrox · Published
The short answer
Microsoft began switching off Exchange Web Services (EWS) in Exchange Online in October 2026, one tenant at a time, and turns it off for good on 1 April 2027. Apps that still use it stop connecting, among them Apple Mail and Calendar on a Mac, classic Outlook for Mac, some Outlook add-ins and backup tools. Until April 2027 a Microsoft 365 administrator can switch EWS back on; the lasting fix is a version of every app that does not need it.
What is changing
Exchange Web Services (EWS) is the interface many apps have used for nearly 20 years to read and write mailboxes, calendars and contacts in Exchange. In 2018 Microsoft said EWS would get no new features, and in 2023 that it would be switched off in Exchange Online in October 2026 (opens in a new tab). A security incident in January 2024 that involved EWS made the work more urgent, and Microsoft has since been taking EWS out of its own apps too. Its replacement is Microsoft Graph.
Microsoft is doing it tenant by tenant (a tenant is your organisation's own Microsoft 365 environment), in two stages (opens in a new tab):
- from October 2026, Microsoft turns EWS off after a notice in the Message Center of the Microsoft 365 admin center, and an administrator can still turn it back on
- from 1 April 2027, EWS is off for good: administrators can no longer turn it back on, and Microsoft says there will be no exceptions.
The change covers Microsoft 365 and Exchange Online only. EWS is not being retired in Exchange Server, the version a business runs on its own servers.
What to do before 1 April 2027
- 1
Check the Message Center
Has Microsoft warned you, or already turned EWS off?
- 2
List every app that still uses EWS
Use the EWS usage report, then check Macs, Outlook add-ins and backup tools
- 3
Turn EWS back on if something important stopped
A stopgap your administrator can use until April 2027
- 4
Fix each app for good
Update, replace or rewrite it, so nothing depends on EWS
Which apps stop working
Microsoft's list of apps that still use EWS (opens in a new tab) covers:
- Apple Mail and Calendar on a Mac
- classic Outlook for Mac
- some Outlook add-ins on the desktop
- outdated versions of Outlook for Windows
- other software that works with mailboxes, such as backup tools from other vendors.
When EWS is off, these apps keep asking for a username and password, or show an error saying EWS is not available. If a work account on a Mac suddenly keeps asking for its password, check this change first.
iPhones and iPads are a different case. Apple's deployment guide (opens in a new tab) says they connect to Exchange through Exchange ActiveSync, while Mail and Calendar on the Mac use EWS, so it is the Mac apps that are on Microsoft's list.
Software built for your business can stop as well: anything that reads a mailbox, files emails against a record or checks calendars through EWS goes down with the rest.
Step 1: Check whether EWS is off in your tenant
Microsoft is not switching every business off on the same day. What happens depends on a setting in your tenant that only an administrator can change. According to Microsoft's rollout notes (opens in a new tab):
- if nobody has ever changed the setting, Microsoft posts a notice in the Message Center seven days ahead, then turns EWS off
- if an administrator had already switched EWS on, Microsoft leaves it on until April 2027, for the apps on the tenant's allow list
- if an administrator had already switched EWS off, nothing changes.
To find out which applies to you, search the Message Center in the Microsoft 365 admin center for two notices: “Action may be required: EWS will be disabled in your tenant in 7 days” and “EWS has been disabled in your tenant”. Microsoft says either one shows when EWS is, or was, turned off in your tenant.
Every step in this guide needs someone with admin access to your Microsoft 365 tenant. If nobody in the business knows who that is, sort it out first.
Step 2: List every app that still uses EWS
The Microsoft 365 admin center has an EWS usage report (opens in a new tab): open Reports, then Usage, choose Exchange and select the EWS usage tab. It shows each app that called EWS in the last 7, 30 or 90 days, with how many calls it made and when it was last active. The data is collected weekly, so recent use can take up to 10 days to appear.
The report lists apps by application ID, not by name. Microsoft publishes the IDs of its own apps; for the others, it suggests looking in the enterprise applications in Microsoft Entra ID. For each one, write down which product it is, who in the business relies on it and who makes it. Then check the list against what people actually use:
- staff who read work mail in Apple Mail or Calendar on a Mac
- anyone still on classic Outlook for Mac or an old version of Outlook for Windows
- Outlook add-ins the team has installed
- mailbox backup and archiving tools
- software built for you that reads mailboxes or calendars, such as a booking page that checks free and busy times.
Who makes each app decides the fix in step 4: Microsoft, another vendor, or whoever built it for you.
Step 3: Turn EWS back on, but only to buy time
If Microsoft has turned EWS off and something the business depends on has stopped, your Microsoft 365 administrator can turn it back on. Microsoft support cannot do it for you. Microsoft explains two ways to do it (opens in a new tab): the Baseline security mode page in the Microsoft 365 admin center, or Exchange Online PowerShell. The change usually takes effect within an hour, and in rare cases takes up to four.
Before it turns EWS off, Microsoft fills in an allow list with the apps it saw using EWS in your tenant over the previous 60 days. Turned back on the way Microsoft's instructions describe, EWS then works only for the apps on that list. An app that was not used in that window has to be added, and changes to the list take 24 hours to apply.
Treat this as a stopgap. Microsoft says turning EWS back on stops working in April 2027, so give each app a date for its real fix instead of switching EWS on and forgetting about it.
Step 4: Fix each app for good
The lasting fix is a version of each app that does not use EWS. Microsoft's advice is to get an updated version from the vendor or, if you built the app yourself, to change its code. In practice:
- Outlook: keep Outlook for Windows on the latest builds, and move Mac users to the new Outlook for Mac, which Microsoft says (opens in a new tab) this change does not affect.
- Apple Mail and Calendar on a Mac: these are Apple's apps, so a version without EWS has to come from Apple. Until it does, the new Outlook for Mac keeps work mail and calendars running on a Mac.
- Add-ins, backup tools and other software you bought: ask each vendor whether their current version still uses EWS and, if it does, when the version without it is due. If the answer is after April 2027, or there is no answer, start looking for a replacement now.
Software built for you needs its code changed to use Microsoft Graph. Most of what EWS does has a direct replacement: Microsoft publishes a table that maps each EWS operation to its Graph API (opens in a new tab), such as reading, sending and moving messages or checking free and busy times. Some gaps remain. Microsoft's deprecation page (opens in a new tab) lists the ones it plans to close, with target dates, and a few it never will, such as general reading and writing of public folders. If a gap that affects you is on neither list, Microsoft says not to count on Graph closing it before EWS is switched off. Check what your software does against the table and both lists before you plan the work, and test the new version with EWS turned off.
Where Vetrox fits
Vetrox is an Australian IT company that looks after Microsoft 365 for businesses across Australia, in English or Mandarin. For this change, that means checking your tenant's notices and EWS usage report, listing every app that still uses EWS with the people who rely on it, turning EWS back on as a stopgap where something important has stopped, and moving your team to versions that do not need it. If software built for your business still uses EWS, we can move it to Microsoft Graph as part of our system integrations work.
Sources
- Microsoft Learn: Deprecation of Exchange Web Services in Exchange Online (opens in a new tab)
- Exchange Team Blog: Exchange Online EWS, Your Time is Almost Up (published 5 February 2026, updated 27 October 2026) (opens in a new tab)
- Exchange Team Blog: Exchange Online EWS application stopped working? Do this. (published 21 October 2026) (opens in a new tab)
- Apple Platform Deployment: Integrate Apple devices with Microsoft Exchange (published 14 April 2026) (opens in a new tab)
- Exchange Team Blog: EWS Deprecation Is Here, What This Means To You (published 1 October 2026, updated 26 October 2026) (opens in a new tab)
- Microsoft Learn: Exchange Web Services (EWS) usage report (opens in a new tab)
- Microsoft Learn: Exchange Web Services (EWS) to Microsoft Graph API mappings (opens in a new tab)