A decade ago, Microsoft’s then-CEO Steve Ballmer famously branded Linux a “cancer that attaches itself in an intellectual property sense to everything it touches.” Today, the same company not only relies on Linux to power its Azure cloud – where over half of workloads are Linux-based – but also ranks among the most active corporate contributors to the Linux kernel. The transformation from open source archenemy to open source champion is one of the most remarkable strategic pivots in tech history. Yet for all the genuine goodwill, corporate contributions, and developer goodwill the shift has generated, Microsoft’s embrace of open source comes with an asterisk – one that Windows enthusiasts, in particular, should understand.

From Hostility to Heart-Eyes: The Pragmatic Pivot

Microsoft’s open source journey didn’t begin with altruism. In the early 2000s, the company waged legal and marketing wars against Linux and open source software, arguing that the GPL license was a threat to intellectual property. The infamous “Halloween Documents” of 1998 laid out a strategy of “embrace, extend, and extinguish” to deal with open source competitors. The company’s posture was monolithic: Windows and proprietary software were the foundation, and everything else was a threat.

Satya Nadella’s appointment as CEO in February 2014 marked the tectonic shift. At his first major public event as CEO, Nadella declared “Microsoft ❤️ Linux,” a phrase that would have been unthinkable under Ballmer. The reason was business, not philosophy. Cloud computing had upended the IT landscape, and the data center was no longer a Windows-only domain. Azure needed to run Linux workloads to be competitive with Amazon Web Services, where Linux dominated. Moreover, a new generation of developers were building on open source stacks – Node.js, Python, Ruby, and containers – often on MacBooks and Linux desktops. If Microsoft wanted to court these developers, it needed them to build for Azure, and that meant meeting them in their open source world.

Key Milestones of the Open Source Era

The pivot unfolded through a series of high-profile moves, each carefully calibrated to win developer trust and drive platform adoption.

  • .NET Goes Open Source (2014–2016): In November 2014, Microsoft open-sourced the .NET Core runtime and libraries, a radical departure from the proprietary .NET Framework. By 2016, .NET Core was fully open, cross-platform, and supported by the .NET Foundation, an independent open source organization. This allowed developers to build and deploy .NET applications on Linux and macOS, directly feeding into Azure’s container and microservice ambitions.

  • Visual Studio Code Arrives (2015): A lightweight, open source code editor built on GitHub’s Electron framework, VS Code quickly became the most popular development environment globally. Its open source core is freely available, but the “Microsoft distribution” adds proprietary telemetry and marketplace integration. This “open core” model would become a pattern.

  • Windows Subsystem for Linux (WSL) Launches (2016): In an astonishing reversal, Microsoft built a full Linux kernel compatibility layer into Windows 10. WSL gave developers native Linux command-line tools, package managers, and file system access directly inside Windows. WSL 2, released in 2019, shipped an actual Linux kernel, maintained by Microsoft, that runs with near-native performance via a lightweight VM. Today, WSL is indispensable for millions of developers who prefer Windows hardware but need Linux environments.

  • Acquisition of GitHub (2018): The $7.5 billion purchase of the world’s largest open source code repository signaled Microsoft’s ultimate embrace. Under Microsoft, GitHub has grown to over 100 million developers, introduced Copilot (an AI pair programmer), and maintained its status as the home of open source. Skeptics worried Microsoft would ruin GitHub; instead, it largely kept the platform independent and free for public repositories.

  • Windows Terminal and PowerToys (2019–present): Both are open source, community-driven projects that exemplify Microsoft’s new transparency. Windows Terminal became the go-to command-line tool, and PowerToys revived beloved Power User utilities – all developed in the open on GitHub.

  • Azure Linux (2023): Microsoft’s own internally developed Linux distribution, originally called CBL-Mariner, now ships as the container host OS for Azure Kubernetes Service (AKS) and other services. This isn’t a desktop distribution but a minimal, hardened OS designed to give Microsoft full control over its cloud infrastructure stack.

Real Developer Benefits: A Windows Renaissance

For Windows enthusiasts, Microsoft’s open source turn has been transformative. The operating system, once derided as a walled garden for enterprise line-of-business apps, has become a first-class development platform for modern open source workflows. WSL 2 brings real Linux kernels (currently 5.15 LTS and later) with seamless integration: files are accessible from both OSes, networking is shared, and even Docker containers run natively without a separate VM. VS Code’s Remote – WSL extension lets developers code against a Linux environment from within Windows with full IntelliSense and debugging.

Beyond WSL, the open sourcing of .NET and the creation of cross-platform PowerShell (PowerShell Core) meant that Windows administrators and developers could finally escape the clutches of proprietary scripting. PowerShell 7, built on .NET, runs on Windows, macOS, and Linux, enabling unified automation across environments.

Even the Windows kernel itself has benefited. Microsoft’s contributions to the Linux kernel – especially around hypervisors, networking, and memory management – have been substantial. The company is one of the top five corporate contributors, driven by the need to optimize Linux for Azure and Hyper-V.

