For Canadian businesses, a day without email can mean more than a missed message. It can mean delayed client decisions, interrupted meetings and work that cannot be recovered simply by reopening an inbox.
Those costs are now at the centre of a proposed Canada-wide class action against Microsoft Canada Inc. and Microsoft Corporation following a global Microsoft 365 outage on November 12 and 13, 2026.
Filed in Ontario and announced on November 16, the case alleges that paying customers suffered economic losses when services they relied on became unavailable. The claim is still at an early stage: a court has not certified the class action, determined Microsoft’s liability or awarded damages.
Microsoft Faces Legal Action Over the November Outage
The legal challenge was announced by Diamond & Diamond Lawyers on November 16 and brought before the Ontario Superior Court of Justice. It names Microsoft Canada Inc. and Microsoft Corporation as defendants and seeks to represent individuals and businesses across Canada who paid for affected services but experienced disrupted access. The allegations include breach of contract, negligence and unfair practices. Those claims are accusations made by the plaintiff, not findings established by a judge.
The lawyers are seeking aggregate damages, alongside punitive and aggravated damages. Aggregate damages could address qualifying losses on a class-wide basis if the legal requirements are met, while the other requested remedies would have different legal purposes. Nothing has been awarded, and the lawsuit’s proposed national scope does not mean every affected Canadian automatically qualifies. For now, the filing sets out the plaintiff’s case and begins a process in which Microsoft will have an opportunity to respond and contest the allegations.
A Markham Business Says It Lost Nearly 24 Hours of Productivity
The proposed representative plaintiff is Metus Lykos Debt Law, a business based in Markham, Ontario. According to the law firm’s announcement, the company alleges that for approximately 24 hours it could not properly respond to client emails, hold meetings or access business files. It says the interruption produced missed opportunities, staff time that could not be put to productive use and costs associated with recovering from the disruption.
The account captures why a technology outage can translate into a financial dispute. An employee may still be paid while waiting for a system to return, but the client whose question went unanswered may not wait. A meeting can be rescheduled; a deadline or potential sale may be harder to recover. Those are illustrations of the losses businesses might face, not independently verified details of Metus Lykos’s accounts. Whether this plaintiff can prove its claimed damages, and whether they can be attributed legally to Microsoft, remain questions for the proceedings.
The Global Outage Disrupted Outlook, Teams and Other Services
Microsoft’s preliminary incident report identifies the disruption as running from 4:20 p.m. UTC on November 12 until 4:10 p.m. UTC on November 13, just ten minutes short of 24 hours. Exchange Online was the most severely affected service: many users were unable to access mailboxes through Outlook or other email clients, and message delivery was delayed. The impact was global, but not every customer lost every service for the entire period.
The problems also reached features within Teams, Copilot, OneDrive, SharePoint and other Microsoft 365 products that rely on Exchange Online. That distinction matters. Microsoft reported that many functions remained available, and that Teams chats and meetings worked for much of the incident after traffic moved to alternative infrastructure. An organization might therefore have experienced a blocked inbox and broken scheduling without a complete shutdown of collaboration tools. The uneven impact will matter when customers describe their losses and seek compensation.
Canadian Hospitals, Courts and Travellers Also Felt the Disruption
The disruption extended well beyond ordinary office inboxes. Alberta’s Court of King’s Bench warned on November 12 that the outage could delay communications and electronically submitted materials. It subsequently extended email-filing deadlines that had fallen on November 12 to November 13. For lawyers and court staff, even a brief delay can complicate processes that depend on time-sensitive notices and confirmations.
Other Canadian institutions reported disruption as well. Via Rail warned passengers that email communications about their journeys might not arrive, while Canadian hospital networks reported email difficulties and directed some inquiries to alternative channels. Insurance Business reported that Unity Health Toronto declared a code grey while emphasizing that patient and resident care was not affected. These examples do not prove the amount of anyone’s financial loss, nor do they make those institutions parties to the lawsuit. They do show how a shared software problem can ripple through travel, health care and the justice system.
Microsoft Identifies a Hidden Software Defect Behind the Failure
Microsoft’s preliminary investigation traces the breakdown to a software defect introduced in July that remained hidden for months. The defect affected specialized Windows-based networking gateway servers used by Microsoft 365, rather than Windows devices generally. It became dangerous under a particular combination of traffic and hardware conditions that Microsoft’s ordinary testing had not reproduced. That helps explain why a problem could exist for so long before suddenly affecting customers around the world.
The trigger involved several failures converging. Microsoft says Teams traffic had shifted onto infrastructure shared with Exchange Online roughly 15 hours before the outage, while an unrelated problem had already taken nearly 14% of gateway server capacity offline. Overloaded servers stopped responding; attempts to redirect users overwhelmed the remaining servers. At the worst point, more than 80% of the affected gateway fleet was unresponsive. Microsoft has characterized the event as a technical failure, not a cyberattack, and says its investigation remains preliminary.
Microsoft’s 99.9% Uptime Commitment Becomes a Central Issue
A central allegation concerns Microsoft’s commitment to 99.9% monthly availability. That figure sounds comfortably close to perfect, but even a small shortfall matters when a company organizes its work around continuous access. Over a 30-day month, 99.9% uptime corresponds to roughly 43 minutes of permitted downtime. An interruption measured in many hours therefore raises serious questions about the reliability customers believed they were purchasing.
Yet the contractual picture is more complicated than one percentage. Microsoft’s published service-level agreements set out different definitions of downtime, qualifying services, credit calculations and exceptions. Those terms may depend on the service and the agreement under which a customer subscribes. The proposed lawsuit alleges that Microsoft failed to honour an uptime standard; the legal question is whether the relevant contractual obligations were breached and what remedies are available. A global outage alone does not establish that every feature, account or subscription experienced an identical contract violation.
Lawyers Suggest Canadian Economic Losses Could Exceed $100 Million
The eye-catching figure attached to the lawsuit is a potential loss exceeding $100 million. It is important to understand where that number came from. Diamond & Diamond used an illustrative scenario, not a completed accounting of Canadian businesses’ losses. The firm started with approximately 1.37 million employer businesses and extrapolated that roughly one million might use Microsoft 365. It then assumed 80% suffered significant disruption and half a normal day’s revenue could not be recovered.
Statistics Canada’s June 2026 data count 1,366,418 Canadian business locations with employees, broadly consistent with the firm’s starting figure. But locations are not necessarily unique companies, and the adoption and revenue assumptions have not been independently established. Some businesses may have recovered much of their delayed work; others may have lost time-sensitive business permanently. The $100-million scenario illustrates how costs could accumulate across many customers. It should not be presented as damages already proven or money Microsoft has been ordered to pay.
Service Credits May Not Cover Lost Revenue and Productivity
Businesses seeking compensation have a second route to consider besides litigation: service credits under Microsoft’s contractual terms. These typically reduce charges for an affected service if the customer qualifies, rather than reimbursing every dollar of lost sales or employee time. Microsoft’s guidance for cloud-service partners says requests depend on which product was disrupted, how long the disruption lasted and evidence that particular customers were affected. A broad service advisory alone does not establish eligibility.
For eligible partner-managed subscriptions, Microsoft instructs providers to document the tenant, outage identifier, affected users and timing, and generally submit non-Azure service claims within one month after the affected billing month ends. That administrative process is different from asking a court for business-interruption damages. Technology experts interviewed by Australia’s ABC warned that ordinary service credits can be much smaller than lost productivity. Canadian claimants will need to examine their own contracts rather than assume every subscription carries the same protection or deadline.
The Proposed Class Action Must Clear a Major Legal Hurdle
Before a Canada-wide group can advance its claims together, the Ontario court must decide whether to certify the proceeding. Under Ontario’s Class Proceedings Act, that involves questions such as whether there is an identifiable class, whether members share common issues and whether a class action is the preferable way to resolve them. The court must also consider the proposed representative plaintiff and its plan for conducting the case. Certification is a procedural step, not a ruling that Microsoft acted unlawfully.
The range of experiences during the outage could become important. A firm shut out of its mailbox for a full working day may have a different loss calculation from someone who briefly lost calendar access. Contract terms may also vary. Separately, Consumer Law Group announced an investigation into potential claims arising from the same outage, but an investigation is not the same as this filed action. As of November 17, Diamond & Diamond’s proposed class action has not been certified.
The Case Raises Bigger Questions About Canada’s Dependence on Cloud Services
The lawsuit may also intensify a wider conversation about dependence on a small number of technology suppliers. Microsoft’s account of the outage shows how an internal gateway failure could affect email and the connected tools used by many organizations at once. Insurance specialists have cautioned that ordinary cyber policies may not necessarily cover a non-malicious service failure; coverage depends on the wording, waiting periods and whether third-party outages are included.
Canadian financial regulators already treat such dependencies as a resilience issue. The Office of the Superintendent of Financial Institutions expects federally regulated financial institutions to assess third-party concentration risk and plan for disruptions to critical operations. Smaller organizations may not face those specific regulatory requirements, but the practical questions are similar: Can staff reach clients without their usual email? Are essential contact details available elsewhere? Can urgent work continue safely? The court case will address legal responsibility, while businesses decide how much interruption they can afford the next time a shared platform fails.