Microsoft EWS Shutdown: Timeline, Gaps, and How To Prepare

July 8, 2026
4 minute read
illustrated gravestone with the Microsoft Exchange logo and text "Exchange Web Services April 1 2027" illustrating the EWS shutdown

Microsoft EWS Shutdown: What’s Happening

The countdown is on. Microsoft is fully shutting down Exchange Web Services (EWS) in Exchange Online by April 1, 2027 and any workflow still relying on EWS will break. EWS has been the primary way that third-party tools use to read, write, and manage mailboxes, including archive mailboxes and legally held content.

Microsoft first announced plans to retire EWS in 2018. When the Midnight Blizzard security incident exploited EWS, they accelerated the timeline. Microsoft is now removing EWS dependencies from its own apps (Outlook, Office, Teams, Dynamics 365) and forcing third parties to do the same.

Microsoft is positioning Microsoft Graph as the replacement. While Graph includes a lot of the same capabilities as EWS, there are some gaps.

Key Takeaways

  • Microsoft is shutting down Exchange Web Services (EWS) by April 1, 2027
  • Microsoft is encouraging users to move to Microsoft Graph as a replacement
  • Microsoft Graph lacks some critical features
  • Bluesource built tools to cover the gaps

Microsoft EWS Deprecation Timeline

  1. July 2018
    EWS deprecation first announced.
  2. September 2023
    Hard disablement date set for October 2026.
  3. January 2024
    Midnight Blizzard breach accelerates the cloud security effort.
  4. May 2026
    Graph Mailbox Import/Export APIs reach General Availability.
  5. October 1, 2026
    EWS begins global disablement for non-Microsoft apps unless explicitly allow-listed.
  6. Oct 2026 - Apr 2027
    Grace period: Allow-listed AppIDs can continue temporarily using EWS.
  7. April 1, 2027
    EWS fully and permanently disabled worldwide with no exceptions.

What’s the Impact?

The core problem is that Microsoft Graph doesn’t support critical EWS capabilities. Microsoft is working on updates to close the gaps, but concerns around archive mailboxes and eDiscovery remain.

Public Folders & Microsoft 365 Groups

Not yet supported in general availability. Microsoft has acknowledged the gap as part of their planned fixes, but nothing is currently available.

Archive Mailbox Access

The new Import/Export API supports archive mailboxes, including handling redirects when auto-expanding archives distribute content across auxiliary mailboxes. This became generally available in May 2026; Bluesource has already updated our tools to support this new API.

Legal Hold + eDiscovery-Preserved Content

This remains the biggest gap between EWS and Graph functionality. The Import/Export API does not currently access mailboxes under legal hold or export litigation-hold-preserved content. For regulated industries, this is a major concern, and Microsoft has not committed to closing it before October 2026. The Import/Export API cannot access mailboxes under legal hold or export litigation‑hold‑preserved content — meaning regulated organizations currently have no Graph‑based path to retrieve preserved data.

Who is affected?

The gaps between EWS and Microsoft Graph functionality affect email archiving vendors, backup and disaster recovery solutions, eDiscovery platforms, data migration tools, any custom EWS integration, and compliance workflows that depend on archive access.

Covering the Gaps with Bluesource

Bluesource is prepared to guide customers through the EWS shutdown and transition. We have the gaps covered. We are one of the few vendors with a fully operational Graph‑based alternative today — not a roadmap, not a dependency on third‑party SDKs, but production‑ready tooling.

This positions Bluesource as ahead of the market.

  • Before Microsoft even declared general availability, we built a Graph client using the new Import/Export API. It has been tested and is ready for production.
  • Our Graph client handles archive mailboxes, including the redirect logic Microsoft requires for auto-expanding archives
  • We develop our own tooling in-house, so we control the timeline. No waiting on a third-party SDK to catch up.
  • We’re actively tracking Microsoft’s roadmap for public folders, Groups support, and legal hold parity, and keeping up to date with new Graph features.

The Bigger Message: What’s Next?

Existing customers: We stay on top of platform changes proactively. Our in-house development means your workflows are not disrupted while others scramble to adapt.

Prospective customers: The EWS shutdown is a real risk to email archiving and compliance infrastructure if your current vendor relies on EWS without a Graph-based alternative. We want you to be aware of this before it becomes urgent. Next steps:

  • Investigate/audit EWS usage
  • Identify allow-list apps
  • Outline a roadmap/migration plan

Bluesource is ready to assess your EWS exposure, validate your vendor’s readiness, and build a transition plan before the October 2026 cutoff.

Prepare for the end of EWS

Connect with Bluesource

Complimentary Gartner® Insights

Microsoft 365 E7: Balance the Opportunity, Negotiation Leverage and Pitfalls