Exchange Web Services enters the final stretch before Microsoft pulls access

What happened

Microsoft has begun retiring Exchange Web Services (EWS), the legacy API that many enterprise applications have long relied on to connect with Exchange Online, with the shutdown now entering its final phase. According to The Register, the API is starting to disappear from tenants as of today, with Microsoft confirming there will be no exceptions or further extensions once the cut-off arrives in April.

EWS has served for years as a core integration point for mail, calendar and contacts functionality in third-party tools, line-of-business applications and custom-built connectors. Its phased withdrawal pushes organisations toward Microsoft Graph, the vendor's modern API framework, as the only supported path for programmatic access to Exchange data going forward.

Why it matters

This is fundamentally a technology-modernisation story: a widely embedded legacy interface is being switched off on a fixed timeline, forcing a migration that many IT teams will have deprioritised until forced to act. Applications and automations built against EWS — from CRM-to-calendar sync tools to custom reporting and compliance systems — risk breaking silently as access is withdrawn tenant by tenant.

For digital transformation leaders, the episode is a reminder that platform dependencies accumulate quietly and rarely get budgeted attention until a vendor sets a hard deadline. Moving to Graph is not simply a technical swap; it typically requires re-architecting authentication, permissions scopes and data-access patterns, work that can stall if discovery of affected integrations starts too late.

By the numbers

• Today is when EWS access begins being withdrawn from tenants, according to Microsoft's published timeline.
• April is the final cut-off date after which Microsoft has said no exceptions will be granted.

The Renascence take

Deprecations like this are usually framed as IT housekeeping, but they are really a test of how well an organisation understands its own operational dependencies — and how that gap ultimately surfaces as a customer or employee experience problem.

Most enterprises will discover their EWS dependencies the hard way: a scheduling tool stops syncing, a support workflow silently drops calendar invites, or a compliance export fails, and only then does anyone trace it back to an API retirement flagged months earlier. The real lesson isn't "migrate to Graph" — it's that legacy integrations are rarely inventoried with the same rigour as customer-facing systems, even though they quietly underpin service reliability. Operators that treat vendor deprecation notices as early-warning signals, rather than deadlines to react to, are the ones who avoid turning a backend API change into a front-line service failure.