Microsoft 365 and Outlook suffer major worldwide outage
A massive worldwide technical failure knocked out Microsoft 365, Outlook, and Teams on Thursday, leaving millions of professionals without enterprise software.
Microsoft 365 and Outlook suffer major worldwide outage
Millions of professionals across the globe found their workdays severely disrupted on Thursday, Nov. 12, as a massive worldwide technical failure knocked out essential enterprise software products. The disruption dragged on into Friday, affecting many users, companies, and some government operations from Asia to the U.S. For ordinary users trying to log in, the failure meant frozen inboxes, inaccessible collaboration tools, and broken communication lines during the middle of the workday. The disruption hit major business platforms including Microsoft 365, Outlook, Teams, SharePoint Online, Copilot 365, and Defender XDR.
The tracking platform Downdetector recorded more than 129,000 error reports as the crisis unfolded on Thursday, with Outlook alone drawing over 100,000 complaints from frustrated users. Downdetector later recorded more than 130,000 users reporting problems accessing Outlook, although new reports have since fallen from that peak. Microsoft 365 saw nearly 50,000 reports, while the company's AI assistant and chatbot, Copilot, also went down. Even Microsoft’s official service status page briefly stopped loading as traffic surged with inquiries, blinding users who turned to the company for answers. More than 430 million people use Microsoft 365 apps, Microsoft said on its website.
What Caused the Servers to Fail and How Did Microsoft Respond?
The technical crisis began in the early afternoon on Thursday, prompting an immediate scramble by engineering teams to identify the failure point. Microsoft initially posted an update at 12:54 p.m. ET to X stating that customers were having problems with Exchange Online mailboxes in the Americas. Within minutes, by 1:07 p.m. ET, the tech giant acknowledged the problem was far more widespread, affecting service connectivity for users in any region. The Redmond, Washington-based company said early Friday that the outage was affecting a wide range of Microsoft 365 offerings that interact with its Exchange Online and email services.
Engineers quickly determined that the crisis was not driven by an overall increase in traffic. Instead, the failure stemmed from a large number of servers becoming unexpectedly unavailable, which forced a heavy, unmanageable load onto the remaining infrastructure. In a post on X, the company detailed its diagnostic findings: 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.
As public frustration mounted, users vented on social media, with one X user demanding, Dude in simple English, have you been hacked or nah?
Microsoft said it didn't have any indication the outage was caused by malicious activity and would treat the incident with urgency until full mitigation.
In Australia, Home Affairs Minister Tony Burke said Friday Microsoft had likened the widespread outage to the CrowdStrike outage in 2024. Burke said he had spoken to Microsoft's top executive in Australia and the government's national cybersecurity coordinator about the global disruption.
They (Microsoft) don't believe they are dealing with a cyberattack. They believe that they are dealing in some ways (with something) similar to what we saw with respect to CrowdStrike where there is an update that has gone awry,
Tony Burke via CBS News Burke told reporters in Sydney.
Texas-based cybersecurity company CrowdStrike blamed a bug in an update that allowed its systems to push bad data out to millions of customer computers, setting off a global tech outage in July 2024 that grounded flights, took TV broadcasts off the air and disrupted banks, hospitals and retailers.
Microsoft worked to prevent additional servers from being impacted while attempting to resuscitate the disabled hardware. By shortly before 4 p.m. ET on Thursday, the company reported that while validating a targeted change, many of the affected servers had become unresponsive. This unresponsiveness prevented engineers from confirming whether their fixes were effective, forcing teams to manually restart the servers so they could come back online with the patch in place.
By Friday, Microsoft reported making additional progress using a measured approach to identify and repair affected infrastructure.
The company stated:
We've made additional progress toward service recovery, with recovery actions completed across portions of the affected infrastructure in the Asia Pacific region. Traffic is being gradually restored, and we're seeing improvements in key customer scenarios, including mailbox access and delayed email processing. However, some users may continue to experience intermittent issues.
Microsoft via CBS News
The company added that its focus is now on extending these recovery actions across affected infrastructure in other regions, while continuing stabilization efforts and adding supporting capacity to improve service consistency.
Who Was Impacted and What Are Experts Advising Users to Do?
While the outage hit businesses, enterprise software users, and some government operations hard across multiple continents, Microsoft's status page indicated that consumer products were spared from the failure.
The ripple effects extended to artificial intelligence platforms as OpenAI and Anthropic each reported that they were facing problems connecting with Microsoft 365 tools as more people use AI platforms to interact with other companies' software. Corporate financial communications also felt the pinch, as U.S.-based industrial technology company Workhorse Group Inc. Delayed a conference call on its quarterly earnings because of the outage.
Global supply chains and transportation networks managed the technical failure with mixed results:
- Hong Kong businessperson Danny Lau, who runs an aluminum firm, said his company's Outlook accounts couldn't receive updates from its U.S. customers due to the outage, warning that if the situation dragged on further, it could
impact the production timeline.
- Air India said its flight operations were unaffected by the Microsoft outage, but it temporarily rerouted its email services to ensure customer queries continued to reach the airline without interruption.
- IndiGo, another Indian airline company, reported disruptions to its email support services affecting its ability to receive customer queries, noting on X that its other support channels remained operational and its flight operations were unaffected.
- Singapore's Government Technology Agency stated that government emails were down and that the agency is working with Microsoft to resolve the issue.
- The Philippines' Supreme Court announced in a social media statement that the ongoing service outage affected some of its operations, including email responses.
- In Japan, Deputy Chief Cabinet Secretary Masanao Ozaki stated that the outage impacted the government's IT infrastructure and that authorities were
keeping a close eye on the developments.
Affected professionals facing slow responses or complete lockouts from the Outlook suite are advised by experts to look for alternative ways to connect with colleagues, such as picking up the phone to talk directly rather than relying on stalled email chains.
The incident lays bare the vulnerability of modern corporate infrastructure to sudden, cascading server failures. As troubleshooting continued, Microsoft stated it was applying its restart approach to additional affected portions of its infrastructure to validate results more broadly.
The next concrete milestone rests on Microsoft's ongoing server validation process, where engineering teams must successfully bring unresponsive infrastructure back online across all affected regions. Users and enterprise administrators should monitor Microsoft's official status page and corporate X account for the next service restoration updates and confirmation that server health checks have normalized.
Updated 1 time since publication; last update 14 November 2026, 01:40.