微软今天开始禁用 Exchange Online 中的 Exchange Web 服务（EWS），早于该 API 于2027年4月1日永久退役。EWS 随 Exchange Server 2007 推出，允许应用程序访问邮箱数据，包括电子邮件、日历和联系人。微软表示，该服务“已不再符合当今的安全、扩展性和可靠性要求”，并建议将集成迁移至 Microsoft Graph，尽管目前仍存在一些功能缺口。
Microsoft begins disabling Exchange Web Services (EWS) in Exchange Online today, ahead of the API's permanent retirement on April 1, 2027. Introduced with Exchange Server 2007, EWS allows applications to access mailbox data including email, calendars, and contacts. Microsoft says the service "no longer aligns with today's security, scale, or reliability requirements" and recommends moving integrations to Microsoft Graph, although some capability gaps remain.
从10月1日起，微软将开始把仍设置为 $null 的租户级 EwsEnabled 设置更改为 $false，从而阻止 EWS。需要暂时保持使用的管理员可以明确将该值设置为 $true，并将获批应用添加到 EwsAllowedAppIDs 列表中。不在该列表中的应用将被阻止。但这只能争取到2027年4月1日，届时微软将永久禁用 EWS。公司态度十分明确：“不会有任何例外。”
Beginning October 1, Microsoft will start changing tenant-level EwsEnabled settings left at $null to $false, blocking EWS. Administrators needing temporary continuity can explicitly set the value to $true and add approved applications to the EwsAllowedAppIDs list. Applications not on that list will be blocked. That buys time only until April 1, 2027, when Microsoft will disable EWS permanently. The company was unequivocal: "There will be no exceptions."
此次退役仅适用于 Exchange Online 中的 EWS。本地部署的 Exchange Server 中的 EWS 不受影响。微软于2018年停止为 Exchange Online 中的 EWS 添加新功能，并于2023年宣布将其退役。因此，管理员已有数年时间做准备，但要从一个深度嵌入的 API 中抽身迁移并非易事。Boomi 负责 API 管理的全球现场首席技术官 Markus Müller 表示，迁移面临的最大挑战之一，是找出对 EWS 的每一项使用。
The retirement applies only to EWS in Exchange Online. EWS in on-premises Exchange Server is unaffected. Microsoft stopped adding features to EWS in Exchange Online in 2018 and announced its retirement in 2023. Administrators have therefore had years to prepare, but moving away from a deeply embedded API is not necessarily straightforward. Markus Müller, global field CTO for API management at Boomi, said one of the biggest migration challenges was identifying every use of EWS.
“由于集成部署推进迅速且文档有限，许多组织并未完整盘点其对 EWS 的依赖，”他说。Müller 补充称，将 EWS 调用转换为 Microsoft Graph 请求的转换层可以充当临时桥梁，但这会引入另一个需要维护的组件，而且并不能消除迁移的必要。他主张，组织应在 API 的整个生命周期内持续监控相关依赖，而不是等到弃用通知发出后才发现它们。微软尚未说明，目前仍有多少组织或流程依赖 Exchange Online 中的 EWS。
"With rapid integration rollouts and limited documentation, many lack a complete inventory of their EWS dependencies," he said. Translation layers that convert EWS calls into Microsoft Graph requests may offer a temporary bridge, Müller added, but create another component to maintain and do not remove the need to migrate. He argued that organizations should monitor APIs as dependencies throughout their lifecycle rather than waiting for deprecation notices to expose them. Microsoft has not said how many organizations or processes still depend on EWS in Exchange Online.
任何被遗漏的集成，都会在分阶段拦截措施波及相关租户时暴露出来——最可能的表现是，用户通过支持工单报告原本稳定运行的工作流突然停止。®
Any overlooked integrations will begin revealing themselves as the phased blocking reaches their tenants – most likely through support tickets reporting that previously reliable workflows have suddenly stopped. ®