Live status of all services Incident · resolved

Admins are unable to access the Exchange admin center (EAC)

Exchange Online EX1500900

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.

  1. Oct 14, 2026, 15:11 CEST

    A post-incident report has been published.

  2. Oct 14, 2026, 15:11 CEST

    A post-incident report has been published.

  3. 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.

  4. 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.

  5. 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.

  6. 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.

  7. 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.

  8. 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.

  9. 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.

  10. 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.

  11. Oct 12, 2026, 11:37 CEST

    When attempting to access the Exchange admin center, affected admins may encounter an “Internal Server Error” message.

When Microsoft 365 goes down

The live overview shows the current state of every Microsoft 365 service, refreshed every minute from Microsoft Graph.

To see whether your own tenant is affected, check Service health in the Microsoft 365 admin center. Only a backup outside Microsoft protects against data loss, and only a tested break-glass account against locked-out admins. We set up both in fixed-scope sprints.

Source: Microsoft Graph, Service Communications API. This is the view of a Swiss Microsoft 365 tenant: services not licensed there are missing, and individual issues may affect your tenant differently. Microsoft names the region only in the issue text. The Switzerland view shows issues for Switzerland, for Europe in general and those without a region, but not issues that only name other countries such as Germany or the UK. This page is not provided by Microsoft.