Outlook and Teams are back up, but Microsoft hasn't closed its 365 outage yet
The Microsoft 365 outage began at about 1.25pm ET on Thursday (6.25pm in Lisbon). By Friday night Outlook.com, OneDrive and Teams showed as operational, but Microsoft was still clearing queued mail and had not closed the incident. Microsoft blames servers that went unexpectedly unavailable, not a surge in traffic.
If Outlook or Teams threw errors at you this morning, it isn’t your laptop. The outage that knocked out a large part of Microsoft 365 on Thursday afternoon was still not fixed overnight: at 4.24am UTC on Friday, Microsoft’s official service status page was still reporting service degradation.
The services it lists are Outlook.com, OneDrive, OneNote, Microsoft To Do, Teams and Microsoft 365 for the web, with a warning that others may be affected too. Microsoft says recovery is continuing across the affected environment.
Is the Microsoft 365 outage fixed?
Not completely. At 10.30pm UTC on Friday, the status page showed Outlook.com, OneDrive, Teams Free and Office for the web as operational, but the overall Microsoft 365 incident was still marked as service degradation. In its latest update, at 8.03pm UTC, Microsoft said it was still draining queued messages and rebalancing traffic, that access could come back before mail flow fully caught up, and that it had no ETA for full recovery. The next update was due at midnight UTC.
When did the Microsoft 365 outage start?
At around 1.25pm Eastern on Thursday, according to Microsoft, which is 6.25pm in Portugal and the UK. Shortly afterwards Downdetector had close to 130,000 reports about Outlook alone. By 4.24am on Friday it had been running for almost exactly ten hours.
What does Microsoft say caused it?
Not a rush of users. Microsoft says load rose because a number of servers became unexpectedly unavailable, and a process that handles secure connections on the remaining machines got so overwhelmed that it stopped answering requests. Engineers paused deployments, freed up memory, rerouted traffic and rebooted servers, and late on Thursday began bringing machines back into service.
Can businesses claim compensation for the outage?
Some can. Microsoft 365 business contracts include service credits when monthly availability falls below the guaranteed level, and admins request them through the Microsoft 365 admin centre, quoting the incident ID: MO1550821 for Microsoft 365 and EX1550543 for Exchange Online. Personal Outlook.com accounts are unlikely to qualify.
If your working day lives in email, the practical advice holds: the desktop apps tend to cope better than the web versions, and anything important is safer with a copy outside the cloud until Microsoft calls it closed. And while you’re patching things, iPhone users have another update waiting: iOS 27.2.1, which fixes the iMessage group chat flaw.
By Oliver Grant
Image: Atomic Taco / Wikimedia Commons (CC BY-SA 2.0)