Executive Summary: Key Legal and Evidentiary Issues

• Scope of evidence a defendant may adduce at the class action authorization stage under article 574 CCP, without turning that stage into a trial on the merits
• Admissibility of a draft sworn statement from Microsoft’s service engineering executive, limited to neutral facts about authorship of reports and existence of contractual documents
• Use of internal post-incident reports as contextual, extrajudicial evidence regarding the outage’s duration, causes and effects, without accepting their truth at this preliminary stage
• Necessity and relevance of filing the Microsoft Customer Agreement, Service Level Agreement and Azure incident-readiness webpage to complete vague or unsupported contractual allegations by the applicants
• Extent of the plaintiffs’ right to cross-examine the author of a sworn statement in a class action authorization context, and the court’s power to strictly limit scope and duration
• Application of proportionality and “essential and indispensable” criteria to control evidentiary volume while preserving the adversarial process at authorization

Background and facts of the case

Corporation Transport Vitesse and Services Camionnage Vitesse Inc. operate a logistics, warehousing and trucking business in Quebec. They subscribe to various Microsoft software and online services (including Microsoft 365 and Azure-related services) and rely on these platforms to manage and conduct their operations. In their view, the continuity and availability of these services are critical to their business activities. They allege that, between Saturday 1 March 2025 and Monday 3 March 2025, multiple Microsoft services became unavailable due to one or more significant service disruptions. The alleged outage affected not only their own systems but also other customers across Canada who use Microsoft’s cloud and productivity services. The applicants claim that the service unavailability caused them inconvenience, operational disruption and financial loss, including reduced revenue and business interruption. On that basis, they seek authorization to institute a class action on behalf of a proposed class comprising all consumers and businesses in Canada who either could not use one or more Microsoft services from 1 March 2025 until full restoration, or who were otherwise impacted by the alleged outage. Their proposed class action targets both Microsoft Corporation and Microsoft Canada Inc. and pleads that both entities breached contractual and legal obligations owed to class members.

Allegations and proposed class action

In their application for authorization to bring a class action, the applicants assert that Microsoft failed in its obligation to provide continuous, functional access to its services. They characterize the events as “Service Disruptions” that persisted from 1 March 2025 into 3 March 2025, though their own pleading is not entirely consistent as to whether there was a single prolonged disruption or two distinct outages in less than three days, one allegedly lasting a full day. Their claim is framed in contract and civil liability, and they seek a reduction of obligations as well as compensatory and punitive damages for all affected class members. The application, however, notably does not attach or detail any contractual documents governing the relationship between Microsoft and its Canadian customers. It simply alleges breaches of contractual obligations by both Microsoft Corporation and Microsoft Canada Inc., without specifying which entity actually contracts with customers, and without providing the terms under which Microsoft undertook to deliver services, maintain uptime or respond to incidents. This evidentiary gap becomes central to the defendants’ attempt to file targeted documentation at the authorization stage.

Microsoft’s request to file evidence at authorization

Microsoft responds with an application for leave to adduce limited evidence at the authorization stage, relying on article 574 CCP, which permits the court to authorize relevant evidence even though the contestation of authorization is, in principle, oral only. Microsoft seeks to file a sworn statement from its Vice President of Service Engineering, Michael Ziock, together with five exhibits. These are two “post-incident reports” for Microsoft 365 (dated 7 and 10 March 2025) prepared by the Incident Communications and Coordination team, a standard form Microsoft Customer Agreement, a Service Level Agreement (SLA) for Microsoft Online Services dated 1 July 2025, and a Microsoft Azure webpage titled “Microsoft Azure Incident Readiness.” In Microsoft’s view, this material is necessary for the court to properly assess the authorization criteria in article 575 CCP, particularly the colour of right element and the definition and existence of the alleged contractual framework underpinning the applicants’ claims. The applicants do not formally oppose the filing of this evidence but reserve their right to argue later that it is irrelevant or of little probative value. They also assert a right to examine Mr. Ziock on his declaration and seek 60 minutes to do so.

Governing principles on evidence at the authorization stage

