Early on a November morning, before the sun had risen over much of the Australian east coast, people reaching for their inboxes found the doors closed. Within minutes, complaints gathered in the crowd-sourced outage trackers, and what began as a stumble in one familiar tool revealed itself as a shared fault across Microsoft's connected services. The company traced the trouble not to a surge of demand but to a quiet loss of machines, leaving the rest to carry more than they were built for. Why those machines went dark remains an open question, and for now the work is one of careful return, wait
Microsoft Investigates Global Outage as Outlook, Teams, OneDrive and Copilot Users Locked Out
A large number of servers had become unexpectedly unavailable
Mark
Start with the basics. What actually happened?
Mimi
Around 4.30am AEST, Downdetector saw a sharp spike in reports. More than 120,000 people said they couldn't get into Outlook, and Teams, OneDrive and Copilot were disrupted too.
Mark
Microsoft says it's not a traffic surge. Why does that distinction matter?
Mimi
Because it rules out the obvious explanation. Demand didn't overwhelm the system. A large number of servers became unavailable, and the ones left standing took on their load.
Luke
Worth noting that's Microsoft's own account. Nothing independent has confirmed it yet.
Mark
And the cause of the servers failing?
Mimi
Still being investigated. Microsoft says it is working to return them to service safely.
Luke
Right, and that's the big unknown. We don't know why they dropped out, how many there were, or when service comes back.
Mark
What about the 120,000 figure?
Luke
It's a count of user reports on Downdetector. That shows scale, but it isn't a verified number of affected accounts, and people can report the same problem more than once.
Mimi
Still, it's a sharp enough spike to tell you this wasn't a local glitch.
Mark
So what should readers watch?
Mimi
Microsoft's Service Health Status page, where the company is posting updates on the cause and the restoration.
Der Puls
- Over 120,000 Outlook complaints flooded Downdetector in a sudden spike shortly before 4:30am AEST.
- Teams, OneDrive and Copilot faltered alongside Outlook, turning a single-app problem into a global disruption.
- Microsoft says a large number of servers went unexpectedly offline, forcing the remaining infrastructure to shoulder the load.
- The cause of the server failures is still unknown, and engineers are restoring machines carefully rather than all at once.
- Users are waiting on Microsoft's Service Health Status page for the next update on cause and recovery timeline.
Early on a November morning, before the sun had risen over much of the Australian east coast, people reaching for their inboxes found the doors closed. Within minutes, complaints gathered in the crowd-sourced outage trackers, and what began as a stumble in one familiar tool revealed itself as a shared fault across Microsoft's connected services. The company traced the trouble not to a surge of demand but to a quiet loss of machines, leaving the rest to carry more than they were built for. Why those machines went dark remains an open question, and for now the work is one of careful return, waited on by everyone who depends on the system.
Shortly before 4:30am AEST, people trying to open their email began hitting a wall. Downdetector, the site that tracks outage complaints, registered a sharp jump, and in a short time more than 120,000 users had reported trouble reaching Outlook.
The problem did not stop at email. Microsoft Teams, OneDrive and Copilot 365 were disrupted as well, and reports came in from around the world, suggesting a widespread failure rather than a fault in one product.
Microsoft acknowledged the issue and said it was investigating. Its later statement on the Service Health Status site offered a clearer picture: traffic had not suddenly increased. Instead, a large number of servers had become unexpectedly unavailable, and the work they had been doing was landing on the machines still running. The strain was a result of the failures, not their source.
What knocked those servers offline is still unknown. Microsoft says it is working out the cause while returning the machines to service safely, though it has not said how long that will take.
The 120,000 figure reflects user complaints rather than confirmed affected accounts, so it signals scale without giving an exact count. For anyone still locked out, the place to watch is Microsoft's Service Health Status page.
Shortly before 4.30am AEST, people trying to open their email began running into a wall. Downdetector, the website that tracks service outages, registered a sharp jump in complaints, and within a short time more than 120,000 users had reported problems reaching Outlook, Microsoft's email platform.
Outlook was not the only service affected. Microsoft Teams, OneDrive and Copilot 365 were all hit by disruptions as well, making this a widespread outage rather than a fault confined to a single product. Reports of the trouble were global in scope.
Microsoft acknowledged the problem and said it was investigating. In its account of what was happening, the company said it was experiencing elevated load across parts of its infrastructure, and it described the problem as occurring in any region, which means no single part of the world was singled out as the source.
The company then offered a more specific explanation in a statement posted to its Service Health Status site. Microsoft said the elevated load was not the result of an overall increase in traffic. Instead, it said, a large number of servers had become unexpectedly unavailable, and that was pushing work onto the servers still running. In other words, the strain on the remaining infrastructure was a consequence of the failures, not their origin.
What took those servers offline is not yet known. Microsoft said it was investigating the reason they became unavailable while working to return them to service safely. The wording about safety suggests the company is not simply switching machines back on, but that is an inference; the statement does not say how the restoration will be staged or how long it will take.
The original report was published as a developing story and carried a note that more was to come. The figure of 120,000 comes from user-submitted reports to Downdetector, which measures complaints rather than confirmed affected accounts, so it indicates scale without giving an exact count.
For anyone locked out, the place to watch is Microsoft's Service Health Status page, where the company has been posting its updates on the cause and on progress returning the affected servers to service.
Bemerkenswerte Zitate
The elevated load isn't driven by an overall increase in traffic, but by a large number of servers being unexpectedly unavailable, which is shifting load onto the remaining infrastructure.— Microsoft, Service Health Status site
Möchten Sie die ganze Geschichte?
Das Original lesen bei PerthNow ↗