{"id":172762,"date":"2026-05-20T00:24:36","date_gmt":"2026-05-19T22:24:36","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/microsoft-razvivaet-distributiv-obshhego-naznacheniya-azure-linux-4-na-baze-fedora-linux"},"modified":"2026-05-20T00:24:36","modified_gmt":"2026-05-19T22:24:36","slug":"microsoft-razvivaet-distributiv-obshhego-naznacheniya-azure-linux-4-na-baze-fedora-linux","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/microsoft-razvivaet-distributiv-obshhego-naznacheniya-azure-linux-4-na-baze-fedora-linux","title":{"rendered":"Microsoft develops a general-purpose distribution Azure Linux 4 based on Fedora Linux","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Microsoft has published developments related to the Azure Linux 4 distribution, which has undergone a complete overhaul compared to the 3.0 branch and has transitioned from its own package base to using packages from Fedora 43. Previously, Azure Linux was positioned as a platform for Linux environments used in cloud infrastructure, edge systems, and various Microsoft services, but now Azure Linux is presented as a secure and reliable general-purpose operating system optimized for the Azure cloud, suitable for use in virtual machines, containers, the WSL (Windows Subsystem for Linux) environment, and as the primary OS on computers. <\/p>\n

The Azure Linux 4 branch is noted to be in development. For production deployments, it is recommended to use the Azure Linux 3 branch. Ready builds are not yet available, but there is a build guide provided. Distribution-specific changes are released under the MIT license. <\/p>\n

In forming the distribution, instead of creating a fork of Fedora, Azure Linux 4 has adopted a declarative approach, allowing the recreation of RPM packages with the necessary modifications and settings from the standard Fedora repositories using configuration files in TOML format. Additional functionality is defined in the form of overlays, which allow generating Azure Linux-specific package spec files based on the standard SRPM packages from Fedora Linux. Overlays define modifications made on top of the Fedora packages, such as additional constructs in spec files, patches, and build parameters. <\/p>\n

The package unit in Azure Linux 4 consists of \"components\" (source packages), which are mostly imported from Fedora through dist-git and can form one or more RPM packages. All components are built from source code, and binary packages from Fedora are not transferred. The azldev tool, written in Go and provided under the MIT license, is used to generate the resulting RPM packages based on overlays. <\/p>\n

Among the features of Azure Linux 4, the delivery of a Linux kernel with additional optimizations, protection against supply chain attacks, a predictable support and update release cycle, built-in capabilities for integration with Azure cloud, and security enhancements stand out. The Azure Linux build system enables the generation of both installation environments with RPM packages and monolithic system images created using rpm-ostree tools, which can be updated atomically without breaking them into individual packages. Two models of update delivery are supported: via individual package updates and by rebuilding and updating the entire system image. <\/p>\n

Security measures implemented in Azure Linux include: <\/p>\n