Exchange ActiveSync (EAS): What It Is and Who Still Uses It

The short answer
Exchange ActiveSync (EAS) is Microsoft's protocol for syncing email, calendar, contacts and tasks from an Exchange or Microsoft 365 mailbox to a phone, with server push and device policies such as remote wipe and PIN rules. Exchange Online still supports it, but Microsoft points developers to Microsoft Graph for new work.
Exchange ActiveSync (EAS) syncs mail, calendar, contacts and device policy to phones. What it does, how it differs from IMAP and Graph, and its status.
On this page
- 01Exchange ActiveSync vs IMAP vs Microsoft Graph
- 02What is EAS (Exchange ActiveSync) and what does it do on a phone?
- 03How does Exchange ActiveSync work?
- 04Is Exchange ActiveSync still supported?
- 05What does EAS activated mean in Intune or Exchange?
- 06Common misconceptions about Exchange ActiveSync
- 07How this shows up in AI Emaily
Exchange ActiveSync (EAS) is Microsoft's protocol for syncing a phone with an Exchange or Microsoft 365 mailbox: email, calendar, contacts and tasks, plus server-pushed new mail and device rules such as a required PIN or a remote wipe. You will also see it written as ActiveSync or EAS.
It is still in use. Microsoft documents EAS as supported in Exchange Online, and Apple lists it as the way iPhone and iPad Mail connect to Exchange Online. What has changed is the direction of travel: developers are told to build on Microsoft Graph, and Outlook for iOS and Android does not use EAS.
- Syncs: mail, calendar, contacts and tasks over one authenticated HTTPS connection
- Push: the server notifies the device when something changes, instead of the phone polling
- Device policy: PIN rules, encryption requirements and remote wipe, set by an admin
- Ownership: proprietary to Microsoft, with a published specification and licensed use
Exchange ActiveSync vs IMAP vs Microsoft Graph#
The three are all paths to mail on a remote server, but they differ in scope, design and who they are for.

