A cause before the report

Microsoft has not yet published its root cause. The Independent prints the company’s own promise that “once mitigated, we will provide full details of the root cause […] within a post-incident Report” [6]. Even so, by Friday the coverage had settled the question in its own voice.

BBC News says the disruption “was caused byCertainty upgradeA certainty upgrade restates a source's claim in the outlet's own voice more firmly than the source made it: a hedge, a limit or a caveat in the original disappears in the retelling. routine automated checks that took some servers offline, overloading the remaining ones with traffic” [4]. That is Microsoft’s working account, and it may turn out to be correct. But on Thursday Microsoft itself said only that elevated load was “likely contributing to the connectivity errors”, and NPR added that “it was not immediately clear what exactly caused that failure” [9]. The step from the company’s “likely” to the BBC’s “was caused by” is a certainty upgrade: the reader gets a conclusion with no source on it, and the hedge that showed the investigation was still open is gone. To spot it, compare the verb in the narration with the verb in the quote it relies on.

A certainty upgrade restates a source's claim in the outlet's own voice more firmly than the source made it: a hedge, a limit or a caveat in the original disappears in the retelling.

The cause also shifted from day to day, and no outlet notes the shift. Early on 13 November the Guardian’s summary said the outage “appears to be sparked by an update issue” [8]. The source for that was Tony Burke’s second-hand report that Microsoft believed it was dealing “in some ways similar to what we saw with respect to CrowdStrike, where there is an update that has that has gone awry” [8]. An analogy passed along by a minister became a cause. CBS News still runs the same Burke quote, followed by a full paragraph on how CrowdStrike’s bug “grounded flights, took TV broadcasts off the air” [1], while the BBC has moved on to automated checks [4]. The Independent quotes a Microsoft fix involving an “upstream authentication/routing configuration component patch” [6]. That fits Microsoft’s statement that a process setting up secure connections on its servers became overwhelmed [10]. So readers get three possible explanations (a bad update, health checks, an authentication component), and no article says which is confirmed or whether they are compatible.

The Independent goes further: “Experts across the security industry are stressingProof by invocationProof by invocation cites a report, a study or unnamed experts as having shown something, without giving a single figure, name or finding from them, so the reader can only take the conclusion on trust.” that the outage was “a mistake by Microsoft itself” [6]. No expert is named or quoted. This is proof by invocation: a verdict of fault arrives on the authority of a crowd the reader cannot check. When “experts” are plural and nameless, ask why none of them was quoted.

Proof by invocation cites a report, a study or unnamed experts as having shown something, without giving a single figure, name or finding from them, so the reader can only take the conclusion on trust.

What the coverage did not do

Online, people joked that Microsoft had cut staff in favour of AI and this was the result. They also posted Friday the 13th memes and “Microsoft 364” puns [10]. None of the articles here presents the job-cuts or AI-code theory as fact, and none rules it out as fact either. The Mirror repeats only the brand jokes from Sainsbury’s and Aldi [5]. The BBC’s AI strategist talks about the future, saying “a failure like this may spread even further” once assistants are plugged into email [4], not about the cause. On this point the coverage held its line. The problem lies elsewhere.

Chaos in the headline, calm in the body

The Independent’s headline says “Microsoft outage sparks chaosHeadline asserts, body hedgesThe mother pattern behind scare quotes, modal deletion, and the commitment-free statement: a headline states a claim as settled fact while the article underneath it quietly hedges, denies, or contradicts it. across NHS, police and schools” [6]. Its subhead adds that it “affected 999 calls for the NHS” [6]. The body tells a different story. The GMB union’s own words are that the backlog “has the potential for chaos” and that “emergency and life-threatening call-outs appear to be unaffected” [6]. Leeds Teaching Hospitals says “our clinical systems are not affected” [6], and Guy’s and St Thomas’ says procedures are “going ahead as planned” [6]. This is headline asserts, body hedges: a reader who skims the headline comes away believing emergency care failed, which the article’s own sources deny. The narration also turns the union’s “potential” into fact when it says the outage “caused chaos in NHS hospitals” [6], the same move as the BBC’s cause sentence.

The mother pattern behind scare quotes, modal deletion, and the commitment-free statement: a headline states a claim as settled fact while the article underneath it quietly hedges, denies, or contradicts it.

The Mirror’s headline does the same with “Microsoft Outlook outage chaos” [5], and the same article quotes the cyber minister reporting “limited reports of impact on frontline service delivery” [5]. Its two articles even disagree on scale. One says “Millions of its customers have been unable to send and receive emails” [3]. The other concedes “it is unclear how many were unable to use it” [5]. The Mirror’s pharmacy piece, to its credit, keeps its modal: patients “could” stay in hospital longer [3], and the pharmacist’s own explanation backs that up.

The fridge paragraph

Right after Microsoft’s statement that “we have no evidence of malicious activity”, the Mirror adds: “It comes after a number of high-profile cyber attacks, including hackers who seized control of supermarket fridges across Europe.Guilt by juxtapositionGuilt by juxtaposition places separate cases or facts side by side so the reader infers a link, a pattern or a cause the article never states, and so never has to prove.” [5]. Nothing links the fridges to Outlook. Placed there, the sentence lets the reader suspect a hack that the article itself never claims. That is guilt by juxtaposition. The test is whether the sentence would make any sense without the suggestion it plants.

Guilt by juxtaposition places separate cases or facts side by side so the reader infers a link, a pattern or a cause the article never states, and so never has to prove.

Promises printed in full

The Mirror runs the cyber minister’s statement at length: “The Government recognises this incident has been inconvenient and disruptiveCommitment-free statementA commitment-free statement is an institutional quote that concedes a problem in feeling-language while specifying no agent, no deadline, and no way to check later whether it happened.” and “We will review this incident and the lessons learned” [5]. There is no date, no named reviewer and no published output that readers could check later. This is a commitment-free statement, and no follow-up question is printed after it. The BBC handles Microsoft’s side the same way: the company “said it was reviewing what went wrong” [4], with no date and no undertaking to publish.

A commitment-free statement is an institutional quote that concedes a problem in feeling-language while specifying no agent, no deadline, and no way to check later whether it happened.

“We” rely on tech

The BBC headline makes the outage a “‘stark reminder’ of how much we rely on tech” [4]. The sources inside that article say something narrower. Gergely Orosz points to “our reliance on a few large US corporations” [4], and Dame Chi Onwurah, quoted by the Mirror, says the UK “is hugely dependent on a small number of US-based technology providers for our public services” [5]. “Tech” in general did not fail; one supplier did, chosen by named public bodies. The wider phrasing in the headline makes a procurement decision sound like a fact of modern life, which nobody decided and nobody can be asked about.

What a reader would need instead

4 checks to run on the next story like this one.

  1. Clear labels on which cause is Microsoft’s confirmed finding and which is a working hypothesis, until the post-incident report is out, plus a commitment to compare that report with Friday’s headlines.

    Certainty upgrade

  2. The context France 24 gave on 12 November and later coverage dropped: “Il s’agit de la deuxième perturbation des services Microsoft 365 cette année” (this is the second disruption of Microsoft 365 services this year) [7].

    Gap in the coverage

  3. Some account of who signed the contracts: which NHS bodies, departments and parliaments chose a single provider, on what resilience terms, and whether Onwurah’s Science and Technology Committee report [5] got a government response.

    Gap in the coverage

  4. Real figures on frontline impact from NHS England and the police, not “chaos” in the headline and “unaffected” in the body.

    Headline asserts, body hedges