A worldwide Microsoft 365 outage that began on Thursday evening and ran deep into Friday afternoon reached well beyond the businesses and commuters reporting it online: it knocked out email and other online services at Kent County Council, all four West Kent borough and district councils, and the NHS trust running Maidstone and Tunbridge Wells hospitals.
Kent County Council
KCC confirmed on its own website at 10.30am that the outage was "intermittently affecting" its systems, leaving it unable to send or receive emails, with knock-on effects for its website and Contact Centre. The council said it was implementing its Business Continuity Plans and using workarounds to keep services running while staying in close contact with Microsoft. By 4pm, KCC said "many services and systems are now operating normally," though it warned some inconsistencies remained across a small number of systems while work continued to resolve them.
Maidstone and Tunbridge Wells hospitals
Maidstone and Tunbridge Wells NHS Trust, which runs the two main hospitals serving West Kent, said it was also unable to send or receive emails because of the outage. The trust was clear that patient care wasn't affected: it told patients to continue attending appointments as planned without needing to call ahead, and said NHS 111 online and 999 services remained unaffected throughout. Anyone who urgently needed to contact a service about an imminent appointment was asked to phone rather than email.
All four borough and district councils affected too
Sevenoaks District Council, Tunbridge Wells Borough Council, Tonbridge and Malling Borough Council and Maidstone Borough Council each posted the same kind of warning across their own websites that day, telling residents they were aware of the Microsoft outage and that it was affecting some services, including the ability to send and receive emails - Maidstone's notice added that its phone lines were experiencing disruption too. None of the four reported any impact on statutory services like bin collections, benefits payments or planning deadlines, and all of the banners had been taken down by Saturday.
What went wrong, and how it ended
The outage began at around 5.53pm on Thursday 12 November, with Outlook failing to load or connect and some users unable to see new emails, and ran for nearly 20 hours before easing off through Friday afternoon - affecting police forces, NHS trusts, courts, schools and businesses across the South East and beyond. Microsoft confirmed full restoration on its official X account on Friday 13 November: "We are seeing broad recovery and stability across our services. This was a technical issue not related to cyber or AI / agents. The incident was introduced by an issue during an earlier network capacity upgrade that surfaced following a recent network change." In plain terms: a botched change to its own network capacity, not a cyber-attack.
How it compares to past outages
This wasn't a one-off. StatusGator, an independent service that tracks Microsoft's own status pages alongside user reports, counted 17 Microsoft 365 outages of varying severity since January 2025 - this one among them. But Thursday's stood out for how long it dragged on:
Duration of 2026's major Microsoft 365 outages
Microsoft 365 outages tracked since Jan 2025
17
This outage, vs the average of 2026's other 4 major ones
~10x longer
"Major" and durations per StatusGator's outage history for Microsoft 365 apps. Most of 2026's other major incidents were resolved within a few hours; this one ran close to 20.
Was this about AI?
With Copilot built into Microsoft 365 and AI features turning up in everything lately, it's a reasonable question - and Microsoft pre-empted it. Its statement was explicit: "this was a technical issue not related to cyber or AI / agents." The fault traced back to a change to its own network capacity, not artificial intelligence, a cyber-attack or user error. If anything, it's automated monitoring - not AI - that's already helping here: StatusGator says it detected several recent Microsoft 365 incidents, including September's worldwide Copilot disruption, ahead of any official Microsoft acknowledgement, purely from tracking status pages and user reports. Catching a problem fast and knowing what caused it, though, remain two different things - Microsoft's own investigation into Thursday's outage took the best part of a day.
What this means for you
If it happens again
- Keep turning up. MTW NHS Trust was explicit that hospital appointments carried on as normal; none of the councils or KCC reported any impact on statutory services like bin collections, benefits or planning deadlines either - the outage mainly hit email and some online forms.
- Phone rather than email if you need to reach a service urgently, as MTW NHS Trust and KCC both advised.
- 999 and NHS 111 run on separate, non-Microsoft systems, so they're not affected by an Outlook outage like this one.
- Check the service's own website or social media first - every local body affected this time posted its own update once it was affected.
Source:
Kent County Council. Contains public sector information licensed under the Open Government Licence v3.0. Also:
Maidstone and Tunbridge Wells NHS Trust; the four councils' own website notices (Sevenoaks District Council, Tunbridge Wells Borough Council, Tonbridge and Malling Borough Council and Maidstone Borough Council), since taken down;
Microsoft's official statement on X; and
StatusGator's Microsoft 365 outage history.