微软今天关闭了 Exchange 管理中心（Exchange Admin Center，简称 EAC）。由于代码更新导致问题，管理员在尝试访问该服务时遇到了“内部服务器错误”（Internal Server Error）的提示。微软首次承认问题存在的时间是 10 月 12 日 09:37 UTC（世界协调时），并指出：“在尝试访问 Exchange 管理中心时，受影响的管理员可能会看到‘内部服务器错误’的提示。”
Microsoft took down the Exchange Admin Center (EAC) today after a code change left administrators facing an "Internal Server Error" when trying to access the service. Microsoft first admitted that something was amiss at 0937 UTC on October 12, noting, "When attempting to access the Exchange admin center, affected admins may encounter an 'Internal Server Error' message."
任何尝试访问 EAC 的管理员都可能受到影响。直到一个多小时后，微软才表示：“我们发现了在访问 EAC 时出现的意外 302 重定向错误，并正在分析诊断日志以确定故障的根源。在调查期间，管理员仍然无法访问 EAC，目前也没有任何解决方法。”对微软的欧洲用户来说，这确实是一个“糟糕的早晨”……根据微软的解释，EAC 是一个用于管理 Exchange Online 的现代化、基于 Web 的管理工具。
Any administrator attempting to access the EAC could be affected. It was more than an hour before the company stated: "We've identified unexpected 302 redirect errors during affected Exchange admin center (EAC) access attempts and are analyzing diagnostic logs to isolate the source of the access failures. "While we continue our investigation, admins remain unable to access the EAC, with no workaround currently available." So, a fun morning for Microsoft's European users. According to Microsoft, the EAC is "a modern, web-based management console for managing Exchange Online."
无论是管理邮箱还是管理用户组，都需要通过 EAC 来完成。微软还称：“Exchange Online 中的 EAC 设计与整个 Microsoft 365 管理体验保持一致。”遗憾的是，这种“一致性”似乎也包括了那些因疏忽或未经充分测试而导致的系统故障。在承认问题出现两小时后，微软表示正在“继续测试撤销最近进行的 EAC 配置更改，并监控测试结果，以确定这是否能够解决故障问题。”
Want to manage mailboxes? EAC is where you go. Group management? Again, EAC. Microsoft explained: "The design of the EAC in Exchange Online aligns with the overall Microsoft 365 admin experience." Sadly, that alignment appears to extend to service wobbles caused by changes rolled out without due care and attention. Two hours after admitting things had gone awry, Microsoft said it was "continuing to test the rollback of the recent Exchange admin center (EAC) change while monitoring the results to determine if this resolves the impact."
对于管理员们来说，这其实是一个再熟悉不过的“老故事”了……幸运的是，撤销该更改确实解决了问题。微软在最后的更新中明确表示：“最近对 EAC 的配置更改导致了某些请求路径中出现异常的 HTTP 响应，从而使得管理员无法正常访问 EAC。”
At this point, administrators were nodding sagely at an all-too familiar story. Of course rolling back the change did the trick. Microsoft stated as much in its final update: "A recent EAC configuration change resulted in unexpected HTTP responses within the affected request path, preventing admins from successfully accessing the EAC.
“恢复已识别的错误配置后，系统的服务功能恢复正常。”微软还向客户保证，他们正在审查这一变更，以确保不会再犯同样的错误，并会加强系统的监控与数据分析能力，以便“更好地检测和预警类似的服务故障”。然而，这类问题其实并不新鲜：去年9月，微软的一次配置更改导致部分用户无法访问 SharePoint Online 的网站和页面；今年4月，又有一次考虑不周的变更导致 Outlook for iOS 应用程序无法正常使用；2025年，微软的 365 服务也曾因配置问题而出现故障。
"Reverting the identified change restored expected service functionality." Microsoft also assured customers it was reviewing the change to ensure it didn't make the same mistake again, as well as its monitoring and telemetry, to "improve detection and alerting for similar service behavior." The problem is that this is hardly a new phenomenon. In September, Microsoft made a configuration change that left some users unable to access SharePoint Online sites and pages. In April, another ill-thought-through change took down Outlook for iOS. And, in 2025, Microsoft 365 tumbled from the cloud because of yet another configuration change.
看起来，微软在测试变更时几乎只是简单地询问 AI 工具“这样看起来没问题吧？”然后就直接发布了新版本。最近这次故障已在工作日结束前得到解决，初步的事后报告将在两个工作日内提交，最终报告则将于下周发布。希望其中某份报告能提出这样的建议：“这个问题一直在重复出现，或许我们在正式部署新功能之前应该进行更多的测试吧？”
It's almost as if testing changes consists of little more than asking Copilot, "does this look alright to you?" and then hitting the go button. The latest outage was resolved before the end of the working day, and a preliminary Post-Incident Report is due within two business days, with a final report due next week. Hopefully one or the other will contain words along the lines of "Hey, this keeps happening, maybe we should do some more testing before deploying to production?" ®