For years, Microsoft has quietly relied on its own Linux distribution behind the scenes.
Most Azure customers never noticed it. The operating system, originally known as CBL-Mariner and later renamed Azure Linux, has powered parts of Microsoft’s cloud infrastructure, Kubernetes services, and internal platforms without attracting much attention.
Now that’s changing.
Microsoft has officially opened Azure Linux 4.0 for public testing, allowing customers to deploy and evaluate the distribution on Azure before its general release. While it may sound like just another version update, Azure Linux 4.0 represents one of the biggest changes in the project’s history: a move to a Fedora-based foundation while continuing Microsoft’s focus on security, performance, and cloud optimization.
To understand why this matters, it helps to look at where Azure Linux came from.
Back in 2020, Microsoft introduced CBL-Mariner, a lightweight Linux distribution designed specifically for internal cloud infrastructure. Unlike Ubuntu, Debian, or Red Hat Enterprise Linux, it wasn’t intended to compete as a general-purpose operating system. Instead, it was built to provide a secure and consistent platform for Azure services and cloud-native workloads.
As Azure continued to grow, so did the importance of the project. CBL-Mariner eventually became the foundation for various Azure services, container hosts, and Kubernetes environments. In 2023, Microsoft renamed it Azure Linux, making its purpose much clearer and signaling its long-term role within the Azure ecosystem.
With Azure Linux 4.0, Microsoft is taking another major step forward.
What’s New in Azure Linux 4.0
| Component | Version | What Changed |
| Kernel | 6.18 LTS | Azure-tuned with new hardware drivers, improved Hyper-V integration, GPU/AI accelerator support |
| Package Manager | dnf5 | Complete rewrite from python to reduce dependencies, faster package resolution, lower memory usage |
| glibc | 2.42 | This includes performance improvements in string ops, memory allocation, thread handling |
| OpenSSL | 3.5 | This release includes post-quantum cryptography support, improved QUIC support, and other crypto updates. |
| systemd | 258 | Faster boot sequences, improved service management |
| Python | 3.14 | JIT compiler, new syntax features |
| RPM | 6.0 | Modernized database backend, improved signature verification |
| FIPS 140-3 | In progress | Will be available at GA. |
The most significant change is its adoption of a Fedora-based package ecosystem. For Linux administrators, this is an important shift. Fedora is widely known as an innovation platform where many technologies are developed and refined before eventually appearing in enterprise Linux distributions.
See also: Mastering the Linux Command Line — Your Complete Free Training Guide
By building Azure Linux 4.0 on a Fedora foundation, Microsoft gains access to a modern package ecosystem, newer software versions, and stronger alignment with upstream open-source development. At the same time, Microsoft continues to maintain its own repositories, security hardening, kernel optimizations, and Azure-specific integrations.
This doesn’t mean Azure Linux suddenly becomes Fedora. Rather, it combines Fedora’s modern software ecosystem with Microsoft’s cloud-focused engineering approach.
Security remains a central focus as well.
Modern cloud environments require operating systems that are small, predictable, and easy to maintain. Every unnecessary package can increase the attack surface. Azure Linux follows the same philosophy that originally guided CBL-Mariner: provide only what cloud workloads need while minimizing complexity.
The result is a distribution designed around secure defaults, regular security updates, and optimized performance for Azure-hosted workloads.
A common question is why Microsoft built its own Linux distribution instead of relying entirely on Ubuntu or Red Hat Enterprise Linux.
The answer comes down to control and consistency.
Running one of the world’s largest cloud platforms requires a highly standardized operating environment. By maintaining its own distribution, Microsoft can control package lifecycles, optimize system components for Azure, accelerate feature integration, and ensure consistent behavior across services.
This approach is not unique. Amazon has Amazon Linux, and Google maintains several specialized Linux platforms for its cloud infrastructure. As cloud providers continue to scale, many prefer operating systems tailored specifically to their environments.
For Azure customers, Azure Linux 4.0 is unlikely to replace every Linux deployment overnight. Popular distributions such as Ubuntu, Red Hat Enterprise Linux, SUSE, and Debian will remain important options on Azure.
However, Azure Linux may become increasingly attractive for organizations that are heavily invested in Azure services, containers, and Kubernetes. Because it is built and maintained by Microsoft, it has the potential to deliver tighter Azure integration, optimized cloud images, and a more consistent experience across Microsoft’s cloud ecosystem.
Perhaps the most interesting aspect of Azure Linux 4.0 is what it says about the broader technology industry.
Two decades ago, the idea of Microsoft developing and promoting its own Linux distribution would have sounded unlikely. Today, Linux plays a critical role throughout Azure, and Microsoft has become a major participant in the open-source ecosystem.
Azure Linux 4.0 reflects that transformation. It demonstrates how Linux has become an essential foundation of modern cloud computing, regardless of who operates the infrastructure.
While Azure Linux 4.0 may not generate the same headlines as a major desktop release, it represents an important milestone in Microsoft’s cloud strategy. The move to a Fedora-based foundation shows a commitment to staying closely aligned with the open-source community while continuing to build a platform optimized for Azure.
For Linux administrators, cloud architects, and Azure users, the public preview offers an early look at the future of Microsoft’s Linux platform—and perhaps a glimpse into how cloud operating systems will continue to evolve in the years ahead.
