Microsoft's billing engine kept running through the outage that flattened Outlook, Teams and Exchange Online on November 12. The refunds, however, will not arrive on their own.

Under Microsoft's Online Services Service Level Agreement, business customers are owed a service credit — not a cash refund — whenever a service falls below 99.9 percent monthly availability. The formula is measured in user-minutes: the length of each incident in minutes multiplied by the number of users it hit. If the outage cost a business roughly 18 hours in a 30-day billing cycle, its Exchange uptime lands near 97.5 percent, which puts it in the 50 percent credit tier for the affected service.

The catch is that none of this is automatic. The SLA states that a claim must be submitted to customer support 'including all information necessary for Microsoft to validate the claim.' In practice that means opening a case with the affected resource name, the number of users impacted, the time and duration of downtime and a description of the errors. Wired, which walked through the process, also lists the incident codes to reference: Exchange (EX1550543), Outlook (MO1550821) and Teams (TM1550488).

And there is a deadline. Claims for the November 12 incident must be filed by December 31, 2026 — the end of the month following the outage.

Individual and family subscribers are not part of this. The consumer Microsoft Services Agreement promises no uptime at all and grants refunds only at Microsoft's 'sole discretion,' so personal Outlook accounts are effectively out of luck.

Microsoft has said it is 'deeply sorry for the disruption this incident has caused our customers and partners' and that it takes the trust placed in its services 'extremely seriously.' Whether that extends to processing thousands of small credit claims is the open question. For any company large enough to notice the bill, the practical advice is simple: gather the affected resource names and user counts, reference the incident codes, and file before the December 31 cutoff.