30 hour Microsoft 365 outage: what you can claim and how

Exchange Online was down for 30 hours and 5 minutes on November 12 and 13, and business, enterprise and education customers can make a Microsoft 365 outage Service Level Agreement claim for a credit on future bills. Here’s what you are entitled to and how to make an SLA claim.

Microsoft’s Exchange Online outage lasted just over 30 hours, according to Microsoft’s own incident report, EX1550543. Microsoft blames a problem left over from a network capacity upgrade. Business, enterprise and education customers can apply for a credit against future bills.   This is called a “Service Level Agreement” or SLA claim.

If every one of your users lost Outlook on the web for the whole time, you can claim a 50% Exchange credit, but not 100%. Most organizations will qualify for less, and some for nothing.

SLA claims don’t apply to Microsoft 365 consumer plans; Personal, Family, Premium or Pro plans.

What happened

Microsoft’s report says users “may have been unable to connect to their Exchange Online mailboxes” for 30 hours and 5 minutes (1,805 minutes).

Microsoft uses the term “may” when the company knows damn well that all customers were affected around the world.

 UTCUS Eastern
StartThu Nov 12, 10:05Thu Nov 12, 5:05 a.m.
EndFri Nov 13, 16:10Fri Nov 13, 11:10 a.m.

These are the official times for the outage. Some reports give the start as 16:17 UTC, but that’s when the incident was first posted, not when the impact began.

What stopped working

All the main ways of reaching a mailbox failed:

  • Outlook on the web
  • MAPI, which desktop Outlook uses
  • Exchange ActiveSync, used by most phone mail apps
  • REST API, used by apps and services that connect to mailboxes

Of those, only “Outlook on the web” matters for an SLA claim.

Mail flowing between Exchange Online and on premises Exchange servers may also have been affected. Problems with Teams, SharePoint and other services are covered by a separate incident, MO1550821.

What caused the Microsoft 365 breakdown

Microsoft says the outage came from a problem during an earlier network capacity upgrade, which surfaced after a more recent network change. It says the cause was technical and not related to a cyberattack, AI or agents.

Microsoft restored service gradually, checking stability at each stage. Even its last update said it was still restoring service to some customers and regions, so some users may have been down after the official end time.

Why making an SLA claim should not be necessary

Microsoft says the company is sorry for its unprecedented and huge mistake. If that was true, the company would not make customers go through all this ‘paperwork’ to make an SLA claim.

Instead, the company should just add an automatic credit to all affected customers.  After all, this was a global and complete outage, despite its use of weasel words like “may be affected”.

We believe all eligible Microsoft 365 customers should make an SLA claim, no matter how small.  Microsoft deliberately makes claims difficult to submit and the SLA terms are rigged to reduce the amount the company has to pay. 

Paying customers should push back forcing Microsoft to deal with the consequences of their mistake in the only way the company truly understands, by refunding customers, big and small.

The incident IDs to quote

You’ll need these for a claim. Find them in the Microsoft 365 admin center under Health | Service health.

Incident IDServiceWhat it covers
EX1550543Exchange OnlineMailbox connections, for 30 hours 5 minutes. Microsoft lists it as an incident, which can qualify for a credit
MO1550821Microsoft 365 suiteConnection problems with Teams, SharePoint, Copilot, Defender XDR, Planner and To Do
TM1550488TeamsA separate, earlier Teams problem for users routed through North and South America.

All three reports are rated as “incident”, which means the SLA credit policy applies.

Microsoft 365 outage: Teams & Exchange Online issues, Nov 12-13, 2026 : Office-Watch.com

What it means for SLA claims

The most anyone can get from EX1550543 alone is a 50% Exchange credit.

Only one kind of failure counts for Exchange: users unable to send or receive email in Outlook on the web. EX1550543 lists Outlook on the web, so it fits.

The SLA counts user minutes: minutes of downtime multiplied by the number of users affected.

Why wait until the end of the month?

A 100% credit needs more than 36 hours of downtime in November, and this outage was 30 hours 5 minutes.

You’d need about six more hours from other November Exchange incidents to reach 100%.

Why not wait until November 30 to make a claim.  If (heaven forbid) there’s more trouble, it might be possible to make a larger claim.

SLA claims must be made by the end of the month after the incident/s, so you have until the end of December to make a claim direct to Microsoft.  Resellers will have a shorter deadline.

Also, the PIR “Post Incident Report” is the better evidence to use in an SLA claim. For the November 2026 disaster, the final PIR is due by November 20th.

One or two users on Business Basic or Standard

For a one-person business, losing Outlook on the web for the whole outage means 95.82% uptime and a 50% credit. For two users, November has 86,400 user minutes:

