Microsoft is officially rolling out Azure Linux 4.0, a free, open-source distribution engineered exclusively for cloud servers and containers. Twenty-five years after the company's leadership famously dismissed open-source software, Microsoft is now shipping its own Fedora-derived operating system to the public.
Linux is a cancer that attaches itself in an intellectual property sense to everything it touches.
- Steve Ballmer, Microsoft
The operating system is not a sudden experiment. It has been quietly powering Microsoft’s internal infrastructure for years, handling massive production workloads for AKS (Azure Kubernetes Service), Azure SQL, and Azure Cosmos DB. Now, following its public preview launch at Build 2026 on June 2, it is available for anyone to deploy on Azure VMs and VM Scale Sets.
From Internal Tool to Version 4.0
Azure Linux originally began in 2019 as an internal project named CBL-Mariner (Common Base Linux Mariner). By 2022, it had proven its stability at an enterprise scale. LinkedIn successfully migrated its entire infrastructure to Azure Linux 3, while Databricks transitioned over 100,000 VMs and more than a million CPU cores to the OS with zero customer-facing incidents.
Officially announced at the Open Source Summit North America on May 18, 2026, Version 4.0 introduces a fundamental architectural shift. Instead of Microsoft engineers manually assembling every component from scratch, the new version is built as a set of declarative overlays on top of a Fedora 43 snapshot. Every deviation from the upstream source is fully documented in the public Azure Linux GitHub repository.
The update also replaces Microsoft's custom tdnf package manager with dnf5. This is the exact same package manager utilized by Fedora and Red Hat, offering faster dependency resolution, lower memory usage, and a predictable environment for administrators accustomed to the Red Hat ecosystem.
How Azure Linux 4.0 Compares to Ubuntu and RHEL
Azure Linux 4.0 is strictly a cloud-only distribution. It is not designed to replace general-purpose operating systems like Ubuntu or Fedora on a local laptop. The base image is aggressively stripped down to approximately 300 MB, omitting any graphical user interface, audio stack, or desktop environment.
Upon installation, users are dropped directly into a text-based console with Bash as the default shell. This minimal footprint is intentional: fewer packages mean a drastically reduced attack surface and fewer vulnerabilities requiring monthly patches. While running it outside of Azure is technically possible via an ISO file, Microsoft explicitly does not support on-premises or alternative cloud deployments.
| Feature | Azure Linux 4.0 | Ubuntu / Fedora / RHEL |
|---|---|---|
| Built for | Azure cloud workloads only | General use, any environment |
| Desktop or GUI | No | Yes |
| Runs outside its platform | No official support | Anywhere: cloud, bare metal, local |
| Base image size | ~300 MB | 500 - 600 MB+ |
| Cost | Free, no OS license | Free to paid (RHEL requires subscription) |
| Maintained by | Microsoft | Canonical / Red Hat / Community |
Under the Hood: The Technical Stack
The current public preview ships with a highly optimized technical stack tailored for Azure's infrastructure. The core is powered by Linux Kernel 6.18 LTS, which includes specific tuning for Hyper-V integration alongside robust GPU and AI accelerator support.
Security is a major focus for enterprise adoption. The distribution includes OpenSSL 3.5, which introduces post-quantum cryptography support covering the NIST-standardized CRYSTALS-Kyber and CRYSTALS-Dilithium algorithms. However, FIPS 140-3 certification remains in progress and will not be finalized until general availability later in 2026.
| Component | Version |
|---|---|
| Linux Kernel | 6.18 LTS |
| Package Manager | dnf5 |
| C Library (glibc) | 2.42 |
| Init System | systemd 258 |
| Python | 3.14 (with JIT compiler) |
| OpenSSL | 3.5 (post-quantum cryptography) |
Azure Container Linux: The Immutable Sibling
Alongside the standard distribution, Microsoft also launched Azure Container Linux at Build 2026. While it shares the same kernel and security update schedule, it serves a fundamentally different purpose as an immutable operating system designed specifically for Kubernetes nodes.
The OS is deployed as a read-only image. Administrators cannot install packages or modify settings on a running system. Instead, updates are applied by swapping out the entire OS image, complete with an automatic rollback mechanism if a failure occurs. This immutable variant has been quietly powering AKS since 2023 and is now available as a standalone product.
| Feature | Azure Linux 4.0 | Azure Container Linux |
|---|---|---|
| Primary use | General cloud servers and VMs | Kubernetes nodes and containers |
| Can you modify it | Yes, install packages freely | No, read-only OS image |
| How updates work | Package-by-package via dnf5 | Entire image swap with auto-rollback |
| Availability | Public preview | Generally available |
The Supply Chain Strategy Behind the Open Source Shift
Microsoft’s decision to build and distribute its own Linux OS is not just about performance; it is a calculated move to control the enterprise supply chain. Currently, Linux instances outnumber Windows Server instances on Azure. When a customer runs Red Hat on Azure, Microsoft provides the infrastructure, but Red Hat collects the lucrative support subscription revenue.
By offering Azure Linux, Microsoft is following the exact playbook used by Amazon with Amazon Linux and Google with Container-Optimized OS. If Microsoft can convince enterprise clients to standardize on Azure Linux, it gains end-to-end control over the entire stack. With every package cryptographically signed and Software Bill of Materials (SBOM) documents published for every release, Microsoft is positioning itself as the sole accountable vendor for highly regulated industries.
Furthermore, the upcoming integration with Windows Subsystem for Linux (WSL) will create a seamless developer pipeline. Developers will soon be able to build and test Linux containers locally using WSL, then deploy them directly to Azure Linux in production, entirely eliminating the environment mismatch problem without ever leaving the Windows ecosystem.