The Asterisk: Open Source as Strategy, Not Ideology

Yet for all these wins, Microsoft’s open source philosophy is decidedly selective. The asterisk that accompanies every announcement is a reminder that the company’s primary allegiance is to its commercial interests, not the open source ethos. This nuance is critical to understanding the real state of play.

The Windows Core Stays Closed
The Windows operating system itself – its kernel, compositor, shell, and first-party apps – remains entirely proprietary. While components like Windows Terminal and PowerToys are open, the deep plumbing that makes Windows Windows is locked away. And with Windows 11, the integration of Microsoft services (OneDrive, Microsoft 365, Edge) has tightened, creating a platform that is increasingly ad-supported and subscription-driven. Open source contributions around Windows are limited to personalization projects like Start11 or community themes, but Microsoft has actively blocked third-party theme engines, citing security and compatibility.

Open Core, with Proprietary Extensions
Many of Microsoft’s most celebrated “open source” projects follow an open core model. Visual Studio Code is open source, but the official binary includes Microsoft proprietary telemetry and marketplaces. GitHub Copilot, whose underlying AI model is trained on public repositories, is a paid subscription service. Even .NET, while open, has a free tier (community) and paid versions (Professional, Enterprise) for Visual Studio’s full IDE. The open parts serve as a funnel to Azure, GitHub Enterprise, and Visual Studio subscriptions.

Embrace, Extend, Profit?
Some critics see echoes of the old “embrace, extend, extinguish” playbook. Microsoft has not killed open source, but it has extended it into its ecosystem, making it hard to leave. Companies that adopt Azure DevOps, GitHub Actions, and Azure Active Directory benefit from deep integration, but they also become more locked into the Microsoft cloud. And when Microsoft open-sourced the open-source .NET platform but kept the high-margin Visual Studio IDE proprietary, it captured a massive community of C# developers while still monetizing the tooling.

The OMI Saga
In 2021, the security community unearthed a series of critical vulnerabilities in Open Management Infrastructure (OMI), a Microsoft-developed open source agent silently embedded in Azure services and even on some Linux distributions. The saga highlighted a darker side: Microsoft leveraged open source code widely, but delayed patching and transparency when bugs emerged. The incident soured some Linux administrators who felt they were unwittingly running Microsoft code with insufficient oversight.

The Windows Enthusiast’s Dilemma

For devoted Windows users and IT pros, the open source shift is mostly positive. WSL 2 is a genuine superpower, allowing them to run Ubuntu, Debian, or custom distros with full systemd support alongside Windows apps. Windows Terminal is arguably the best terminal emulator on any platform. And the fact that Microsoft contributes to the Linux kernel means that Windows-native hypervisors like Hyper-V perform better with guest Linux VMs.

But there is an underlying tension. The Windows desktop experience is becoming increasingly locked down, with mandatory Microsoft accounts, hardware TPM requirements, and gradual erosion of local account options. The same company that gives away VS Code for free also serves up ads in the Start menu and collects telemetry that privacy-conscious users find invasive. And while Microsoft champions open source development, the code that runs Windows Search, the Windows Update engine, and the Windows Security model remains a black box.

The Community’s Verdict: Cautious Optimism

Developer and IT communities have largely embraced Microsoft’s tools while maintaining a healthy skepticism. GitHub stars and VS Code extension downloads speak to adoption; debates on Reddit and Hacker News reflect the ongoing wariness. Many point out that Microsoft’s open source tendencies are purely transactional. You get a great set of tools in exchange for your telemetry and, eventually, your Azure subscription.

And yet, that transaction is delivering real value. The .NET Foundation has produced mature, enterprise-grade frameworks that rival or surpass those from Oracle and Red Hat. Azure Kubernetes Service is a leading managed Kubernetes platform, built on a foundation of open source projects. Microsoft’s acquisition of GitHub has not destroyed the platform; it has instead poured resources into improving it, including making infrastructure contributions to all repositories through the GitHub Archive Program.

What’s Next: Open or Closed, the Strategy Continues

Microsoft’s open source arc is not yet complete. The company continues to release tools like Microsoft Dev Box (cloud-based developer workstations) and improve WSL with features like Linux GUI app support and USB device passthrough. The Windows Subsystem for Android, while not open source, shows how Microsoft is willing to incorporate an entire Linux-based runtime (Android uses a Linux kernel) to enrich Windows.

On the flip side, the push for AI integration in Windows – through Copilot, Recall, and cloud-based AI features – will likely remain proprietary, and may deepen the data collection many users resent. The tension between open source collaboration and proprietary platform lock-in will only intensify.

For Windows enthusiasts, the bottom line is this: enjoy the fruits of Microsoft’s open source strategy – the remarkable developer tools, the Linux kernel inside your OS, the sense that Windows is finally part of the broader software community – but keep your eyes open. The asterisk isn’t going anywhere. It’s the fine print of a pragmatic, profit-driven conversion that has, so far, made Windows a much better place to code and compute.