# Microsoft Outlook Goes Down Nationwide \[UPDATE\]

DevFeed: [Microsoft Outlook Goes Down Nationwide \[UPDATE\]](<https://devfeed.tech/articles/microsoft-outlook-goes-down-nationwide-update-131007.md>)

Original publisher: [Read original article](<https://tech.slashdot.org/story/26/11/12/1959220/microsoft-outlook-goes-down-nationwide-update>)

Author: BeauHD

Published: 2026-11-12T20:00:00Z

Content type: news

Language: en

Sources: [Slashdot](<https://devfeed.tech/sources/slashdot.md>)

Topics: [microsoft 365](<https://devfeed.tech/topics/microsoft-365.md>), [Microsoft](<https://devfeed.tech/topics/microsoft.md>), [health check](<https://devfeed.tech/topics/health-check.md>), [infrastructure monitoring](<https://devfeed.tech/topics/infrastructure-monitoring.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [americas](<https://devfeed.tech/tags/americas.md>), [automated](<https://devfeed.tech/tags/automated.md>), [change](<https://devfeed.tech/tags/change.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [component](<https://devfeed.tech/tags/component.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [connect](<https://devfeed.tech/tags/connect.md>), [connectivity](<https://devfeed.tech/tags/connectivity.md>), [copilot](<https://devfeed.tech/tags/copilot.md>), [disruption](<https://devfeed.tech/tags/disruption.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [fail](<https://devfeed.tech/tags/fail.md>), [failed](<https://devfeed.tech/tags/failed.md>), [health](<https://devfeed.tech/tags/health.md>), [health-checks](<https://devfeed.tech/tags/health-checks.md>), [microsoft](<https://devfeed.tech/tags/microsoft.md>), [microsoft-outlook](<https://devfeed.tech/tags/microsoft-outlook.md>), [outlook](<https://devfeed.tech/tags/outlook.md>), [update](<https://devfeed.tech/tags/update.md>)

## AI overview

A Microsoft 365 outage disrupted Outlook, Teams, Copilot and SharePoint for users across the Americas; both individual and enterprise Outlook users reported login problems. The excerpt reports more than 129,000 Downdetector reports and says Microsoft attributed the disruption to unavailable servers overloading remaining infrastructure. Microsoft was redistributing traffic, testing a configuration change to address automated health-check failures, restarting affected servers, and monitoring their return to service. Its investigation pointed to a component processing server health, and it said it had taken steps to prevent further servers from being affected. No restoration estimate is included. The excerpt's final update is cut off.

## Source excerpt

Microsoft is suffering a major Microsoft 365 outage that's disrupting Outlook, Teams, Copilot and SharePoint for users across the Americas, with more than 129,000 problem reports logged on Downdetector shortly after the disruption began. Microsoft blames the connectivity problems on an unexpectedly large number of unavailable servers that overloaded the remaining infrastructure. The company says it's redistributing traffic and restarting affected systems. From a report: Microsoft was not providing an estimated time by which it expects service to return. Both individual Outlook users and those on enterprise accounts experienced problems logging in to the service. The outage also affected other Microsoft services, including Microsoft Teams, the Copilot 365 AI service and SharePoint Online. "Users may be unable to connect to multiple Microsoft 365 services," the company said on its Service Health Status page. UPDATE 11/12/26, 19:50 UTC: From Microsoft 365 Status: "We're testing a configuration change to address a problem that's causing servers to fail automated health checks and become unavailable. In parallel, we've initiated a restart of all affected servers and are monitoring health as they return to service. More info under EX1550543 and MO1550821 in the Microsoft 365 admin center, as well as http://status.cloud.microsoft if the admin center is not available to you." UPDATE 11/12/26, 20:19 UTC: From Microsoft 365 Status: "We've not identified any recent change correlated with the start of impact; however, our investigation indicates the failed health checks may originate from a specific component that's responsible for processing server health. We've taken steps to prevent additional servers from being impacted while we work to return the affected servers to service. More info under EX1550543 and MO1550821 in the Microsoft 365 admin center, as well as http://status.cloud.microsoft if the admin center is not available to you. UPDATE 11/12/26, 20:29 UTC: "According t