Admins are unable to access the EAC.
- Status
- Post-incident report published
- Feature
- Reports of an Incident
- Region
- Not specified (all regions)
- Started
- Oct 12, 2026, 10:15 CEST
- Resolved
- Oct 12, 2026, 14:50 CEST
- Duration
- 4 h 35 min
Message
A post-incident report has been published.
Timeline
Every update Microsoft posted for this issue, newest first.
- Oct 14, 2026, 15:11 CEST
A post-incident report has been published.
- Oct 14, 2026, 15:11 CEST
A post-incident report has been published.
- Oct 12, 2026, 15:28 CEST
We've completed the rollback of the identified Exchange admin center (EAC) change. Service telemetry shows that errors have returned to expected levels, and user reports have confirmed that EAC access has been restored. Admins who continue to experience impact should close their existing EAC browser session, open a new session, and retry accessing the EAC. We’ll continue to monitor service health to ensure sustained service stability.
- Oct 12, 2026, 15:04 CEST
We’ve completed the rollback and are continuing to monitor service health, with telemetry showing errors trending downward from their earlier peak. Admins who continue to experience impact should close their existing Exchange admin center (EAC) browser session, open a new session, and retry accessing the EAC. We’ll continue monitoring to validate recovery.
This quick update is designed to give the latest information on this issue. - Oct 12, 2026, 14:50 CEST
We’re continuing to roll back the identified Exchange admin center (EAC) change. Initial telemetry shows errors trending downward from their earlier peak, and we’re monitoring service health to determine whether the rollback restores access for affected admins.
This quick update is designed to give the latest information on this issue. - Oct 12, 2026, 14:23 CEST
Our testing has identified a recent Exchange admin center (EAC) configuration change as a potential contributor to the access failures and associated HTTP 302 redirects. We’re rolling back the change, which we expect to complete within approximately two hours. Once complete, we’ll monitor the environment to determine whether this resolves the impact.
- Oct 12, 2026, 14:01 CEST
We’re continuing to test the rollback of the recent Exchange admin center (EAC) change while monitoring the results to determine if this resolves the impact. In parallel, we’re continuing our analysis of the unexpected HTTP 302 redirects to help determine the source of the issue.
This quick update is designed to give the latest information on this issue. - Oct 12, 2026, 13:21 CEST
We’re continuing to investigate the unexpected HTTP 302 redirects and are testing a rollback of a recent Exchange admin center (EAC) change to determine if this resolves the impact. We’re also comparing results across affected environments to determine our next steps.
- Oct 12, 2026, 12:53 CEST
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.
This quick update is designed to give the latest information on this issue. - Oct 12, 2026, 12:19 CEST
We’re reviewing service logs and analyzing available diagnostic data to identify the source of the issue and determine next steps.
- Oct 12, 2026, 11:37 CEST
When attempting to access the Exchange admin center, affected admins may encounter an “Internal Server Error” message.