Decoding the world of cybersecurity

Whitehall’s Microsoft reliance draws scrutiny

Ministers have acknowledged that almost all UK civil servants use Microsoft for communications, prompting questions about public sector resilience following the November Microsoft 365 outage.

Whitehall’s Microsoft reliance draws scrutiny
Summary
  • Minister Ian Murray said 98–99% of civil servants use Microsoft as their communications platform.
  • The Microsoft 365 disruption on 12–13 November affected businesses and public bodies, but was not attributed to a cyberattack.
  • MPs questioned supplier concentration, procurement, continuity arrangements, and the potential for diversification.

Almost all UK civil servants use Microsoft for workplace communications, a government minister has acknowledged, exposing the scale of Whitehall’s dependence on a single technology provider after a major outage disrupted services across the country.

During a House of Commons debate on 16 November 2026, minister Ian Murray said that 98–99% of civil servants use Microsoft as their communications platform. The figures emerged as MPs examined the consequences of disruption to Microsoft 365 services on 12 and 13 November and questioned the adequacy of contingency arrangements.

The outage affected businesses, public bodies and other users internationally. Parliamentary scrutiny concentrated on the extent to which essential activities had become dependent on interconnected commercial technology services and how those activities could continue during a substantial interruption.

The government said Microsoft had confirmed the incident was not an attack on its systems. The interruption was therefore a service resilience event rather than evidence of a cybersecurity intrusion, although many of the same continuity and dependency questions arise in both circumstances.

Government communications depend on shared infrastructure

Microsoft supplies widely used email, messaging, identity, document management and productivity services. Integration between these functions can improve administration and collaboration, but it also means that disruption to shared infrastructure may affect several activities simultaneously.

During the Commons debate, Murray acknowledged the limited diversification in government communications platforms while noting that some departments also use services supplied by Google.

The percentage he provided describes the prevalence of Microsoft communications services across the civil service. It should not be interpreted as proof that every department uses identical technology configurations or that all government services were unavailable during the outage.

Nevertheless, widespread reliance on one provider creates shared exposure. Departments may maintain separate internal systems yet still depend on common identity, email or collaboration infrastructure for ordinary operations.

Loss of email can delay correspondence and approvals, while disruption to document access and messaging services can interfere with coordination between teams. Where those systems support public services, the consequences may extend beyond internal inconvenience.

The government reported that major telecommunications services continued operating and that it had no evidence of wider disruption to UK data centre infrastructure or other cloud operators at that stage.

By Friday afternoon, Microsoft systems were returning to service. Ministers said officials had engaged the company and expected further information about how similar interruptions could be prevented or resolved more quickly.

Supplier concentration raises procurement questions

MPs used the incident to question whether government technology procurement had created excessive dependence on a small number of large suppliers.

The discussion included Microsoft’s position within public administration, the potential role of open source software and the difficulties of replacing established services.

Alternative products may reduce dependence on one provider, but diversification is not achieved simply by purchasing additional licences. Systems intended to provide resilience must continue operating when the primary service is unavailable and must remain accessible through independent supporting infrastructure.

For example, an emergency communications platform provides limited protection if its authentication relies entirely on the same identity service affected by the outage. Similarly, a secondary document repository may be inaccessible if its recovery credentials or administrative processes are tied to unavailable systems.

The structure of these dependencies makes resilience testing important. A continuity plan may describe alternative communications channels, but those arrangements need to be usable under the conditions in which they would actually be required.

Changing established platforms introduces operational costs. Departments may need to migrate records, maintain access controls, integrate security monitoring and retrain staff. Poorly managed transitions can create new weaknesses even when the long-term objective is to reduce concentration risk.

Public sector resilience involves contractual oversight

Digital service contracts commonly define availability commitments, support obligations and incident handling procedures. These arrangements can establish supplier responsibilities, but financial remedies after an outage do not restore access to essential services during the interruption itself.

Parliamentary questions also addressed whether Microsoft would provide sufficient technical explanations and whether government should seek stronger commitments regarding future resilience.

The government said its existing cyber and resilience programmes would examine dependencies and vendor lock-in. Those assessments may influence future procurement and continuity arrangements, although the debate did not establish a timetable for large-scale migration away from Microsoft.

Supplier concentration extends beyond workplace productivity platforms. Cloud hosting, telecommunications, identity services and managed technology providers can each become shared dependencies across organisations that otherwise have separate governance and operations.

The Microsoft outage gave Parliament a practical example of that exposure. It demonstrated that significant disruption can occur without a malicious intrusion, while the widespread use of one provider can complicate continuity across multiple organisations at the same time.

Further scrutiny will depend on the government’s review of the incident, its assessment of existing contingency arrangements and the information Microsoft provides about the failure and subsequent recovery.

×