Exchange Web Services Is Being Retired: What It Means for Your CRM Email Integration
If your CRM synchronises email, calendar entries or contacts with Microsoft 365, it may rely on Exchange Web Services (EWS), an older Microsoft interface that is being switched off in Exchange Online. Microsoft's documentation says EWS starts to be disabled globally from October 2026 and is fully disabled in April 2027. Vivato builds bespoke and semi-bespoke CRM systems for UK organisations, and this is a good moment for any CRM owner to check whether an integration quietly depends on EWS before it stops working.
What is Exchange Web Services, and why is Microsoft retiring it?
Exchange Web Services is an interface that lets applications read and write mailbox data in Exchange, such as emails, calendar items and contacts. Microsoft announced its deprecation in July 2018 and has since steered developers towards Microsoft Graph, its modern API. According to Microsoft, a January 2024 security incident involving EWS raised the urgency of the move.
Microsoft's timeline, as published on Microsoft Learn, is:
| Date | Milestone |
|---|---|
| July 2018 | EWS deprecation announced |
| October 2026 | EWS starts to be disabled globally for all organisations |
| April 2027 | EWS is fully disabled |
Note that the retirement concerns Exchange Online, the cloud service. It is not an announcement about Outlook or Microsoft 365 as a whole.
Why does this matter for a CRM?
Many CRM features that feel like "email integration" are built on mailbox access behind the scenes. Typical examples include:
- email tracking and saving emails against customer records
- calendar and appointment synchronisation
- contact synchronisation
- shared mailbox processing, such as turning enquiries into CRM records
- Outlook activity logging
If one of these uses EWS and is not updated, it can fail. To users, that tends to look like "the CRM is broken" rather than "an interface was retired", so support tickets are often the first sign.
Microsoft states that third-party applications using EWS must migrate. A vendor-authored article from a Dynamics partner, enCloud9, warns specifically that Dynamics 365 Customer Engagement (on-premises) and Dynamics CRM 9.x environments connecting to Exchange Online may see email, appointment and mailbox-processing failures. Treat that as one vendor's view and confirm against Microsoft's own documentation for your version.
Which CRM setups are most likely to be affected?
Risk is not evenly spread. Based on how these integrations are typically built, the higher-risk situations are:
- Older on-premises or self-hosted CRM systems connecting to Exchange Online.
- Bespoke or custom-built integrations written years ago against EWS and never revisited.
- Small add-ins and connectors from third parties that are no longer actively maintained.
- Scripts and automations that poll a shared mailbox, often created by one person who has since left.
Modern, actively maintained SaaS CRMs generally manage their own migration to Microsoft Graph, but you should still ask the supplier to confirm. Never assume.
How can you check whether your CRM depends on EWS?
Start with evidence rather than guesswork. Microsoft points administrators to the EWS usage reports in the Microsoft 365 admin centre and to its EWS to Graph mapping guidance. A practical sequence looks like this:
- Ask your Microsoft 365 administrator for the EWS usage report and list every application calling EWS.
- Match each caller to a business system. Identify which belong to the CRM, and which to other tools.
- Ask each supplier in writing whether their integration has moved to Microsoft Graph, and when.
- Inventory your custom code. Search for EWS usage in any bespoke integration, scheduled jobs or scripts.
- Test in a non-production environment, where possible, with EWS disabled for a pilot user or group. Microsoft says administrators can disable EWS at organisation and user level.
Fix, rebuild or replace: how do you decide?
Once you know what depends on EWS, the decision for each integration is usually one of three routes.
| Option | Best when | Trade-off |
|---|---|---|
| Update the existing integration to Microsoft Graph | The integration is bespoke, well understood and otherwise fit for purpose | Needs development effort, and some EWS capabilities may not have exact Graph equivalents |
| Replace the connector | A maintained alternative exists and covers your needs | Possible licence cost and a different feature set |
| Rethink the CRM itself | The CRM is old, hard to maintain and the integration is one of several problems | Largest effort, but may address wider issues at once |
Microsoft notes that some capabilities will not be added to Graph, so do not assume every function maps one-to-one. This is where an honest review helps. A small update is often the right answer, and you should be wary of any supplier who treats a single integration issue as a reason to rebuild everything.
If several integrations are ageing at once, it may be worth looking at the bigger picture. Our guides on CRM integration and consolidation and API and third-party integrations cover how to reduce brittle point-to-point connections.
Is this a one-off, or a pattern?
It is part of a wider pattern. Vendors retire older interfaces and products, and CRM owners inherit the work. We have covered related examples, such as the Zendesk Sell retirement and 2027 migration planning and a 2026 audit of HubSpot legacy CRM cards. The lesson is the same each time: keep an inventory of what your CRM connects to, who owns each connection and who is responsible when a vendor changes the rules.
Frequently asked questions
Does the EWS retirement affect Outlook itself?
Microsoft says it is removing EWS dependencies from its own products. The change is mainly a risk for third-party and custom applications that call EWS directly. Check your own estate rather than relying on a general answer.
What is Microsoft Graph?
Microsoft Graph is Microsoft's current API for working with Microsoft 365 data, including mail, calendars and contacts. It is the main route Microsoft recommends for replacing EWS-based integrations.
Do I need a bespoke CRM to avoid this kind of problem?
No. Any CRM, bespoke or off-the-shelf, depends on external services that can change. What matters is having an owner, an inventory and a supplier who communicates changes early. Vivato builds bespoke and semi-bespoke CRM systems, but we would be the first to say that many organisations are well served by a maintained off-the-shelf product.
Final Words
The EWS retirement is a practical reminder that CRM email and calendar features depend on interfaces you do not control. Check your usage reports, ask your suppliers for written confirmation and test before disablement reaches your tenant. If you find an integration you are unsure about, Vivato is happy to talk through the options, from a targeted fix to a broader rethink. You are welcome to get in touch for a no-pressure conversation.
