Key points
- Microsoft customers must claim outage credits
- A full-day Microsoft email outage could trigger a 50% credit
- Microsoft promised a final incident report within five business days
Businesses that lost Outlook email during the Microsoft (MSFT) outage on Nov. 12 and 13 may qualify for a credit on their Exchange Online bill. The credit isn’t automatic. Customers must file a claim, and Microsoft’s service level agreement sets a Dec. 31 deadline for a November incident.
In a notice to administrators, Microsoft described an Exchange Online incident lasting nearly 24 hours. By our calculations, an organization whose users couldn’t send or receive email for that entire period would fall into the 50% credit tier for November. The result depends on the customer’s contract, Microsoft’s definition of downtime, any applicable exclusions, and acceptance of the claim.
Microsoft has apologized and provided a preliminary explanation, but it hasn’t said how many customers were affected. Microsoft shares closed at $523.88 on Nov. 13, up 0.2%, after rising 0.4% to $523.00 on Nov. 12.
How the Exchange Online credits work
Microsoft's service level agreement for online services, in its October 2026 version, promises Exchange Online customers a credit when uptime falls short. Downtime is any period when users can't send or receive email with Outlook Web Access. The credit is 25% of the fees for that month when uptime drops below 99.9%, 50% below 99%, and 100% below 95%.
Uptime is measured in user-minutes over the calendar month. By our calculations, if every user at an organization couldn't send or receive email for the whole stretch, the organization would fall below 99.9% after about 43 minutes of downtime in November, below 99% after about 7.2 hours, and below 95% after 36 hours.
Microsoft's notices to administrators, as posted by the University of Pennsylvania, describe the Exchange Online incident, tracked as EX1550543, as running from 11:20 a.m. ET on Nov. 12 to 11:10 a.m. ET on Nov. 13. The incident's header lists an earlier start, 5:05 a.m. ET on Nov. 12, with the same end time. Neither window is any one customer's measured downtime.
Using the 11:20 a.m. start, the outage lasted 1,430 minutes, or about 3.3% of November, which would leave uptime near 96.7%. Using the 5:05 a.m. start, it lasted 1,805 minutes, which would leave uptime near 95.8%. Both fall between the 99% and 95% marks, so an organization whose users were all down the whole time would land in the 50% tier under this calculation. If only some users were affected, or their downtime was shorter, the resulting credit could be lower or zero.
Some customers may have been down longer. Microsoft said in the Exchange Online incident’s final update, at 11:15 p.m. ET on Nov. 13, that it was still restoring service to remaining customers and regions, and its status account said early on Nov. 14 that it had "restored service to the remaining impacted customers and regions," CBS News reported.
Customers have to file their own claims
The credits aren't automatic. A customer has to file a claim with Microsoft support that includes a description of the incident, the time and duration of the downtime, the number and location of affected users, and the errors they saw. Claims missing that information will be rejected, according to the agreement. For an incident in November, the deadline is Dec. 31. Microsoft says it typically processes claims within 45 days. Microsoft's public updates on the outage that we reviewed don't mention service credits.
The credits have limits. They apply only to the fees for the service that fell short, can't exceed that service's monthly fees, and don't cover lost revenue or other losses. The agreement also excludes problems such as a customer's own misconfiguration and network issues outside Microsoft 365. Whether a customer qualifies depends on its own contract and how long its users were actually cut off.
Microsoft points to a latent bug exposed by network work
On Nov. 13, Microsoft said the incident stemmed from an issue during an earlier network capacity upgrade that surfaced after a recent network change, according to TIME. The company said it had addressed the underlying issue and that the outage was "not related to cyber or AI/agents." It also apologized for the disruption.
Its notice to administrators that evening went further. Microsoft said traffic shifts during standard network maintenance and upgrades "exposed a latent bug causing a rapidly increasing number of requests to queue for processing." The affected servers ran out of processing capacity and couldn't accept new connections, the notice said.
Microsoft told administrators it would provide a preliminary post-incident report within two business days and a final one within five, which by our count means Nov. 17 and Nov. 20. That incident’s latest update on the log, from 11:15 p.m. ET on Nov. 13, said a full report would follow once Microsoft's review is complete, and we haven't found a published report as of Nov. 16. Charles Lamanna, Microsoft's executive vice president for Copilot, agents, and platform, said Microsoft would publish a post-mortem with a timeline and repair items, CBS reported.
What Microsoft hasn't disclosed
Microsoft hasn't said what the network capacity upgrade or the later network change was, or what the latent bug is.
Microsoft hasn't said how many users or organizations lost service. More than 430 million people use Microsoft 365 apps, according to Microsoft's website, but CBS said it was unclear how many were affected. Patrick Anderson, president of the Michigan think tank Anderson Economic Group, estimated that perhaps as many as 26 million users on Nov. 12 and 51 million on Nov. 13 were disrupted in a way that caused an economic loss, CNN reported. The group put the cost at $7 billion in lost productivity. Those numbers are an outside estimate, not a count from Microsoft, and the two days shouldn't be added together, since some users may have been hit on both.
Governments, courts, and companies lost email
The US House of Representatives was affected, its communications department told TIME. So were the UK government, Britain's National Health Service, and the city governments of Austin, Texas, and Jacksonville, Florida. Workhorse Group postponed its third-quarter earnings release and investor call, Gizmodo reported.
Microsoft said it had "no indication" that the Federal Aviation Administration's nationwide ground stop on Nov. 13 was related to its services. The FAA's explanation doesn't mention Microsoft and points to its own telecommunications network.