The court restates and applies well-established principles governing evidence at the class action authorization stage in Quebec. Under article 574 CCP, the application for authorization is presumed to be based on facts taken as true at that preliminary stage; the judge’s task is to test the proposed legal syllogism against the article 575 criteria, not to act as the ultimate trier of fact. Evidence may still be admitted, but it must remain limited, proportionate and strictly “essential and indispensable” to evaluating the authorization criteria. The court must avoid converting authorization into a trial on the merits. Evidence may be admitted to demonstrate that certain allegations are obviously improbable or false, or to provide salient facts omitted from or to clarify vague or contradictory allegations in the authorization application. However, such evidence must not be open to serious challenge regarding its truthfulness or probative value, otherwise its admission risks triggering an adversarial debate that belongs at trial. Sworn statements are treated like written testimony and should be confined to neutral, objective facts within the personal knowledge of the declarant, avoiding hearsay and legal opinion. Against that background, the court exercises its discretion to prune Microsoft’s proposed material and to carefully cabin the permissible scope of any cross-examination.

Assessment of the sworn statement by Microsoft’s executive

Microsoft tendered a draft sworn statement from Mr. Ziock, who manages the team responsible for investigating the March 2025 service disruptions and preparing the post-incident reports. The court accepts that paragraphs establishing his role, his team’s involvement and the fact that they authored the internal reports are appropriate, neutral and necessary to introduce those reports into evidence. These portions are allowed, subject to the removal of defined terms like “First Service Incident” and “Second Service Incident,” since the number of distinct incidents is precisely a contentious factual issue that must not be predetermined through evidentiary labels at authorization. By contrast, paragraphs in which Mr. Ziock sets out Microsoft’s position on how many incidents occurred, their causes, and the extent of service availability are refused. These matters are actively contested by the applicants, who have indicated they will challenge Microsoft’s assertions about the number and duration of disruptions. Allowing this sort of detailed, opinion-laden narrative at the authorization stage would invite a trial-before-the-trial on central liability questions. The court instead confines itself to allowing only those elements of the statement that objectively identify the contractual documents relied upon and clarify which Microsoft entity contracts with customers. Paragraphs stating that the contractual relationship with the applicants is governed by the Microsoft Customer Agreement, incorporating the Service Level Agreement, and that Microsoft Canada Inc. does not itself enter into customer contracts, are admitted. This fills a significant evidentiary gap in the applicants’ pleadings, which alleged contractual obligations on both entities without providing any written contracts. Conversely, paragraphs where Mr. Ziock advances interpretive arguments about the scope of Microsoft’s obligations, or paraphrases or argues the meaning of various clauses, are excluded as improper legal argument for a witness and beyond what is “essential and indispensable” at this stage. A final paragraph describing a public Microsoft Azure webpage is also rejected as unnecessary, since the document can be filed directly without sworn evidence.

Treatment of the internal post-incident reports

The two post-incident reports summarize Microsoft’s internal understanding of the March 2025 disruptions, including their duration, probable causes, customer impact and remedial steps. They refer to two separate incidents: one on 1 March 2025 around 8:36 p.m. lasting about an hour, and another on 3 March 2025 at 4:22 p.m. lasting about two hours. As internal records, they are treated as extrajudicial declarations and cannot be admitted to prove the literal truth of the events they describe. The court nonetheless permits their filing for a limited contextual purpose: to show what Microsoft, at the time, identified as the number, cause, duration and effects of the disruptions. This contextual evidence becomes useful because the applicants’ own allegations are both sparse and internally inconsistent about whether there was a single continuous outage or two distinct events, and how long they actually lasted. Given this paucity and contradiction, the court finds that admitting the reports as context helps it evaluate whether the authorization criteria—especially the existence of at least a colour of right and the proposed common questions—are met. At the same time, the court cautions that these reports relate to issues that are clearly disputed and must be treated with care. At authorization, they cannot be used to resolve contested facts or to displace the presumption of truthfulness accorded to the applicants’ allegations. The actual determination of how many service disruptions occurred, for how long and with what causes and impact is reserved for the merits stage, if the class action is eventually authorized.

