The events of Thursday 12 and Friday 13 November have once again exposed just how vulnerable our digital infrastructure can be when one of the world's largest technology providers experiences disruption.
It raises a much bigger question: Have we become so dependent on Microsoft that we can no longer function effectively without it?
On Thursday, users across the world began reporting difficulties accessing Microsoft 365 services, including Outlook and Teams. These are not niche applications. They are fundamental communication and collaboration tools used by hundreds of millions of people worldwide.
Microsoft attributed the disruption to what it described as "elevated load" on its infrastructure, rather than a cybersecurity breach. However, the precise cause of the incident was not immediately clear.
More than 20 hours after the problems began, Microsoft reported "encouraging progress", with email queues approaching normal levels. But by then, the consequences were already being felt far beyond the inconvenience of not being able to send an email or join a Teams meeting.
The impact: When digital infrastructure stops working
In the UK, the disruption had implications for organisations and public services that depend on Microsoft technology every day.
Schools urged parents to make contact by telephone rather than email.
The GMB union reported a serious impact across ambulance services and NHS trusts.
Some court cases were delayed because of the disruption.
Internationally, the effects were equally significant. Hospitals and rail passengers in Canada experienced disruption, court services in the United States were affected, and delegates attending the COP31 climate conference in Turkey encountered difficulties accessing important documents.
Cybersecurity expert Jake Moore described the scale of the impact as "absolutely massive", highlighting the fact that Microsoft software sits at the heart of so many businesses and organisations.
The problem wasn't simply that people couldn't access their emails. It was that organisations which have built their everyday operations around a single technology ecosystem suddenly found themselves unable to operate as normal.
When the infrastructure we depend on stops working, how much of our world stops with it?
Understanding the dependency: What is .NET?
To understand how Microsoft has become so deeply embedded in the digital landscape, we need to look beyond the applications we use every day and examine some of the technology that sits underneath them.
One important part of that story is .NET.
In simple terms, .NET is a software development platform created by Microsoft. It provides developers with the tools, libraries and runtime environment needed to build applications, websites, business systems and services. It supports programming languages such as C# and F#, allowing developers to create software that can interact with other systems and operate across different environments.
Microsoft first introduced the .NET vision around the turn of the millennium, positioning it as a way to simplify software development and make applications work together more effectively.
As businesses increasingly moved towards interconnected digital systems, developers needed common frameworks and technologies that would allow different applications to communicate, share information and operate together.
Over time, it helped establish a substantial ecosystem of applications, enterprise systems and development tools, many of which became closely associated with Microsoft's wider technology offering.
From proprietary technology to open source: Microsoft's strategic pivot
For much of its early life, .NET was closely tied to Microsoft's own ecosystem. The original .NET Framework was proprietary, Windows-focused and heavily integrated with Microsoft's development tools and server technologies. For developers, this created a degree of dependency.
Building applications using .NET often meant working within the Microsoft environment, using Windows servers, Internet Information Services (IIS) and development tools such as Visual Studio.
There were attempts to break away from this dependency. The Mono project, for example, sought to bring .NET capabilities to Linux and macOS, giving developers more flexibility outside the Windows environment.
Cloud computing was gathering momentum. Linux was becoming increasingly important. Businesses were embracing containerisation, distributed systems and platforms that could operate across multiple environments. Microsofts traditional Windows-centric approach risked becoming a limitation in a world where flexibility and interoperability were becoming essential.
The open-source pivot: .NET Core (2014–2019)
Under CEO Satya Nadella, Microsoft began a significant shift in its approach.
In 2014, the company announced .NET Core, an ambitious move towards a modular, open-source and cross-platform version of the .NET platform.
The objective was to allow developers to build and run applications across Windows, Linux and macOS.
Microsoft was effectively opening up a technology that had previously been closely controlled within its own ecosystem.
The company also embraced a more collaborative development model through the .NET Foundation, encouraging wider community involvement and contributions. Alongside this, Microsoft's acquisition of Xamarin helped bring together different strands of its development ecosystem, particularly around mobile applications. By 2019, .NET Core had become an established alternative to the original Windows-focused framework.
The message was clear: Microsoft was no longer simply trying to keep developers within Windows. It wanted to become an essential part of software development wherever that development took place.
Open source doesn't necessarily mean independence
Today, .NET is open source. Developers can use it without purchasing proprietary Microsoft licences, and applications can run on Linux servers, cloud infrastructure and other platforms. On the surface, this suggests that the dependency has been broken.
However there is an important distinction between having access to technology and having control over the direction that technology takes as Microsoft remains the dominant force behind the .NET ecosystem. It continues to invest heavily in its development, employs many of the engineers responsible for its evolution and plays a central role in determining its future direction.
Lets look into this a bit further by reviewing:
1. The roadmap and direction
Microsoft continues to play the leading role in shaping the future of .NET, including major architectural decisions, language development and performance improvements.
2. The development environment
Although developers have alternatives such as Visual Studio Code and JetBrains Rider, Microsoft's own development tools remain central to the ecosystem.
3. Cloud integration
.NET is deeply integrated with Microsoft's Azure cloud platform. While it can run on competing cloud providers, the relationship between .NET and Azure creates a powerful commercial and technical ecosystem.
4. The wider technology ecosystem
When Microsoft changes its priorities, invests in new technologies or introduces new development approaches, the wider .NET community inevitably takes notice.The technology may be open, but the influence remains heavily concentrated.
So, are we actually dependent on Microsoft?
We are no longer technically dependent on Windows or proprietary Microsoft licences to develop and operate .NET applications. Organisations can deploy .NET applications on Linux, use alternative development environments and host their systems with competing cloud providers.
Microsoft remains a central force in the development, maintenance and evolution of the platform. And, more importantly, the applications and services we use every day increasingly sit within interconnected technology ecosystems. The recent Microsoft disruption illustrates the potential consequences of that concentration.
It demonstrates how an issue affecting one major technology provider can have a ripple effect across businesses, public services, healthcare, education and even international events.
This is not simply about Microsoft. The same questions could be asked of Amazon Web Services, Google Cloud and other providers whose infrastructure supports huge parts of the modern digital economy.
Cutting through the noise: The bigger question
Perhaps the most important lesson from this incident is not that Microsoft experienced an outage. Technology fails. Systems experience problems. Infrastructure is not infallible. The bigger issue is how little control many organisations have over their ability to continue operating when the platforms they depend on become unavailable.
Have we built resilience into our digital infrastructure, or have we simply become comfortable with convenience?
Are organisations maintaining meaningful alternatives, independent systems and contingency plans, or have they placed so much trust in a handful of technology providers that they have lost the ability to operate without them?
Because when the technology we rely on every day suddenly becomes unavailable, we are reminded of something rather uncomfortable:
We might own our data, run our businesses and make our decisions, but increasingly, the infrastructure that allows us to do all of those things belongs to somebody else.
And that is certainly something worth cutting through the noise about.