What happenedLost user minutesUptimeCredit
Both users out for the full 30 hours 5 minutes3,61095.82%50%
Both users out for 8 hours96098.89%50%
Both users out for 3 hours36099.58%25%
One of the two out for 30 minutes3099.97%Nothing

In money, two Business Standard users pay $28 a month, so a 50% credit is worth at most $14. On Business Basic it’s at most $7. One user gets half those amounts. The credit only covers the Exchange share of the price, so expect less.

A 50 user office

November has 2,160,000 user minutes for 50 users.

What happenedLost user minutesUptimeCredit
All 50 users out for the full 30 hours 5 minutes90,25095.82%50%
All 50 users out for 8 hours24,00098.89%50%
10 of the 50 out for 3 hours1,80099.92%Nothing

On Business Standard, 50 users pay $700 a month, so a 50% Exchange credit is worth at most $350.

Teams, Copilot and home users

  • Teams: the morning problem (TM1550488) ran 68 minutes, more than the 43.2 minute line. If every Teams user in your organization couldn’t chat or start meetings for that whole time, it’s enough for a 25% Teams credit on its own. Any Teams downtime from MO1550821 adds to the same November total.
  • Copilot: there’s no separate uptime promise for Microsoft 365 Copilot that we could find, so Copilot being down adds nothing.
  • Home plans (Microsoft 365 Personal, Family and so on) have no SLA, so there’s nothing to claim.

A sample claim for the November outage

Here’s a partly completed claim based on the 12/13 November incident only.

Subject: SLA service credit claim: Exchange Online, incident EX1550543

We are claiming a service credit under the Service Level Agreement for Microsoft Online Services for the incident below.
Organization: [company name]
Tenant ID: [tenant ID]
Subscription: [Microsoft 365 Business Standard], [2] licenses, bought direct from Microsoft
Service affected: Exchange Online
Incident ID: EX1550543 as shown in Service health

1. Description of the incident
Our users could not send or receive email in Outlook on the web. They saw this error: 
They could not reach the website at all and got no response from the Microsoft service.

Outgoing Messages could not be sent.

Incoming messages were not delivered in a timely way.

2. Time and duration
Start: [date, time and time zone]
End: [date, time and time zone]
Duration: 1,805 minutes

3. Users affected
[2] of our [2] licensed users, at [office location].

4. Our attempts to resolve the incident

This was a widespread global problem that Microsoft has acknowledged.
We did try multiple connection methods using many versions of Outlook desktop and mobile. Outlook on the web was not available at all.

No separate support request was opened since Microsoft had already opened an incident.

5. Uptime calculation for [month and year]
User minutes: [30] days x 1,440 x [2] users = [86,400]
Downtime: [480] minutes x [2] users = [960] user minutes
Monthly uptime: ([86,400] minus [960]) divided by [86,400] x 100 = [98.89]%

This is below [99%], so we request a [50%] service credit for [Exchange Online] for November 2026

Attached: [screenshots, error messages, copy of the Service health incident report]

Contact: [name, role, email, phone]

What to do now

If you bought direct from Microsoft, the claim deadline for this outage is Dec 31, 2026. If you bought through a reseller, ask them for their deadline now; it will be earlier.

  • Save the incident pages today. Screenshot or print to PDF EX1550543, MO1550821 and TM1550488. Service health only shows the past 30 days, so they disappear around December 12
  • Get the Post Incident Reports. The preliminary one is due within two business days of the end, so by about Nov 17, 2026. The final one is due within five business days, by about Nov 20, 2026
  • Write down when your users lost and regained Outlook on the web, not just desktop Outlook
  • Do the user minutes math for Exchange, and separately for Teams if it failed too
  • Under 99.9%? Claim it. Direct customers: admin center, Help & support | Contact Support. Reseller customers: email your reseller from your company address with the details

When Microsoft 365 goes down again

For more on how Microsoft words its uptime promises and works out credits, Microsoft 365 outage credits: what you can really claim explains the SLA rules for every Microsoft 365 service, not just Exchange.

This isn’t the first time paying customers have been left without email. Microsoft outages hurt lots of paying 365 customers shows the pattern, and Was Microsoft 365 email down or not? looks at how Microsoft’s status reports can play down what users actually went through.

The next outage is a matter of when, not if. Three ways to prepare for a Microsoft 365 email outage has simple steps you can take now so your office can keep working when Exchange Online stops.

Your choice of Outlook makes a difference too. Microsoft outage shows how vulnerable the new Outlook is and New Outlook for Windows stops for 19 hours explain why the cloud based app fails harder than the desktop version, and How to Install Outlook Classic on Windows Instead of New Outlook shows how to switch back.