Microsoft Rolls Back Exchange Admin Center Configuration Change After Outage
A configuration change temporarily blocked administrator access to the Exchange Admin Center, prompting Microsoft to reverse the update and review its monitoring and change-management processes.
Key Takeaways:
- A configuration change caused an Exchange Admin Center outage, preventing administrators from accessing the management console.
- Microsoft restored service by rolling back the problematic change.
- The incident has renewed attention on change-management and validation processes for cloud services.
Microsoft experienced an outage affecting the Exchange Admin Center (EAC) on October 12 after a configuration change caused administrators to receive “Internal Server Error” messages when attempting to access the web-based management console. This issue prevented admins from managing Exchange Online resources such as mailboxes and groups, with no workaround available during the disruption.
According to Microsoft, the outage began when a recent configuration change introduced unexpected HTTP responses and 302 redirect errors within the EAC request path. Administrators were unable to sign in to the service and perform routine management tasks. Microsoft acknowledged this issue and began analyzing diagnostic logs to identify the cause.
The Exchange Admin Center is the primary management interface for Exchange Online, and affected organizations temporarily lost access to key administrative functions. This disruption added to a growing list of Microsoft service incidents linked to configuration changes, which raised concerns about change management and testing processes across Microsoft 365 services.
Microsoft identifies and reverses the problematic update
Microsoft identified the problematic configuration change and rolled it back. The company confirmed that reverting the change restored normal service functionality. Microsoft also said it is reviewing both the change itself and its monitoring and telemetry systems to improve detection and alerting for similar issues in the future. A preliminary post-incident report is expected within two business days, followed by a final report the following week.
Rapid deployment and configuration updates allow Microsoft to deliver new features and improvements more quickly, but they can also increase the risk of service disruptions when changes are not sufficiently validated before reaching production. This incident highlights the ongoing challenge of balancing deployment speed with reliability, particularly for cloud services that organizations depend on for daily administration and operations.
Rabia has a master's degree in Software Engineering and she has years of experience writing professionally about Microsoft products and other technologies. Rabia has also written for OnMSFT.com as well as Windows Report. She is always up to date on t...
