What Is EWS? Exchange Web Services Meaning and Retirement

The short answer
EWS stands for Exchange Web Services, a SOAP/XML API Microsoft introduced with Exchange Server 2007 so applications can read and manage mailbox data such as email, calendars and contacts. Microsoft began disabling it in Exchange Online in October 2026, with full shutdown in April 2027. The replacement is Microsoft Graph.
EWS means Exchange Web Services, Microsoft's SOAP API for mailbox access. What it does, when Exchange Online turns it off (2026-27) and what replaces it.
On this page
- 01What is Exchange Web Services (EWS)?
- 02Is EWS being deprecated, and when does it stop working?
- 03Does the EWS retirement affect me as an Outlook or Apple Mail user?
- 04What breaks when EWS is switched off
- 05How does EWS work?
- 06EWS vs Microsoft Graph: what replaces it
- 07Common misconceptions about EWS retirement
- 08Where AI Emaily fits
EWS stands for Exchange Web Services. It is a SOAP/XML API that Microsoft introduced with Exchange Server 2007 so that applications can read and manage mailbox data such as email, calendars and contacts. In email and IT, that is what EWS means; this page does not cover other uses of the acronym.
It is also being switched off. Microsoft began disabling EWS in Exchange Online in October 2026, in a phased rollout, and plans to finish in April 2027. Exchange Server on your own hardware is not part of this change.
- Stands for: Exchange Web Services
- What it is: a SOAP (XML) API over HTTPS for programmatic access to Exchange mailboxes
- Replaced by: Microsoft Graph, a REST/JSON API
- Status: Exchange Online disablement began October 2026 and completes in April 2027
What is Exchange Web Services (EWS)?#
Exchange Web Services (EWS) lets a program read and change the contents of a mailbox, including messages, calendar events, contacts, tasks and folders, without going through the Outlook interface a person would use. Microsoft's documentation describes it as available for Exchange Online and for on-premises Exchange starting with Exchange Server 2007.
It is a server-side API, not a mail app. A backup tool, a CRM, a room-booking system or a signature manager uses EWS to reach many mailboxes at once. That is different from a protocol such as IMAP, which a single person's mail client uses to fetch their own mail.
Is EWS being deprecated, and when does it stop working?#
Yes, in Exchange Online. Microsoft announced in 2018 that EWS would receive no more feature updates, and in 2023 it set October 2026 as the start of disablement. Microsoft's deprecation page, updated in October 2026, still describes a phased process rather than a single cut-off, and admins have controls that change when it hits a given tenant, so timing can differ between organizations.
Microsoft's Message Center notice (MC1227454) describes the October 2026 step as EWS being blocked by default unless a tenant has configured its own EWS settings, with admins able to allow listed applications until the April 2027 shutdown. Check your own admin center for how your tenant is set, because Microsoft has moved this timeline before.
| Date | What Microsoft says happens |
|---|---|
| July 2018 | Microsoft announces EWS will get no further feature updates; Microsoft Graph becomes the path forward. |
| 2023 | Microsoft sets October 2026 as the start of EWS disablement in Exchange Online, for non-Microsoft apps first. |
| January 2024 | The Midnight Blizzard security incident involves EWS; the effort widens to include Microsoft's own applications. |
| 2025 | Microsoft ships EWS usage reports, an EWS analyzer tool, and controls for admins to disable EWS at organization and user level. |
| October 2026 | EWS starts to be disabled globally for all Exchange Online organizations, in a phased rollout. This has now begun. |
| April 2027 | EWS is fully disabled in Exchange Online. |
This is Exchange Online only
Does the EWS retirement affect me as an Outlook or Apple Mail user?#
It depends on which app you read mail in. The retirement targets anything that calls EWS against an Exchange Online mailbox, and a few popular mail clients do exactly that.
| Your mail app | Affected? | What to know |
|---|---|---|
| Legacy Outlook for Mac | Yes | Microsoft says it stops working against Exchange Online mailboxes from October 2026, because it uses EWS. The fix is the current Outlook for Mac. |
| Apple Mail on a Mac, Microsoft 365 work or school account | Yes | Apple's Mac Mail and Calendar use EWS for Exchange. Apple says it is working with Microsoft to move to Graph in a future macOS 27 update and gives no firm date. Admins can allow EWS until April 2027, or you can use a Graph-based client. |
| Apple Mail on iPhone and iPad | Not by this change | Apple lists Exchange Online on iOS and iPadOS as connecting with Exchange ActiveSync, not EWS. |
| Current Outlook (new Outlook for Mac, Outlook for Windows, Outlook on the web, Outlook mobile) | No migration on your side | Microsoft says it is removing EWS dependencies from its own products. Ask your admin if something specific stops syncing. |
| Third-party mail clients and add-ins | Depends | Check the vendor. Any client that still calls EWS against Exchange Online is in scope. |
Apple's status can change
What breaks when EWS is switched off#
Any app that still calls EWS against an Exchange Online mailbox stops working once EWS is disabled for that tenant. That includes older mail clients, backup and e-discovery tools, migration utilities, room and resource booking systems, CRM sync, email signature managers and in-house scripts.
A blocked request comes back as HTTP 403 Forbidden with an X-EWS-Policy-Reason header, which reads either that EWS is disabled for the user or tenant, or that it is blocked by policy. Admins can inspect the EwsEnabled and EwsAllowedAppIDs settings, and changes to the allow list can take up to 24 hours to apply.
The fix for builders is to move those apps to Microsoft Graph. Microsoft publishes EWS usage reports in the Microsoft 365 admin center, an EWS analyzer tool and EWS-to-Graph operation mappings to help find what still depends on EWS.
How does EWS work?#
An EWS client sends a request as a SOAP envelope, an XML document, over HTTPS to a single endpoint on the Exchange server, and the server replies with XML. Most developers use the EWS Managed API, a .NET library that wraps the raw SOAP calls, though you can also call the service directly.
Clients rarely hard-code the address. They use Autodiscover, a Microsoft service that returns the correct EWS endpoint for a given mailbox. Basic auth is no longer available in Exchange Online, so an app signs in with OAuth 2.0.
One feature made EWS popular for service apps: impersonation. EWS impersonation lets a service account, granted the right role, act as though it were another user, so one application can reach many mailboxes without holding each person's password. Backup, archiving, migration and CRM tools leaned on this heavily. That broad reach is part of why the January 2024 Midnight Blizzard incident, which Microsoft says involved EWS, raised the urgency of retiring it.
EWS vs Microsoft Graph: what replaces it#
Microsoft Graph is the replacement. It is a single REST API for Microsoft 365, covering mail, calendars and contacts along with Teams, files and users, using JSON instead of XML. For a plain-language tour, see what the Microsoft Graph mail API is.
Microsoft says many scenarios already map directly from EWS operations to Graph, but not everything does. Its roadmap lists remaining gaps with target dates, several in Q4 2026, such as import and export for archive and public folder mailboxes. It also says a few EWS capabilities will not come to Graph at all: generic public folder create/read/update/delete, generic Microsoft 365 Group mailbox access, and Discovery Mailbox access.

