Mac users who rely on Apple Mail for a Microsoft 365 work inbox may encounter an unwelcome bit of enterprise-tech friction: Microsoft has begun disabling Exchange Web Services, or EWS, by default in Exchange Online. Apple’s Mail and Calendar apps on macOS still depend on that older connection method for these accounts, so the change can interrupt syncing for affected organizations.

The important word is can. This is described as a phased rollout rather than a universal switch flipped at the same moment for every organization. Some users may lose access before others, while businesses that previously chose to keep EWS enabled are not affected for the moment. That uneven timing makes this less like a clean service-wide outage and more like a compatibility deadline gradually arriving on different desks.

For people who use a Mac as their primary work machine, the impact could go beyond a stale inbox. Apple says its Mail, Calendar, Contacts, Notes and Reminders apps on Mac are being moved to Microsoft Graph support in a future macOS 27 update. Until that arrives, however, an organization’s EWS setting can determine whether those familiar built-in apps remain a workable way to access a Microsoft 365 account.

What is changing, and who is affected?

Exchange Online is Microsoft’s cloud-hosted email service used with Microsoft 365. It is the scope of this change. Organizations that operate their own Exchange servers are not included, so this is not a blanket shutdown of every Exchange deployment in existence.

EWS is an older programming interface that lets apps communicate with Exchange data. In everyday terms, it has been one of the routes through which a desktop client can request and update mailbox-related information. Microsoft stopped adding new EWS features in 2018 and said in 2023 that it would begin disabling the protocol in Exchange Online from October 2026. The current rollout is the practical start of that transition for organizations that have not opted to retain EWS.

The distinction between a protocol and an app matters here. Apple Mail has not suddenly ceased to be an email client, and Microsoft 365 accounts have not inherently disappeared. The problem is the compatibility layer between the Mac apps and Microsoft’s hosted Exchange service. If that layer is unavailable, the apps that still use it may no longer be able to keep the relevant work data synchronized.

Apple’s Mac-side suite is broader than just Mail in this case. The planned migration mentions Mail, Calendar, Contacts, Notes and Reminders. That means an affected employee should not assume a successful-looking inbox is the entire test. Calendar changes, contact updates, reminders and notes connected to the work account may be relevant too.

Why iPhone and iPad users are not in the same position

The change does not affect iPhone and iPad in the same way. Those devices use Exchange ActiveSync rather than EWS for this purpose. Exchange ActiveSync is a separate synchronization protocol, so the EWS disablement in Exchange Online is not the mechanism their access relies on.

That creates a potentially confusing split for people who work across Apple devices. A Microsoft 365 account may continue functioning on an iPhone or iPad while its associated services no longer sync correctly in Apple’s apps on a Mac. It is therefore risky to treat successful mobile access as proof that the desktop setup is healthy.

The distinction also narrows the troubleshooting question. If a Mac user reports a syncing issue around this change while their iPhone remains current, the difference in connection technology is a meaningful clue. It does not establish every cause of every mailbox problem, but it explains why the symptoms could be device-specific.

Apple’s planned Graph move has not arrived

The long-term replacement named by Apple is Microsoft Graph, a newer Microsoft API. An API, or application programming interface, is the set of rules and tools software uses to exchange information with a service. In this situation, Graph is intended to become the newer connection path for Apple’s macOS productivity apps and Exchange Online data.

Apple says it is working with Microsoft on the migration for a future macOS 27 update. Yet there is no released Graph-support update cited here. macOS 27.1 beta releases were skipped, and the available macOS 27.2 beta release notes do not mention Graph support. That leaves a real gap between the older method being phased out and the stated future plan for the replacement.

It would be premature to infer a release date, specific implementation details, or an exact cutoff for Apple’s support from that absence. The concrete point is simpler: organizations should not plan on a macOS 27 Graph migration that has not yet been delivered. A future software update is not a present workaround.

This sort of transition illustrates why workplace software compatibility is often controlled by several parties at once. Microsoft determines how its cloud service accepts connections. Apple determines when its apps adopt a newer method. IT teams determine the policies and approved clients available to employees. Users see the result as either a functioning calendar or an alarming request to add an account again.

What organizations can do now

For organizations affected by the phased EWS disablement, there are two routes identified in the available information:

  • Keep EWS running for now. IT administrators can restore or preserve access during the transition period if their organization needs Apple’s Mac apps to continue using EWS.
  • Use a Graph-compatible client. Microsoft Outlook is identified as an example of a client compatible with Microsoft Graph.

The first option is a temporary compatibility measure, not a permanent endpoint. Microsoft plans to shut down EWS in Exchange Online permanently on April 1, 2027, with no extensions currently planned. Teams that choose to retain EWS in the near term still need a plan for the post-EWS environment.

The second option shifts the immediate burden from the service setting to the user experience. Moving Mac users to Outlook can retain access through a Graph-compatible app, but it may change established habits for people accustomed to Apple Mail and its integration with the rest of macOS. Whether that is acceptable is an organizational decision involving support, policy and user workflow—not a universal declaration that one client is better for every person.

Practical checks for Mac users and IT teams

Individual employees should avoid changing organizational mail settings on their own. The relevant control is an administrative choice, and repeated account removal or re-adding may not solve an EWS policy change. Instead, report the problem through the company’s support process and make the report specific.

A useful report can state that the account is Microsoft 365 or Exchange Online, identify the Mac apps affected, and note whether the same account still updates on iPhone or iPad. Mentioning whether mail, calendar, contacts, notes or reminders are out of date gives IT staff a clearer starting point than simply saying that “Exchange is broken.”

Administrators, meanwhile, have a limited period in which EWS can still be kept active if necessary. The practical planning questions are straightforward: which Mac users depend on Apple’s built-in apps, whether EWS has already been retained at the organization, whether Outlook is an approved replacement, and how staff will be told about any change. Testing should look at the entire group of affected data types rather than email alone.

There is also a communications lesson in the mobile exception. Users may reasonably ask why the same work account works on their phone but not on their Mac. Explaining that the two platforms use different synchronization technology is more useful than characterizing the issue as a general Microsoft 365 failure. For related Apple service context, see this look at a separate Apple services availability issue; the current matter is specifically about Exchange Online’s EWS transition and macOS client compatibility.

A deadline with an uneven short-term impact

The immediate experience will vary because the rollout is phased and because some organizations have deliberately kept EWS running. That variability should not be mistaken for uncertainty about the overall direction. EWS is being retired from Exchange Online, its permanent shutdown is scheduled for April 1, 2027, and Apple’s Graph-based macOS support remains a future update rather than a presently documented fix.

For Mac users, the sensible next step is awareness rather than panic: a suddenly non-syncing work account may be tied to this change, even if a phone continues to work. For IT teams, the job is more urgent and concrete: choose whether to maintain EWS temporarily, deploy a Graph-compatible client, or prepare for Apple’s eventual macOS migration—while remembering that the old protocol’s final deadline is already on the calendar.