Microsoft Quietly Powers Half of Azure With Its Own Linux Distribution
TLDR
- Azure Linux 3.0 is Microsoft’s homegrown distribution — 100% OSI-approved open source
- Now ships as the default OS on roughly 60% of new Azure Kubernetes Service nodes
- Free for Azure customers, with no extra licence fee
- Built specifically for AKS, container hosts and Azure VMs
- Azure Linux 2.0 reaches end-of-life on 30 November 2025 — v3.0 migration window is now
- Latest release pulls in the Linux 6.12 LTS kernel, AppArmor and DMA P2P support
Microsoft’s Own Linux Quietly Runs the Cloud
The company that built its empire on Windows now builds one of the most widely deployed Linux distributions on the planet. Azure Linux — Microsoft’s homegrown, Azure-optimised distribution — has grown from a quiet internal project into the default operating system running a large slice of the company’s cloud. If you have spun up an Azure Kubernetes Service (AKS) cluster recently, there is a strong chance you were running it on Azure Linux without even realising.
What makes this story more than a curiosity is the scope of the deployment. Azure Linux is the foundation under Azure Container Host (the new container-optimised OS for AKS), the default option for fresh Azure VMs that prioritise security and lighter footprint, and increasingly the runtime of choice for AI workloads shipped through Azure infrastructure. Microsoft has packaged the entire stack as fully open source under OSI-approved licences, with the public repository hosted at github.com/microsoft/azurelinux and visible to anyone curious enough to inspect the build.
Why Microsoft Built Its Own Linux
Linux distributions in 2026 have largely converged — Ubuntu, RHEL, SUSE and Debian cover most enterprise needs. So why build a new one from scratch? The short answer is that cloud-native workloads look nothing like the desktop or server workloads those distros were designed for. A general Linux tries to support every conceivable use case at the cost of bloat, attack surface and slower updates. Azure Linux removes everything that isn’t directly relevant to running Azure workloads — containers, Kubernetes nodes, GPU-pass-through hosts — and bundles a tighter, more auditable result.
The result is measurable. Cold-start times on Azure Linux node pools are noticeably faster than equivalent Ubuntu deployments, and the image includes Microsoft’s hardened kernel configuration tuned for CPU and GPU SKU variation on Azure hardware. The October 2025 release (3.0.20251021) introduced AppArmor components by default, enabled DMA peer-to-peer for GPU-accelerated workloads, and brought the Linux 6.12 LTS kernel to production.
Free for Customers, Cheap for Microsoft
Azure Linux carries no additional licence fee for Azure customers. The OS ships with the platform cost bundled into the underlying compute, which means a Windows-style surcharge is not part of the picture. For cost-conscious teams running many small AKS node pools, that pricing structure tilts the comparison decisively in Azure Linux’s favour.
Microsoft’s internal economics also work in its favour: owning the OS layer lets the company trim unnecessary middleware, push security fixes faster, and tie the OS update cadence directly to Azure feature releases. That kind of vertical integration is rare in the Linux ecosystem, where most distros must reconcile upstream release cycles with downstream enterprise expectations.
Where This Matters Most for Builders
The biggest practical impact today is on AKS migrations and new cluster builds. About 60% of newly created AKS node pools now run on Azure Linux by default, and Microsoft is pushing strongly toward v3.0 adoption. Developers building AI inference pipelines on AKS — particularly those pulling in PyTorch or running GPU pools — benefit from the optimised kernel and prebuilt NVIDIA/Azure container images. Teams running older Azure Linux 2.0 node images need to plan the jump soon, because Microsoft officially ends support for v2.0 on 30 November 2025.
For sysadmins, the day-to-day operations story is simpler than one might expect. Azure Linux uses standard dnf/rpm tooling, exposes standard Kubernetes artefacts, and ships an immutable image variant (Azure Container Linux) where the entire OS is rebuilt each release rather than patched in place. That makes blue/green cluster upgrades safer than the traditional rolling-update model, especially for regulated workloads that demand clear audit trails.
Our Take
What Microsoft has quietly built with Azure Linux is a serious piece of cloud infrastructure — not a press-release vanity project. By making the distribution open source, free to Azure customers, and tightly integrated with AKS, the company has turned a would-be lock-in concern (“now you’re relying on Microsoft’s custom Linux”) into a competitive advantage (“our cloud Linux is faster, leaner and easier to patch than the off-the-shelf alternatives”).
For developers, the real takeaway is that the default OS on a new AKS cluster is increasingly Microsoft-blessed and tuned for the hardware you’ll actually be running on. If you have been writing container manifests and Helm charts against generic Linux assumptions, it is worth a quick audit of the layers below. The shift to Azure Linux on AKS isn’t a hype story — it is the new baseline, and it is already running in production.
Keyword: Azure Linux 3.0
