Outagepilot · Daily Ships · Monday 16 Nov 2026

Microsoft 365 went down? Work out your SLA credit.

Exchange Online / Microsoft 365 was down on 12–13 Nov 2026 (EX1550543, MO1550821, TM1550488). Microsoft does not pay SLA credits automatically — you have to claim, with evidence, before the deadline. The form below is prefilled with that outage for a fictional 40-user firm (Northwind Surveyors, example fees). One click on “Work out my credit” gives you the answer.

Your setup
Services and fees

Enter a per-user monthly fee or a total monthly fee for each service. Buying a suite? Enter the suite fee, then the share of it for this service. The SLA says: “If you purchased more than one Service (not as a suite), then you may submit claims pursuant to the process described above as if each Service were covered by an individual SLA. Fo…” It gives no fixed split, so any share you enter is an assumption to confirm — credits apply only to the affected service.

Incidents

Incident IDs come from Service Health in the Microsoft 365 admin center. Postings marked Advisory are usually not eligible (Partner Center) and are excluded from the maths.

Worked examples

How the maths works

Microsoft measures uptime per service, per calendar month, in user-minutes: ““User Minutes” means the total number of minutes in an Applicable Period, less all Scheduled Downtime, multiplied by the total number of users.” Uptime = (User Minutes − Downtime) / User Minutes × 100. Below 99.9% the standard credit is 25%, below 99% it is 50%, below 95% it is 100% of that service’s fees for the month. Google adds days of service instead (3, 7 or 15). Every number here traces to the published SLA texts linked in the footer.