Microsoft makes Azure Linux 4 generally available for customer VMs
Microsoft has made Azure Linux 4 generally available as a server operating system for customer virtual machines and virtual machine scale sets. Customers pay for the underlying Azure compute, with no additional operating-system licensing fee, according to Microsoft. The distribution is also used across Azure services, including Azure Kubernetes Service (AKS), App Service and Azure Cosmos DB.
The release gives enterprise teams another option for aligning the operating system used on virtual machines with the Linux environment behind Microsoft’s cloud services. Organizations that currently maintain separate distributions for VMs, Kubernetes nodes and container images may be able to reduce that variation by adopting Azure Linux across those environments. A common platform can make it easier to coordinate package and patch management, although teams will still need to assess compatibility with their workloads and establish their own update and validation processes.
A server-focused Linux distribution
Azure Linux is derived from Fedora and uses RPM packages. Microsoft positions it as a general-purpose server OS, not a desktop distribution; it is not designed for graphical user interfaces or desktop use. Version 4 includes Linux kernel 6.18 LTS, the dnf5 package manager, systemd 258, glibc 2.42, RPM 6.0, Python 3.14 and OpenSSL 3.5.
OpenSSL 3.5 includes support for post-quantum cryptography, which is intended to address the potential future threat posed by quantum computers to current cryptographic methods. Its presence in the release does not, by itself, mean workloads are using post-quantum algorithms. Enterprises should review their application and cryptographic configurations before drawing conclusions about protection for specific services.
Microsoft says SELinux is enabled by default and that drivers are signed. SELinux can restrict the resources processes are allowed to access, providing an additional control within the operating system. These defaults may help teams apply consistent baseline protections, but they do not replace workload-specific access controls, patching or monitoring.
Three container image options
Azure Linux 4 container images are available in three forms, all built from the same supply chain as the VM images and hosted on Microsoft Artifact Registry. Core images allow teams to install packages as needed. Runtime images are configured for Python, Node.js, Java or .NET workloads. Distroless images omit both the shell and package manager.
Removing those tools can reduce the utilities available to an attacker who gains access to a running container. It also limits the tools engineers can use to troubleshoot a live workload. Teams considering distroless images should therefore ensure their deployment and observability practices provide the information needed to diagnose issues without relying on an interactive shell inside the container.
The shared image supply chain is relevant to organizations seeking to manage VM and container operating systems together. However, using images from a common source does not remove the need to track image versions, apply updates and verify that deployed workloads are running approved builds. The source material does not specify a support lifecycle or release-update schedule for Azure Linux 4, so organizations evaluating it should confirm those details with Microsoft.
Security and workload integrations
Microsoft Azure Linux Program Lead Jim Perrin said several security vendors support the release. Microsoft identified Palo Alto Networks and Aqua Security for workload and container protection; Qualys for vulnerability identification and compliance monitoring; and Upwind and Wiz for runtime visibility and cloud context. Microsoft also named NVIDIA as providing options for GPU-accelerated AI and compute-intensive workloads.
These integrations may matter to teams seeking to use existing security and compute tooling with the distribution. Their presence should not be treated as a guarantee that a particular product configuration is supported or enabled by default; organizations should validate requirements with the relevant vendors.
Azure Linux 4 is available on GitHub. For enterprise platform teams, the main evaluation questions are whether the distribution supports the applications and operational tooling in use, how its updates fit existing maintenance windows, and whether a shared OS base can simplify management across VMs and containers without compromising workload-specific requirements.