What was filed, and where
Law360 Canada reported on November 16 that Diamond & Diamond had filed the proposed class action. It said the firm suggests Canadian businesses' economic losses could exceed $100 million. Law360's public text is only a short teaser, so most of the detail below comes from the firm's own case page and the Open Class Actions write-up.
According to the firm's page, the statement of claim was issued on November 16, 2026. It was filed in the Ontario Superior Court of Justice at Newmarket under court file CV-26-00004427-00CP. The defendants are Microsoft Canada Inc. and Microsoft Corporation. The representative plaintiff is Metus Lykos Debt Law, a Markham, Ontario business. The firm says the business could not answer client emails, hold meetings or open files for about 24 hours.
Open Class Actions stresses the status of the case:
- The case has not been certified.
- Microsoft has not responded in court.
- There is nothing to claim, no settlement and no deadline.
Open Class Actions also says it had not found a U.S. class action over this outage as of November 18.
The outage itself
The firm says the disruption began around noon Eastern on November 12. It lists Outlook, Teams, OneDrive, SharePoint and Copilot among the affected services.
Microsoft's preliminary post-incident report, dated November 15, puts the impact window at 4:20 PM UTC on November 12 to 4:10 PM UTC on November 13, lasting nearly 24 hours. The scope was wider than the claim's list. WebProNews reports that Exchange Online, Teams, SharePoint Online, Copilot, Microsoft Graph, Defender XDR, Intune, Planner, To Do, Power Apps, Purview, Fabric, Universal Print, some Windows 365 Cloud PCs and some admin tools were all impacted.
On cause, Microsoft said it was not a cyberattack. Wccftech summarizes the report as describing a months-old Windows server defect, combined with increased traffic and reduced infrastructure capacity. The plaintiff's firm says more than 80% of affected gateway servers were unresponsive at the worst point.
The reports differ slightly on when the preliminary report appeared. Microsoft's report is dated November 15. The firm and Open Class Actions say it was released November 16. That is probably a gap between the date on the document and the date it became public.
The report is not the last word. A final report is scheduled for November 20. Details may change. Customer Windows PCs were not the failing component, because this was a cloud-side gateway problem.
What the claim alleges
The firm's page and Open Class Actions describe these allegations:
- Causes of action: breach of contract, negligence and unfair practices. The claim also seeks punitive and aggravated damages.
- Uptime: the claim says Microsoft's agreements required 99.9% monthly uptime. It also says Microsoft represented that its services were reliable and that updates went out through gradual, region-by-region safe deployment practices.
- Consumer law: for personal, family or household users, the claim relies on Ontario's Consumer Protection Act, 2002 and the equivalent laws in other provinces. It pleads that any terms blocking class proceedings, such as an arbitration clause or class waiver, are unenforceable for consumers. Whether that holds is for the court.
- Damages sought: lost revenue and opportunities, unproductive staff time, IT and overtime recovery costs, billing and collection delays, loss of use for personal subscribers, and subscription fees for services not provided.
Open Class Actions expects Microsoft's subscription terms and service-level commitments to be central to the contract claim. That is a reasonable expectation. It is not a finding.
Who might be in the class
As drafted, the proposed class covers individuals and organizations that live in or carry on business in Canada. They must have held a paid subscription or licence for an affected service during the outage. They must also have been unable to use it, or found it impaired.
- Sole proprietors, corporations and partnerships may be included.
- Free accounts may fall outside the definition.
- If your employer paid for your licence, the firm says you "possibly" qualify. That is not a yes.
- The claim is filed in Ontario but covers all provinces and territories.
- The court sets the final class definition.
The $100 million figure
Treat the $100 million number with care. The firm calls it an illustrative scenario. It rests on assumptions about Canadian adoption of Microsoft 365, how many businesses were disrupted, and how much revenue could not be recovered. The firm's own disclaimer says it is not a finding of loss. It is an advocacy number from a firm that is also collecting names for a database.
What admins should do now
This is general IT practice, plus the firm's own record-keeping advice. It is not legal advice, and it does not mean you are a class member.
- Preserve evidence. Keep licence and subscription details, invoices, and Service Health or admin center notices. Incident IDs here were EX1550543 and MO1550821.
- Document the impact. Save screenshots of errors and note when access failed and returned. Keep records of cancelled meetings, delayed invoices, overtime and workaround costs.
- Read before you sign. The firm warns that a service credit or release offered by Microsoft or a reseller could affect your rights. Check the terms first.
- Check your actual contract. Do not assume every customer has the same uptime commitment or remedy. Enterprise agreements, resellers and consumer terms can differ, and this reporting does not establish what any one agreement provides.
- Watch the final report. Microsoft's November 20 report may refine the cause and the repair items.
The firm's sign-up form adds your details to its database. It says doing so creates no lawyer-client relationship and does not guarantee membership or compensation. Open Class Actions is an informational site with its own sign-up prompts, so treat it as secondary reporting.
What happens next
In Ontario, a judge must certify the case before it can proceed for the class. That means deciding whether the claims raise common issues and whether a class action is the preferable way to resolve them. Microsoft's response, including any challenge based on its contract terms, will shape what happens. Any money would come only from a court-approved settlement or judgment. Until certification, the case is only a proposal.
For IT teams, the outage is a reminder to plan for cloud dependence. Many orgs have no email or collaboration fallback plan. A proposed lawsuit won't help during the next incident. Documented continuity procedures will.
Update: Microsoft 365 customers reportedly must request outage service credits manually (November 18, 2026)
The Register reports that Microsoft is directing affected Microsoft 365 customers to apply for service-credit reimbursement rather than issuing credits automatically after the November 12–13 outage. According to the outlet, customers must locate the relevant outage ID and submit a request through the Microsoft 365 Admin Center.
That process could create additional work for IT administrators and managed service providers, especially where a partner administers many customer tenants. The Register also reports that there is no apparent bulk-submission option, though Microsoft has not publicly confirmed the process or any automatic-credit plan in the material cited by the outlet.
For organizations preserving outage evidence, this makes the incident IDs and service-health notices more important. Admins considering a credit request should retain tenant-level impact records, subscription details and any communications about eligibility, while checking their own agreement’s service-level terms and claim process.
References
- Microsoft 365 Outage Class Action Filed in Canada - openclassactions.com openclassactions.com · 2026-11-19T02:00:00+00:00
- Microsoft faces proposed class action over global Microsoft 365 outage - Law360 Canada Law360 Canada · 2026-11-16T21:41:07+00:00
- Time for frustrated M365 customers to stage a 'distributed denial of satisfaction' action The Register · 2026-11-18T08:45:00+00:00