Microsoft Enables Legacy Exchange Web Services API to Rescue Stalled Online Apps

Microsoft announced that administrators of Exchange Online can reactivate the deprecated Exchange Web Services (EWS) API, a move intended to restore functionality to third‑party applications that rely on the interface after it was retired earlier this year.

The decision follows a wave of reports from IT teams that critical business tools—ranging from calendar synchronizers to ticketing systems—suddenly stopped communicating with Exchange Online when Microsoft phased out the EWS endpoint. While the company has encouraged developers to migrate to newer Graph‑based APIs, many legacy integrations have not yet been updated, leaving organizations scrambling for a temporary fix.

In a technical bulletin, Microsoft detailed a step‑by‑step process for re‑enabling the EWS service through the Exchange admin center or via PowerShell commands. The guidance emphasizes that the reinstated API is meant as a short‑term solution, urging customers to plan migrations to supported APIs to avoid future disruptions.

Industry analysts note that the situation highlights the challenges of balancing security and modernization with the operational realities of large enterprises. Retiring an API without a clear, universally‑adopted replacement can create gaps for customers who depend on legacy code, especially in sectors with strict compliance requirements where rapid software changes are difficult.

For organizations already affected, the immediate benefit is a restored connection for essential workflows, such as automated meeting scheduling and ticket generation. However, Microsoft cautions that the revived endpoint may not receive the same level of performance tuning or security updates as its newer counterparts, and it could be fully discontinued in future service cycles.

Looking ahead, the tech giant says it will continue to provide migration resources, including code samples and documentation, to help developers transition to Microsoft Graph. The company also plans to monitor usage of the re‑enabled EWS API to gauge how many customers remain dependent on the older protocol.

In the meantime, IT leaders are advised to conduct inventory checks of all applications interfacing with Exchange Online, prioritize updates for those still using EWS, and establish timelines for moving to supported APIs. The temporary reinstatement offers a breathing‑room solution, but the broader industry trend points toward a unified, modern API ecosystem for Microsoft 365 services.