If your company pays for Microsoft 365 and its staff lost email for more than about 7 hours this week, Microsoft's own service-level agreement (SLA) says the company can ask for 50% of that month's fee for the affected service as a credit, but only if it files a claim by December 31.
The Microsoft 365 outage began on Thursday, November 12, US time, and lasted until early Saturday in Manila, when Microsoft reported broad recovery. It knocked out Outlook email and disrupted Teams, Copilot and other work tools in dozens of countries. In the Philippines it reached the courts and the overnight outsourcing workforce.
When the Microsoft 365 outage started in Manila time
Users began reporting that they could not open Outlook at about 16:00 GMT on Thursday. That is midnight on Friday in Manila. Microsoft first flagged the problem just before 1 p.m. US Eastern time, about 2 a.m. Friday in Manila, and Downdetector logged reports from 74 countries and territories within about an hour, according to the Associated Press.
That timing explains who here felt it first. Philippine reports spiked at 2:15 a.m. local time, "in step with US office hours," Ookla analyst Luke Kehoe said, linking it to the country's large outsourcing workforce serving US clients overnight, as reported by Technobaboy.
Which services went down
- Outlook (Exchange Online): hardest hit. Many users could not open mailboxes on the web, app or phone, and messages arrived late.
- Teams, SharePoint and Copilot: disrupted, although Teams chats and calls largely kept working.
- Admin and security tools: TechCrunch also listed Defender security screening, Intune device management and some cloud-based Windows PCs.
Admins can find the incident in the Microsoft 365 admin center under EX1550543 (Exchange Online) and MO1550821 (services that depend on it), LazyAdmin's incident tracker notes.
Supreme Court email and other PH effects
Communications at the Supreme Court of the Philippines were among those disrupted, Al Jazeera reported. The judiciary runs on PJ365, its Microsoft 365 platform with Outlook for email. In an advisory on November 13, the Court said "responses to emails and other transactions may be delayed" and that it was working with Microsoft to restore PJ365 services. Lawyers and litigants waiting on court email should expect slow replies until the backlog clears.
What caused it
Microsoft said a process on the affected servers "responsible for establishing secure connections becomes overwhelmed," and restored servers failed again once traffic returned, ABC News quoted the company. In a later update, Microsoft said the "incident was introduced by an issue during an earlier network capacity upgrade that surfaced following a recent network change." It apologized, saying "We are deeply sorry for the disruption," and reported "broad recovery and stability" while it kept restoring remaining customers, ABC News reported on Saturday.
Microsoft said it found no sign of a cyberattack. Microsoft executive Charles Lamanna said there is "no indication this is the result of malicious or cyber activity." A full post-incident report is promised.
Estimates of the length differ. Ookla put it at about 16 hours, Kentik's Doug Madory saw traffic return after about 18 hours, per TechCrunch, and Microsoft only reported broad recovery about a day after the first reports.
Did you lose any email?
Probably not. Microsoft said "the email timeout window has been extended to 48 hours to preserve delayed messages," per ABC News. Mail sent during the outage should arrive late rather than bounce, so check before resending.
How much can a company claim back?
The Microsoft SLA for Online Services (October 2026 edition) promises Exchange Online uptime of 99.9% a month. Downtime counts when users cannot send or receive email with Outlook on the web, and is measured per user.
| Monthly uptime | Service credit |
|---|---|
| Below 99.9% | 25% |
| Below 99% | 50% |
| Below 95% | 100% |
By our math, November has 43,200 minutes. A user locked out for 16 hours (960 minutes) had uptime of (43,200 - 960) / 43,200 = 97.8%, which lands in the 50% tier. The 99% line falls at 432 minutes (7.2 hours) of downtime, and the 100% tier needs more than 36 hours. This assumes every user was locked out for the whole period; users who still had partial access will show a higher uptime.
How to file the claim
- Who files: the company's Microsoft 365 administrator, or the reseller for companies that buy through a Microsoft partner. Free consumer Outlook.com accounts are not covered.
- What to include: under the SLA, a description of the incident, the time and duration of downtime, affected resource names, the number and location of affected users, and the errors seen. Missing details can get a claim rejected. Citing EX1550543 and MO1550821 helps.
- Deadline: for Microsoft 365 services, Microsoft must receive the claim by the end of the month after the incident, so December 31, 2026 for this outage.
- What you get: a credit against future service fees, not a cash refund. Microsoft says it typically processes claims within 45 days.
