{
  "id": 14038428,
  "title": "Microsoft blames a configuration change for Exchange Admin Center tumble",
  "url": "https://urgent.news/2026/10/12/microsoft-blames-a-configuration-change-for-exchange-admin-center",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-10-12T17:55:53.000Z",
  "source": {
    "name": "The Register Science",
    "slug": "the-register-science",
    "url": "https://www.theregister.com/saas/2026/10/12/microsoft-blames-a-configuration-change-for-exchange-admin-center-tumble/5302698"
  },
  "original_language": "en",
  "account": "Microsoft's Exchange Admin Center (EAC) went offline today after a recent code modification caused an Internal Server Error for administrators trying to access the service. The issue became apparent at 0937 UTC on October 12, with Microsoft initially notifying users that any attempts to access the EAC could result in an Internal Server Error. The company explained that the problem stemmed from unexpected 302 redirect errors observed during EAC access attempts, and they were currently analyzing diagnostic logs to pinpoint the cause of the failures.\n\nMicrosoft described the EAC as a modern, web-based management console for managing Exchange Online, used for tasks such as managing mailboxes and group management. An alignment issue was identified, where the design of the EAC mirrored the overall Microsoft 365 admin experience, but this alignment also seemed to extend to service disruptions caused by changes rolled out without sufficient care. Two hours after initially admitting the problem, Microsoft initiated a rollback of the recent EAC change while monitoring results to determine if it resolved the issue. This action proved effective in restoring normal service functionality for administrators.\n\nThe company assured customers that it was reviewing the change to prevent future occurrences and improving its monitoring and telemetry to enhance detection and alerting for similar service behavior. However, this experience is not unprecedented; similar issues have occurred before, including a configuration change in September that affected some users' ability to access SharePoint Online sites and pages, and another misstep in April that brought Outlook for iOS to a halt. In 2025, Microsoft 365 has suffered multiple outages due to configuration changes, leading to speculation about the effectiveness of Microsoft's testing processes, which seem to involve minimal scrutiny before deployment to production.",
  "summary": "Rollback fixed things, but stop us if you've heard this before",
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}