| Dimension | Exchange Web Services (EWS) | Microsoft Graph |
|---|---|---|
| Format | SOAP requests and responses in XML | REST requests, JSON responses |
| Endpoint | One Exchange endpoint, e.g. /EWS/Exchange.asmx | graph.microsoft.com, one API across Microsoft 365 |
| Authentication | OAuth 2.0 required in Exchange Online; Basic and NTLM historically | OAuth 2.0 with Microsoft Entra ID |
| Change notifications | Push, pull and streaming notifications | Webhooks (change notifications) and delta queries |
| Status in Exchange Online | Deprecated; disablement began October 2026, full in April 2027 | Actively developed; Microsoft's recommended API |
Common misconceptions about EWS retirement#
- Myth: EWS is disappearing everywhere. Reality: the retirement is for Exchange Online only. Exchange Server on-premises keeps EWS.
- Myth: EWS stops on a single day. Reality: it is phased. Disablement began in October 2026 and completes in April 2027, and admins can influence it with allow lists and settings.
- Myth: only developers are affected. Reality: people using legacy Outlook for Mac, or Apple Mail on a Mac with a Microsoft 365 work account, are affected too. Current Outlook apps are not something you migrate yourself.
Where AI Emaily fits#
You might be reading this because an app you rely on is losing EWS access, so here is what a mail client can and cannot do. AI Emaily is a mail client, an AI chief of staff that helps triage your inbox and drafts replies you approve before anything sends. It is not an EWS integration and not a migration tool.
It connects to your own signed-in Outlook or Microsoft 365 mailbox through Microsoft's OAuth sign-in and the Graph API, not EWS, so the retirement does not change how you add an account. That means your own mailbox only: no shared mailboxes and no send-as. If Apple Mail on your Mac stopped syncing a Microsoft 365 account, a client that connects through Graph, such as Outlook or AI Emaily, is one way around it until Apple ships its update. What AI Emaily does not do is move a custom in-house app or a third-party tool off EWS; for that you need Microsoft's EWS-to-Graph mappings and analyzer tools, and usually a developer.
Frequently asked
See it in AI Emaily
Keep reading
Sources
- Microsoft Learn: Deprecation of Exchange Web Services in Exchange Online
- Microsoft 365 Developer Blog: Retirement of Exchange Web Services in Exchange Online
- Microsoft Community Hub: Exchange Online EWS, Your Time is Almost Up
- Microsoft Learn: Control access to EWS in Exchange
- Microsoft Support: End of support for legacy Outlook for Mac
- Apple Platform Deployment: Microsoft Exchange and Graph on Apple devices
- Microsoft Graph documentation

Written by
Nafiul HasanNafiul Hasan is an entrepreneur and AI automation system builder with 10+ years of experience turning messy, manual workflows into reliable automated systems. He designs and ships AI enterprise solutions end-to-end — the agent logic, the data plumbing, and the product people actually use — and founded AI Emaily to give busy professionals their attention back. He writes here from the builder's seat: what works, what breaks, and how to put AI to work without giving up control.