Is Microsoft Azure Linux aDistant Relative of Red Hat Linux?

When Microsoft announced Azure Linux 4.0 at the Open Source Summit North America in Minneapolis on May 18, 2026, the audience reaction was somewhere between laughter and disbelief. Jim Zemlin, CEO of the Linux Foundation, literally walked back onto the stage to ask Brendan Burns — co-founder of Kubernetes and VP of Azure’s cloud-native business — “Did you just announce that Microsoft is going to release a Linux distribution?” Burns replied simply: “Yes, that’s right.”

The shock was theatrical, but the technical story underneath was already weeks old for those who had been watching Azure Linux’s GitHub repository. There, one detail quietly answered the most interesting question: whose DNA runs through Microsoft’s new Linux?

The answer is Fedora’s. And Fedora, as any Linux administrator knows, is the upstream heartbeat of Red Hat Enterprise Linux.

The Family Tree: How Fedora Connects Microsoft and Red Hat

To understand the relationship, you need to understand how the Red Hat ecosystem works. Red Hat funds and steers Fedora as a community distribution — a fast-moving proving ground where new packages, kernels, and technologies are tested before being stabilized into Red Hat Enterprise Linux (RHEL). Fedora is, in essence, RHEL’s research lab.

Azure Linux 4.0 slots into this family tree as a direct Fedora derivative: it pulls packages from Fedora 43’s upstream repositories, applies targeted overlays for Azure-specific requirements, and uses the standard RPM toolchain — the same one that underpins every RHEL-family distribution. This means Azure Linux shares genuine technical ancestry with RHEL, even though Microsoft built and maintains it independently.

“Fedora is not merely a package source; it is the community distribution most closely associated with Red Hat’s enterprise Linux pipeline.”

What “Fedora-Based” Actually Means in Practice

Microsoft’s choice of Fedora was neither accidental nor purely ideological. Azure Linux 4.0 uses declarative TOML overlay files to document every deviation from Fedora’s defaults. Any package that diverges from upstream requires an explicit justification checked into the repository — meaning anyone can audit exactly what Microsoft changed and why. This is a meaningfully different philosophy from building a distribution from scratch.

The shift to dnf5 — the standard Fedora/RHEL package manager — is a pointed signal. Previous versions of Azure Linux used tdnf, a stripped-down package manager Microsoft built itself. Replacing it with the community-standard tool is, as one Hacker News commenter put it, a step back toward the commons: most company-internal platforms grow increasingly proprietary over time, but Microsoft is moving in the opposite direction.

However, “Fedora-based” emphatically does not mean “Fedora-compatible.” Gerard Braad, a principal software engineer who examined the distribution in depth, explicitly cautioned that Azure Linux’s minimal package footprint means dependency assumptions that hold on Fedora or a standard RHEL system may simply not exist in Azure Linux. If you migrate a workload from RHEL or Ubuntu and assume the dependency chain is intact, you will be surprised.

Red Hat Knows — and the Relationship Is Deliberately Diplomatic

The obvious question is: how does Red Hat feel about its upstream being used as the foundation for a Microsoft product? According to sources familiar with the matter, Red Hat was informed in advance. It would have been extraordinary if it had not been — Azure’s Linux ecosystem is deeply intertwined with Red Hat, Canonical, SUSE, and other distribution vendors, and Microsoft cannot afford to damage those partnerships.

Indeed, Microsoft has been careful to frame Azure Linux not as competition for Red Hat Enterprise Linux, but as a complementary, Azure-native option. In statements accompanying the launch, Microsoft emphasised that eight partner distributions remain officially certified on Azure, including RHEL. “You can run Red Hat or Ubuntu if you want,” a Microsoft product manager noted. “This just gives you an out-of-the-box native Azure option.”

Azure Linux vs. Amazon Linux: Same Ancestor, Different Philosophies

Microsoft is not the first hyperscaler to build its own Linux from Fedora ingredients. Amazon Linux 2023 is a blend of multiple Fedora versions and CentOS 9 Stream components, released in March 2023 with a two-year major release cadence and five years of long-term support per version. Amazon’s approach prioritises stability: version locking is on by default, and updates are controlled rather than automatic.

The practical implication: Microsoft is betting on a tighter relationship with the Fedora community as a strategic asset, while Amazon treats Fedora more as a raw material. Microsoft engineer Kyle Gospodnetich co-authored a proposal to build x86-64-v3 packages for Fedora 45 — a contribution motivated directly by Azure Linux’s performance needs on modern x86 hardware. That kind of upstream contribution is genuinely rare for a hyperscaler.

Is This “Embrace, Extend, Extinguish” in Disguise?

Whenever Microsoft expresses enthusiasm for open source, a predictable chorus invokes the three letters EEE — the Embrace, Extend, Extinguish strategy Microsoft was credibly accused of in the late 1990s. The concern is understandable. But several structural factors make the old playbook unavailable here.

First, licensing. Linux’s core components are covered by the GPL, which makes proprietary lock-in through extensions legally and practically difficult. The landscape is fundamentally different from the era of the leaked “Halloween Documents,” when Microsoft strategists were openly discussing ways to undermine open-source software.

Second, incentive structure. Windows is no longer Microsoft’s primary revenue engine. By some estimates, Windows accounts for roughly 6% of Microsoft’s total revenue today; the bulk flows from Azure and Microsoft 365. A company whose profits depend on cloud infrastructure running Linux has no rational motive to undermine Linux. More than two-thirds of Azure’s customer compute cores already run Linux, and platforms like Microsoft 365, GitHub, and OpenAI’s ChatGPT — which Microsoft powers — all run on Linux and Kubernetes.

The more accurate frame for understanding Azure Linux is not “extinguish,” but accountability. Enterprise customers want a clear throat to grab when something goes wrong. Amazon, Google, and now Microsoft all maintain their own distributions partly because a first-party OS means a single entity — with a business relationship and a support contract — owns the full stack from kernel to application. That is a commercial motivation, not an ideological one.

What Azure Linux 4.0 Is — and Is Not — Right Now

Clarity matters here, because Microsoft’s use of the word “general-purpose” has been genuinely misleading. Azure Linux 4.0 entered public preview on June 2, 2026, available for Azure Virtual Machines, VM Scale Sets, and container images. AKS support and WSL integration are still pending. General availability is not expected until late 2026.

“General-purpose” means it has expanded beyond container hosting — any Azure VM can now run it. It does not mean it is a general-purpose Linux distribution in the way Ubuntu or Fedora are. Outside Azure, it has no official support. Running it on-premises or on another cloud is technically possible but entirely unsupported by Microsoft. Amazon Linux 2023, by contrast, does run as a VM image outside AWS, at least at a basic level. The two companies’ appetite for “general” is meaningfully different.

Why This Moment Matters

Azure Linux 4.0 is a moderately sized product announcement, but it is a large symbolic one. Microsoft has spent more than twenty years travelling from Steve Ballmer’s “Linux is a cancer” to shipping a Linux distribution derived from Red Hat’s community upstream. That journey reflects a company that figured out its business model and productised the foundation that business actually runs on.

The three major public cloud providers now all maintain their own Linux distributions. Behind that trend is a solidifying conviction: cloud providers no longer want to merely control upper-layer services. They want the entire stack — chips, networking, operating system kernel, container runtime, application platform — to be shaped by their own hands. Azure Linux 4.0 is Microsoft’s formal entry into that competition, built, perhaps fittingly, on the shoulders of its one-time rival.