Exchange Sync BridgeBeyond Time Matters: Every Kind of Software the EWS Shutdown Breaks
Microsoft began disabling Exchange Web Services on October 1, 2026, and the rollout is now moving tenant by tenant. Time Matters firms are the loudest casualty in legal IT — but EWS is the plumbing behind far more than practice management sync. If it talks to a mailbox and it isn't made by Microsoft, it's worth checking.
EWS Is The Plumbing, Not The Fixture
Exchange Web Services is the API that third-party software has used for well over a decade to read and write mailboxes in Exchange Online — calendars, contacts, tasks, email. Microsoft's own apps never depended on it: Outlook, Teams, and the mobile apps use newer protocols. That's why the October 1 disablement is so easy to sleepwalk into. Email keeps flowing, Outlook opens fine, and the only things that stop are the integrations you bought from someone else.
Per Microsoft's EWS retirement FAQ, tenants that haven't opted to keep EWS are being disabled on a phased schedule that started October 1, 2026, with a final, permanent shutdown on April 1, 2027. You don't get to see where your tenant sits in the queue — and neither does the software that depends on EWS.
If It Talks To A Mailbox, Check It
Practice management sync.
The category most legal IT teams already know about: Time Matters Exchange Synchronization on versions before 2026 connects to Exchange Online over EWS. The vendor shipped a Graph-based fix in Time Matters 2026 — but upgrades require an active AMP membership, and firms on older versions or off AMP need another path (your options without AMP). Other practice management and matter management products with Exchange sync features belong on the same list.
Voicemail sync.
Cisco Unity Connection's unified messaging features use EWS to move voicemails and notifications into Exchange mailboxes — Cisco's own Field Notice FN74365 spells out the impact. When EWS goes, voicemail stops appearing in Outlook and message-waiting indicators fall out of sync.
On-prem CRM server-side sync.
Dynamics CRM on-premises uses server-side synchronization over EWS to track email and appointments against Exchange Online. Hybrid and older deployments are the ones at risk — the sync keeps running silently until it doesn't.
Document management integrations.
DMS tools that file email into matters, watch intake mailboxes, or push notifications into Outlook commonly do it over EWS. The DMS itself keeps working; the mail flow around it stops.
Room booking and resource panels.
Conference-room displays, desk booking panels, and visitor systems that read Exchange calendars directly are classic EWS consumers. The symptom: the panel shows a free room while the calendar says otherwise.
Archiving and journaling tools.
Anything that pulls mail for retention, e-discovery staging, or compliance journaling over EWS stops collecting — and a silent gap in an archive is a compliance problem, not just an IT one.
Shared-mailbox monitors and workflow automation.
Ticketing bridges, intake parsers, and workflow tools that watch a shared mailbox for new items (support@, intake@, billing@) overwhelmingly use EWS polling. When it stops, work simply stops arriving — with no bounce, no error, and no alert.
Custom and bespoke applications.
The hardest to inventory: internal tools, vendor-written one-offs, EWS Managed API utilities, and PowerShell scripts that impersonate mailboxes. If a contractor built it years ago and nobody owns it now, assume EWS until proven otherwise.
Nothing Errors. It Just Stops.
Every category above fails the same way: silently. The application keeps running, the interface looks normal, and the data it was supposed to move quietly falls behind. Voicemails stop reaching inboxes. CRM records stop capturing email. The archive develops a hole nobody can see from the dashboard. In a law firm, the first visible symptom is usually a stale calendar or a missed deadline — discovered by a person, not a monitoring system.
And because the disablement is phased, "it still works" tells you nothing. Your tenant's turn in the queue is not visible to you, and a tool that synced this morning is not evidence it will sync next week.
The Audit Nobody Budgeted For
The fix starts with an inventory, and it's faster than it sounds. Our 5-minute EWS checklist walks through the tells: the configuration screens that name EWS or an Exchange Web Services URL, and the Entra ID app registrations whose granted permissions give EWS applications away. The EWS Retirement Guide covers the same ground in more depth.
For anything you're unsure about, ask the vendor in writing, specific to the version you run: "What is your plan for Exchange Online connectivity after EWS is disabled?" Vendors with a real fix will name it — the way PCLaw | Time Matters shipped Graph-based sync in Time Matters 2026, per the official release notes. "We're looking into it" is also an answer — just not a comforting one this far into the rollout.
Three Paths Per Application
Take the vendor fix, where one exists.
If the vendor has shipped Graph-based connectivity and you're eligible for it, that's the cleanest path. Just get cost and timeline in writing — an upgrade project under deadline pressure is its own risk, and this quarter every affected firm is competing for the same consultants.
Buy time with Microsoft's allowlist.
A tenant admin can explicitly re-enable EWS and allowlist specific applications, extending access until the final April 1, 2027 cutoff — here's how the configuration works. It's free, it's legitimate, and it buys real months. It is not a strategy: on April 1 it ends regardless. Use it as breathing room, not as the plan.
Bridge the application to Microsoft Graph.
For software with no vendor fix coming — or a fix gated behind an upgrade you don't want — Exchange Sync Bridge translates the application's existing EWS requests to Microsoft Graph on a hosted service. The software keeps working exactly as it does today; no upgrade, no retraining, setup typically in minutes. Pricing is $40 per sync-enabled user per month, no setup fees, no minimum term. Your data is never stored, and sign-in runs through Microsoft — we never see a password (security details).
Not sure what's using EWS in your environment?
Send us your software list and we'll tell you which items are affected — and what the fix looks like for each.
Find Out If You're Impacted