Microsoft News: Global Outage Hits Outlook, Teams
The microsoft news breaking on Thursday was the kind that stops workplaces cold. A global Microsoft 365 outage knocked out Outlook, Teams and Copilot for millions of people, and more than ten hours after it began the company was still struggling to bring its services back. The disruption started in the United States on Thursday afternoon, spread to 74 countries and territories within an hour, and was still not fully resolved when business hours began on Friday across Asia and the Pacific. Microsoft said a large number of its servers had become unexpectedly unavailable, and its fixes were not working as expected — a blunt admission from a company whose cloud sits at the centre of daily work worldwide.
Outlook bore the brunt of the failure. The email service is the front door to Microsoft’s cloud for hundreds of millions of workers, and when it stopped responding, inboxes, calendars and contacts went with it. Microsoft said the parts of Microsoft 365 that depended on Exchange Online — the cloud platform behind email, calendar, contacts and tasks — were affected, while elements that did not rely on it kept working. That explained the uneven experience: some Teams meetings went ahead as scheduled, while others could not make or receive calls, and Copilot, the company’s artificial intelligence assistant, stopped working alongside the email it is built on. SharePoint was also caught up, and complaints piled up for Microsoft 365, Copilot and OneDrive as well.
The scale showed up quickly on Downdetector, the outage tracker that collects status reports from users. Reports of problems with Outlook in the United States peaked at more than 130,000 shortly after 1 p.m. Eastern Time on Thursday, with one count putting the peak at 138,058 reports. The flood eased through the evening — to about 34,490 by Thursday evening, more than 25,000 still coming in at 9:30 p.m. Eastern, and around 18,000 at 11:30 p.m. — but the numbers stayed far above normal deep into the night. Reports of wider Microsoft 365 problems had fallen to nearly 13,000 by 5:47 p.m. Eastern, with 763 users reporting trouble with Teams. By Friday morning, reports were still appearing across Asia-Pacific, including India, Australia and Japan, as the working day began there.
What Went Wrong Inside Microsoft’s Servers
Microsoft’s explanation pointed inward, at its own infrastructure, rather than at a surge of outside traffic. The company said a portion of its infrastructure was experiencing elevated load across multiple regions, likely contributing to the connectivity errors. It later clarified the point: a number of servers had become unexpectedly unavailable under elevated load, and the problem was not driven by an increase in traffic. The system did not buckle because too many people tried to use it at once, but because parts of the system itself dropped out, leaving the remaining servers to carry more than they could handle.
The repair effort did not go to plan. In its latest update on Thursday, Microsoft said the steps it had taken to fix the outage were not going as expected. “We’ve monitored the status of the changes applied to improve serviceability and confirmed they’re not taking as expected,” the company said in a post on X. It added that it was identifying alternate workstreams to increase capacity in the face of what it called sustained traffic management imbalances. Earlier, the company had said the servers it had restored remained stable and that it was shifting traffic to alternate routes wherever possible. By 6 p.m. Eastern, Microsoft said it had observed limited recovery as users gradually reconnected.
Microsoft is tracking the incident under two identifiers in the Microsoft 365 admin centre: EX1550543, covering Exchange Online, and MO1550821, covering the wider Microsoft 365 impact. As of Friday morning in Asia, Microsoft had not confirmed full recovery, and it had not published a root cause. That silence was itself part of the story: Microsoft could say what had broken, but not yet why.
Who Was Hit
The outage reached far beyond individual inboxes. Businesses and government agencies around the world that run on Microsoft’s platforms were caught up in it. In Washington, the US House of Representatives said the outage had affected its users and its engineers were working with Microsoft. In Australia, the spy agency and the federal police were among the organisations hit on Friday. Government agencies in Australia, Japan and the United States were all affected, a measure of how deeply Microsoft’s cloud is embedded in public administration.
OpenAI said it was investigating an issue with Microsoft connectors in which new connections might be broken and tools were not working as expected. Anthropic said it had identified an issue with an upstream provider affecting its Microsoft 365 connector. The two are among the most prominent makers of artificial intelligence tools, and their problems showed how a failure in one company’s cloud can cascade into the products of others — an artificial intelligence news angle that underlined how interconnected the industry’s infrastructure has become.
The business consequences were concrete. Electric truck maker Workhorse Group, which had been expected to report third-quarter results on November 12, rescheduled the announcement to November 16, citing business disruptions caused by the global Microsoft outage — a listed company unable to publish its earnings on schedule because its email and collaboration tools were down.
In Malaysia, the National Cyber Coordination and Command Centre, known as NC4, told government ministries and operators of National Critical Information Infrastructure to audit their digital services after the outage. The advisory singled out a particular worry: the impairment of Defender XDR, Microsoft’s cloud-delivered security platform, left organisations that relied on it alone with diminished visibility over potential network threats while central servers remained compromised. The episode became a cybersecurity news story in its own right, not because anyone had attacked Microsoft, but because the tools used to watch for attacks had gone dark with everything else.
Not a Cyberattack, Microsoft Says
From the first hours of the outage, one question hung over the failure: had someone attacked Microsoft? The company moved quickly to close that line of inquiry down. It said it was not aware of any malicious activity causing the outage, and Australian Home Affairs and Cyber Security Minister Tony Burke said Microsoft believed it was not dealing with a cyberattack. “They believe they are dealing in some ways similar to what we saw with respect to CrowdStrike where there is an update that has gone awry,” Burke said at a press conference.
The comparison Burke reached for was the CrowdStrike malfunction of 2024, one of the largest internet disruptions on record, which hobbled technology systems in hospitals, banks and airports around the world after a faulty software update. That failure was not an attack either — a reminder that the world’s most connected systems can be brought down by their own complexity. Microsoft has not said that an update caused this outage, and Burke’s remark was a comparison rather than a diagnosis, but the parallel captured why the incident rattled so many organisations: the damage was internal, and it struck at the heart of everyday work.
There was awkward timing. Two days before the outage, Microsoft had issued a moderately severe warning about an actively exploited security flaw in Outlook, which allowed attackers to trick users into opening a corrupted message file without triggering Outlook’s security warning. That flaw was a separate matter, and nothing in the reporting connects the two. But it meant the outage arrived in a week when Outlook’s security was already under scrutiny.
Microsoft News: A Pattern, Not a One-Off
The November outage was not the first time this year that Microsoft’s cloud services have failed at scale. On July 23, 2026, a bug in Microsoft’s automated network maintenance system removed internet routes from far more devices than intended during a routine maintenance event, stranding a West US Azure data centre from Microsoft’s global network and knocking out Teams, SharePoint, OneDrive, Copilot and more than a dozen other cloud services across North America for nearly five hours. The disruption started at 10:44 a.m. Eastern and was not fully resolved until 3:41 p.m. Eastern, and Microsoft’s preliminary review traced the failure to the software layer that translates maintenance requests into machine-readable instructions. The incident also caused cascading outages in at least 19 downstream software platforms whose infrastructure routes through Azure’s West US region.
The July failure followed a nine-hour incident in January 2026, and only days before the November outage, on November 9, some users in Europe, the Middle East and Africa could not open their mailboxes in Outlook on the web for several hours. In October, Microsoft reported an Azure cloud outage that affected its productivity software and a range of industries worldwide. The November outage is the latest in a string of major disruptions to Microsoft’s cloud services in 2026, each with a different technical trigger but the same result: email, meetings, files and AI assistants disappearing together, for hours at a time, across continents.
That recurrence is the deeper story. Each outage on its own can be explained as a technical fault. Taken together, they show how much of the world’s daily work now depends on a small number of cloud platforms, and how a failure in one can ripple through businesses, governments and the artificial intelligence tools that sit on top of them. The data center news behind these failures is rarely dramatic — a maintenance bug here, servers dropping out there — but the consequences are measured in lost working hours, delayed earnings and government services running blind.
What Happens Next
The immediate question is when the services will be fully back. As Friday began in Asia and the Pacific, Microsoft was still restoring the affected servers, and the recovery was uneven: some users were reconnecting while others still saw errors or slow connections in Outlook, Teams and SharePoint. Microsoft has not yet confirmed full recovery or published a root cause. For IT administrators, the company points to incidents EX1550543 and MO1550821 under Service health in the Microsoft 365 admin centre.
For the millions who lost their email for a working day, the outage is a reminder of a vulnerability that no amount of familiarity can remove. Outlook and Teams feel like utilities, as reliable as electricity, until the day they are not. Businesses that could not send an email, join a meeting or open a file will be reviewing their backup plans. The full accounting — what broke, why, and what Microsoft will change — will come in the company’s post-incident review. Until then, the story stands as the biggest technology news of the week: a global failure, a fix that did not work as expected, and a working world left waiting for its inbox to come back.
Source: CNN