Admission of the customer agreement, service level agreement and incident-readiness webpage

The court next considers the contractual documents Microsoft wishes to introduce: the standard Microsoft Customer Agreement and the Microsoft Online Services Service Level Agreement. In its view, these contracts are central to the legal relationship between Microsoft Corporation and its customers, including the applicants, and are therefore “essential” for assessing the colour of right under article 575 paragraph 2 CCP. The applicants themselves allege contractual obligations by Microsoft but provide no written contract in support. Admitting these agreements at authorization fills that lacuna and allows the court to have at least an outline of the legal framework—such as which Microsoft entity is actually a contracting party and whether the obligations look more like obligations of diligence than strict result or warranty. The judgment does not reproduce or interpret specific clauses in detail at this stage; rather, it recognizes that their existence and structure are relevant to the viability of the proposed cause of action and class definition. The Microsoft Azure “Incident Readiness” webpage is also admitted as a separate exhibit. This public-facing document advises customers about the possibility of service disruptions and suggests steps they can take to monitor service issues and mitigate negative impacts. For the court, such a document bears on whether the applicants can plausibly argue that Microsoft undertook an obligation of result or warranty regarding uninterrupted service, or whether its commitments are better characterized as obligations of diligence. That characterization will matter later when analyzing breach and contractual liability, but at authorization, the webpage simply supports the court’s preliminary view that there is a concrete contractual context in which the applicants’ legal theory must be assessed.

Cross-examination of Microsoft’s witness

On the procedural front, the applicants seek to examine Mr. Ziock on his sworn statement for 60 minutes. Article 105 CCP allows an affidavit’s author to be examined on the facts attested to, and in an individual action such an examination is typically a matter of right. But in the class action context, Quebec case law is divided: some decisions hold that cross-examination on affidavits at authorization is not automatic and must be controlled by the court in light of proportionality; others recognize a right to examine but emphasize that it is limited to verifying the seriousness of the facts set out in the statement. This judgment does not definitively resolve that doctrinal debate. Instead, it adopts a pragmatic middle ground consistent with the adversarial principle and proportionality. The court authorizes an oral examination of Mr. Ziock solely on those paragraphs of his statement that are being admitted into evidence—namely the introductory and role-defining paragraphs and the portions dealing with the existence and identity of the contractual arrangements. The examination is capped at 45 minutes (rather than the requested 60 minutes) and must occur no later than 31 March 2026. The court also specifies that, if an examination takes place, the transcript will be added to the court record. This approach allows the applicants to test the seriousness and clarity of the limited factual assertions being relied on, while preventing the examination from expanding into a broad merits-style cross-examination on disputed outage details.

Outcome of the application and status of the overall case

In the operative part of the judgment, the Superior Court grants Microsoft Corporation and Microsoft Canada Inc.’s application for leave to adduce relevant evidence in part. The defendants are authorized to file a restricted version of Mr. Ziock’s sworn statement containing only specified neutral paragraphs and to introduce the two Microsoft 365 post-incident reports, the Microsoft Customer Agreement and the Service Level Agreement as exhibits supporting that statement. The Microsoft Azure Incident Readiness webpage is also admitted as a standalone exhibit. The applicants are granted the right to examine Mr. Ziock on the admitted paragraphs of his statement, subject to a 45-minute time limit and a deadline for holding the examination. The court orders that any examination transcript will form part of the record, and it directs that costs will follow the event at a later stage. Substantively, this judgment does not decide whether the class action will be authorized, nor does it resolve liability or quantum of damages. It is an interlocutory procedural ruling that defines what evidence may be considered at the upcoming authorization hearing and how the parties may test that evidence. On this application, the successful party is effectively the defendants, Microsoft Corporation and Microsoft Canada Inc., who obtain partial leave to file the evidence they wanted, though subject to judicial pruning. No damages, indemnity or quantified costs are awarded in this ruling, and the total monetary amount in favour of any party cannot be determined from this decision alone, as costs are explicitly left “to follow” and the merits of the action (including any potential class-wide damages) remain to be decided at a later stage.