| Dimension | Exchange ActiveSync | IMAP | Microsoft Graph |
|---|---|---|---|
| Protocol type | Microsoft's, specification published, licensed use | Open standard (IETF RFC 3501) | Microsoft's REST API |
| Wire format | Binary XML (WBXML) over HTTPS | Text commands over TCP (port 143, or 993 with TLS) | JSON over HTTPS |
| Push email | Yes, long-poll from the server | Only with extensions such as IDLE; otherwise the client polls | Yes, via change notifications |
| Syncs email | Yes | Yes | Yes |
| Syncs calendar and contacts | Yes | No | Yes |
| Syncs tasks | Yes | No | Yes (through Microsoft To Do) |
| Device management | Yes: remote wipe, PIN, encryption policy | No | No; handled by MDM separately |
| Authentication on Exchange Online | OAuth 2.0 (Basic auth is disabled) | OAuth 2.0 (Basic auth is disabled) | OAuth 2.0 |
| Microsoft's direction | Supported on Exchange Online; developers pointed to Graph | Supported on Exchange Online with OAuth | Recommended for new development |
What is EAS (Exchange ActiveSync) and what does it do on a phone?#
On a phone, EAS keeps your inbox, calendar, contacts and tasks in step with your Exchange or Microsoft 365 mailbox, and lets the server push new mail instead of waiting for the phone to ask. Microsoft's documentation describes it as a protocol based on HTTP and XML, optimized for high-latency and low-bandwidth networks. Microsoft first shipped it in the Exchange Server 2003 era.
Compared with IMAP, EAS was built to solve three things IMAP handled poorly or not at all. Push delivery is the most visible. Unified sync is the second: IMAP carries mail only, so calendars and contacts would need separate CalDAV and CardDAV connections. Device management is the sharpest difference. An Exchange admin can set EAS policy such as a minimum password length, device locking, encryption requirements and a remote wipe for a lost phone, which IMAP has no equivalent for. That is the origin of the phrase EAS policy.
Without EAS, organizations that need device control use a Mobile Device Management tool such as Microsoft Intune, Jamf or Workspace ONE, which enforces policy at the device layer rather than inside the mail protocol.
How does Exchange ActiveSync work?#
EAS carries its data as a compact binary encoding of XML called WBXML, sent over HTTPS to a single endpoint. The device authenticates, then issues HTTP POST requests with a command such as FolderSync, Sync or Search, and the server answers with the relevant data. After the first sync it receives only changes since the last one, which keeps ongoing bandwidth low.
Push works through long-polling. The device opens a request and the server holds it open until new mail arrives or a wait interval expires, then the device immediately asks again. That produces near-instant delivery at the cost of a standing connection, which is one reason newer push systems and Microsoft Graph change notifications moved away from it.
Device management travels on the same connection. An admin issues a remote wipe from the Exchange admin center, the server queues it, and the device carries it out the next time it checks in. Password and encryption policy works the same way: the server sends a policy document, and the device has to acknowledge and enforce it before sync completes.
EAS runs entirely over HTTPS on port 443
Is Exchange ActiveSync still supported?#
Yes. Exchange Online supports EAS, and Apple's deployment guide lists Exchange Online with EAS 16.1 for iOS and iPadOS, so the built-in Mail app on an iPhone still uses it. We found no Microsoft announcement setting an end date for EAS itself on Exchange Online. Three things have tightened, though:
- Basic authentication: Microsoft began disabling Basic auth for EAS in Exchange Online on October 1, 2022, and after extensions it is now disabled in all tenants. A phone that stopped syncing around then was usually using a client that still sent a username and password.
- Minimum version: Microsoft's Message Center notice MC1197103 said devices using EAS versions below 16.1 can no longer connect to Exchange Online from March 2026, and that Outlook mobile is not affected because it does not use EAS. Confirm the current rule in your own admin center.
- Outlook for iOS and Android: Microsoft describes it as built on the Microsoft cloud with its own native sync to Exchange Online rather than EAS, and it recommends it for Exchange Online. The Mac side is different: Apple Mail on a Mac uses EWS, not EAS, and that is being retired. See what EWS is.
Basic auth for EAS is gone on Exchange Online
What does EAS activated mean in Intune or Exchange?#
In Intune's conditional access setup for Exchange, the Exchange connector reads the ActiveSync records on the Exchange side and matches them to Intune device records, so Intune can decide whether a device may get mail. A device list showing EAS activated is generally read as the device having an ActiveSync record that Intune has matched.
Microsoft does not define that label in one obvious place we could find, so treat this as the common reading and check your tenant's Intune and Exchange documentation or ask your admin for the exact rule.
Common misconceptions about Exchange ActiveSync#
- Myth: EAS is the same as IMAP. Reality: IMAP is an open IETF standard for email only. EAS is Microsoft's protocol and also carries calendar, contacts, tasks and device policy. A client that supports one does not automatically support the other.
- Myth: EAS is an open standard because the spec is public. Reality: Microsoft publishes the EAS specification, but implementing it commercially is done under a Microsoft licence. Publication is not the same as open licensing.
- Myth: EAS and EWS are the same thing. Reality: EAS syncs mobile devices; EWS is a SOAP API for programmatic mailbox access by apps and some Mac clients. They are retired on different schedules, and EWS is the one being switched off in Exchange Online.
How this shows up in AI Emaily#
AI Emaily does not use Exchange ActiveSync. It connects Outlook and Microsoft 365 through Microsoft Graph for the mailbox you sign in with, so no shared mailboxes and no send-as. Gmail connects through the Gmail API, and iCloud, Yahoo, Fastmail and other providers connect over IMAP.
Because it does not use EAS, AI Emaily does not issue or respond to EAS device policy such as remote wipe or PIN rules. Those stay with your organization's MDM or Exchange admin settings, and any policy your IT team applies to your phone still applies. If you are choosing a client for an Exchange mailbox, see the best email client for Exchange accounts. We build AI Emaily; you can see how the Outlook connection works at aiemaily.com/docs/connect-outlook, and compare plans at aiemaily.com/pricing.
Frequently asked
See it in AI Emaily
Keep reading
Sources
- Microsoft Learn: Exchange ActiveSync
- Microsoft Open Specifications: MS-ASHTTP, Exchange ActiveSync HTTP Protocol
- Microsoft Learn: Deprecation of Basic authentication in Exchange Online
- Apple Platform Deployment: Microsoft Exchange and Graph on Apple devices
- Microsoft Community Hub: Exchange Online ActiveSync device support update

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.