Azure Linux 4.0 Moves to Fedora Base for Azure Workloads

Azure Linux 4.0 shifts to a Fedora upstream base, offering Linux kernel 6.18 LTS, native Azure tooling integration, and no additional OS licensing costs for virtual machines and container workloads.

TL;DR

  • Microsoft has released Azure Linux 4.0, replacing its internal Common Base Linux (CBL-Mariner) architecture with a Fedora upstream foundation.
  • The operating system runs Linux kernel 6.18 LTS, tuned with Hyper-V synthetic device drivers, vMBus transport optimizations, and host-level I/O enhancements.
  • Deployment targets expand beyond Azure Kubernetes Service (AKS) container host node pools to standalone Azure Virtual Machines, VM Scale Sets, relational databases, and GPU-accelerated AI/ML instances.
  • Azure Linux 4.0 carries no additional OS licensing surcharge on Azure, providing a direct zero-cost alternative to Red Hat Enterprise Linux and SUSE Linux Enterprise Server.

Microsoft has released azure linux 4.0, marking a structural shift in the cloud provider’s internal operating system strategy. First introduced to public cloud environments in November 2026 following an initial announcement in June 2026, version 4.0 abandons Microsoft’s custom Common Base Linux (CBL-Mariner) foundation in favour of a Fedora upstream base. This architectural realignment replaces bespoke distribution plumbing with standard RPM package management while retaining Microsoft’s internal engineering focus on hypervisor integration and guest kernel performance tuning.

The operating system couples a Fedora-derived userland with a custom-compiled Linux kernel 6.18 LTS. This kernel includes hypervisor-native guest drivers for Microsoft Azure infrastructure, guest-to-host memory management features, and pre-integrated agents for cloud management services. While earlier iterations served primarily as a minimal host OS for Azure Kubernetes Service node pools, Azure Linux 4.0 is positioned as a general-purpose Linux distribution for enterprise enterprise workloads across the platform.

By offering Azure Linux 4.0 with zero additional OS licensing fees on Azure cloud platforms, Microsoft introduces a financial factor into cloud operating system selection. According to reporting by The Register, the distribution enables enterprise engineering teams to evaluate whether commercial third-party subscriptions like Red Hat Enterprise Linux (RHEL) or SUSE Linux Enterprise Server (SLES) remain necessary for workloads running on Microsoft Azure.

Evolution of Microsoft’s In-House Operating System Strategy

Microsoft’s development of custom Linux distributions began in its networking infrastructure. Before deploying Linux as an application guest OS, Microsoft developed Software for Open Networking in the Cloud (SONiC), a Linux-based network operating system designed to control telemetry, switching, and routing hardware across Azure data centres. By 2015, internal operational dependencies on Linux had expanded across Microsoft’s cloud infrastructure, necessitating a standardised, internal operating system layer to power core microservices.

In 2020, Microsoft published this internal distribution as Common Base Linux (CBL-Mariner). CBL-Mariner served as a bare-bones, security-hardened Linux distribution built specifically for Microsoft’s internal engineering teams and Azure services. It provided a minimal software bill of materials (SBOM), reducing attack surface area and patching overhead for infrastructure services. To allow platform engineers running workloads on the Azure Kubernetes Service (AKS) to execute workloads on the same base environment used by the control plane, Microsoft integrated CBL-Mariner into public AKS node pool offerings.

The distribution underwent systematic branding and structural revisions as its user base expanded beyond internal infrastructure teams:

  • CBL-Mariner 1.0/2.0 (2020–2022): Rebranded publicly as Azure Linux 2.0 in 2022. The OS operated exclusively as a minimal container host, lacking general-purpose enterprise application tooling and third-party software repository support.
  • Azure Linux 3.0 (2024): Expanded deployment across AKS node pools and select Azure platform-as-a-service (PaaS) offerings. Although stability improved, maintenance of a completely bespoke upstream package repository created supply chain friction for software requiring standard Enterprise Linux dependencies.
  • Azure Linux 4.0 (2026): Transitioned the underlying base from CBL-Mariner to an upstream Fedora base. Announced in June 2026 and released in November 2026, version 4.0 broadens the target deployment footprint from container hosts to standalone virtual machines, scale sets, and high-performance computing nodes.

Maintaining a custom Linux distribution from source requires extensive engineering resources to monitor, backport, and patch thousands of upstream software packages. By shifting the foundational package layer to Fedora upstream, Microsoft offloads general-purpose package maintenance to the broader open-source ecosystem. This allows Microsoft’s Linux Systems Group to focus engineering resources on hypervisor integration, security baseline compliance, eBPF observability, and Azure management plane interoperability.

Upstream Alignment: Adopting the Fedora RPM Ecosystem

Transitioning Azure Linux 4.0 to a Fedora foundation aligns Microsoft’s operating system with the Red Hat package ecosystem. Earlier versions of CBL-Mariner utilised a custom RPM-based configuration with distinct package naming structures and limited third-party software availability. By adopting Fedora as its upstream baseline, Azure Linux 4.0 natively inherits the standard RPM repository hierarchy, package spec conventions, and dependency resolution mechanisms associated with the broader enterprise Linux software family.

Platform engineers and sysadmins managing Azure Linux 4.0 interact with standard dnf package management utilities. This alignment streamlines software supply chains for enterprise operations by simplifying package installation and build processes:

# Verifying OS release metadata on Azure Linux 4.0
cat /etc/os-release

# Inspecting active repository configurations
dnf repolist -v

# Installing infrastructure packages using standard DNF syntax
sudo dnf install -y htop iperf3 tracepath

The transition to a Fedora base delivers immediate operational advantages for devops pipelines and software distribution:

  • Ecosystem Compatibility: Applications, monitoring agents, and security tools built for RHEL, Fedora, or CentOS Stream can be ported to Azure Linux 4.0 with minimal package modification.
  • Toolchain Standardisation: Developers can construct RPM specs and build container base images using established open-source toolchains, avoiding proprietary distribution-specific build scripts.
  • Developer Familiarity: Systems administrators trained on enterprise RPM distributions can operate Azure Linux 4.0 environments using familiar administrative conventions, file paths, and systemd service configurations.

From a software supply chain perspective, rebasing on Fedora changes how software updates flow into Azure environments. Microsoft ingests upstream Fedora source packages, filters them through internal automated security scanners, strips unneeded desktop or consumer modules, and signs the resulting binaries using Microsoft code-signing authorities. These packages are then served directly from Microsoft Edge Content Delivery Networks (CDNs).

Upstream Baseline Versioning

Microsoft has not publicly disclosed the exact Fedora release number (e.g., Fedora 40 or Fedora 41) used as the precise upstream point of origin for the Azure Linux 4.0 launch build. Systems administrators should query /etc/os-release or inspect repository metalink sources directly on deployed instances to confirm specific package baseline versions.

Kernel 6.18 LTS Optimisations and Hyper-V Guest Tuning

At the core of Azure Linux 4.0 is Linux kernel 6.18 LTS, customized specifically for Microsoft Azure’s hypervisor layer. Rather than running a generic distribution kernel, Microsoft compiles the 6.18 kernel tree with custom configuration flags, backported hypervisor patches, and explicit kernel module defaults tuned for multi-tenant hyper-scaler environments.

The fundamental architecture relies on deep integration between the Linux kernel guest drivers and the underlying Azure Hyper-V virtualisation bus (vMBus). This high-speed synthetic channel bypasses legacy PCI device emulation, executing I/O operations directly between guest memory buffers and host hypervisor storage and networking stacks.

+-------------------------------------------------------------------+
|                     Azure Linux 4.0 Guest OS                      |
|                                                                   |
|   +-------------------+  +-------------------+  +-------------+   |
|   | Enterprise Apps   |  | Container Runtime |  | Azure CLI   |   |
|   +---------+---------+  +---------+---------+  +------+------+   |
|             |                      |                   |          |
|   =========== System Call Interface (POSIX / eBPF) ============   |
|                                                                   |
|   +-----------------------------------------------------------+   |
|   |                  Linux Kernel 6.18 LTS                    |   |
|   |  +------------------+ +-----------------+ +------------+  |   |
|   |  |  hv_storvsc      | |  hv_netvsc      | |  hv_utils  |  |   |
|   |  | (Storage Driver) | | (Network Driver)| | (Services) |  |   |
|   |  +--------+---------+ +--------+--------+ +-----+------+  |   |
|   +-----------|--------------------|-------------------|------+   |
+---------------|--------------------|-------------------|----------+
                |                    |                   |
================|====================|===================|===========
                |        Hyper-V Virtual Bus (vMBus)      |
================|====================|===================|===========
                v                    v                   v
+-------------------------------------------------------------------+
|                    Azure Hyper-V Host Layer                       |
|   +-------------------+  +-------------------+  +-------------+   |
|   | NVMe Direct Access|  | Accel. Networking |  | Host Clock  |   |
|   +-------------------+  +-------------------+  +-------------+   |
+-------------------------------------------------------------------+

The primary guest drivers compiled into the Azure Linux 4.0 kernel tree include:

  • hv_storvsc: Synthetic storage driver communicating directly with Azure Managed Disks and local NVMe arrays, providing elevated I/O operations per second (IOPS) while reducing host-side CPU context switches.
  • hv_netvsc: Synthetic network driver supporting Accelerated Networking (SR-IOV). It allows virtual machine network interfaces to directly map host physical network interface cards (NICs), achieving lower latency and higher packet throughput.
  • hv_balloon: Dynamic memory allocation driver facilitating memory ballooning and host-driven guest memory resizing, allowing cloud hosts to reallocate unused physical RAM without forcing guest reboot cycles.
  • hv_utils: Time-synchronisation and guest heartbeat module, ensuring sub-millisecond clock drift accuracy against host PTP (Precision Time Protocol) references required for distributed transaction logging.

Kernel 6.18 LTS also includes memory management and scheduler modifications optimized for cloud host topologies. Non-Uniform Memory Access (NUMA) node placement is tuned automatically based on the hardware topology presented by Azure VM sizes (such as E-series memory-optimized or F-series compute-optimized instances). Transparent Huge Pages (THP) defaults and memory compaction routines are configured to mitigate memory fragmentation stalls in long-running container hosts and database engines.

Native Observability and Security Tooling Integrations

Enterprise operating system deployments often require significant post-provisioning configuration to install monitoring agents, vulnerability scanners, and platform management tools. Azure Linux 4.0 addresses this friction by embedding native support hooks and binary modules for Microsoft’s cloud control plane directly into the system image.

For threat protection and compliance monitoring, Azure Linux 4.0 includes pre-validated kernel interface bindings for Microsoft Defender for Cloud. Older distribution images frequently encounter operational issues when eBPF (Extended Berkeley Packet Filter) probes or security kernel modules fail to compile against updated kernel headers. Azure Linux 4.0 avoids these runtime compilation failures by ensuring kernel 6.18 LTS provides native eBPF system call hooks verified against Defender security daemons out of the box.

System observability is handled through integrated compatibility with the Azure Monitor Agent (AMA). Systemd units, audit logging daemons (auditd), and rsyslog configurations are structured to route system telemetry, authentication logs, and performance metrics directly to Azure Monitor Log Analytics workspaces without requiring third-party log collectors.

# Checking status of native Azure observability and management daemons
systemctl status azure-monitor-agent.service --no-pager
systemctl status waagent.service --no-pager

# Auditing active eBPF programs utilised by security telemetry
sudo bpftool prog list

Security baseline defaults in Azure Linux 4.0 follow established enterprise standards. Security-Enhanced Linux (SELinux) is included in an active configuration, offering mandatory access control (MAC) policies tailored for system services. Cryptographic subsystems support FIPS 140-3 operational modes when enabled via kernel boot parameters, allowing compliance with government and regulated industry frameworks.

Management operational friction is further reduced through built-in support for the Azure CLI environment and Azure Instance Metadata Service (IMDS) endpoints. Cloud-init initialization routines are optimized for Azure IMDS, reducing instance spin-up latency during auto-scaling events by streamlining metadata retrieval, network interface provisioning, and SSH key injection.

Expanding Scope: From Container Hosts to General Workloads

While previous versions operated primarily as minimal container node hosts within Azure Kubernetes Service (AKS), Microsoft positions Azure Linux 4.0 for broader enterprise deployment across diverse cloud architectures. Moving to a Fedora base provides the application package compatibility required to support multi-tier software stacks directly on bare virtual machine instances.

Platform architects can deploy Azure Linux 4.0 across several Azure compute footprints:

  • Standalone Azure Virtual Machines: Suitable for hosting enterprise web stacks (Nginx, Apache, Node.js), application runtimes (Java OpenJDK, .NET Core, Python), and custom enterprise software suites.
  • Azure Virtual Machine Scale Sets (VMSS): Configured for auto-scaling stateless application tiers where rapid boot times, minimal image sizes, and consistent IMDS initialisation reduce scaling latencies.
  • Enterprise Relational and Key-Value Databases: Optimized kernel I/O scheduling and storage driver stacks provide high throughput for database engines such as PostgreSQL, MySQL, MariaDB, and Redis.
  • GPU-Accelerated AI/ML Workloads: Pre-tested driver module hooks support NVIDIA CUDA runtimes and AI acceleration libraries on Azure NC, ND, and NV-series GPU virtual machines.

To evaluate how Azure Linux 4.0 compares against traditional enterprise Linux options on Azure, consider the following technical and operational breakdown:

Feature / Dimension Azure Linux 4.0 Ubuntu 24.04 LTS Red Hat Enterprise Linux (RHEL) SUSE Linux Enterprise (SLES)
Upstream Lineage Fedora Debian Fedora / CentOS Stream openSUSE Factory
Package Format RPM (via dnf) DEB (via apt) RPM (via dnf) RPM (via zypper)
Kernel Baseline 6.18 LTS (Azure Tuned) 6.8 (Ubuntu OEM/Azure) 5.14 / 6.x (RHEL Tuned) 6.4 (SUSE Kernel)
OS License Surcharge Zero ($0.00) Zero (Canonical Pro extra) Hourly / Annual Surcharge Hourly / Annual Surcharge
Target Footprint AKS, VMs, Scale Sets General Purpose / Cloud General Purpose / Enterprise General Purpose / Enterprise
Default Security MAC SELinux AppArmor SELinux AppArmor
Platform Integration Native Azure Services WALinuxAgent / Custom WALinuxAgent / Custom WALinuxAgent / Custom

Performance Benchmark Availability

Detailed comparative performance benchmarks (such as Sysbench, SPECvirt, or Flexible I/O Tester results) contrasting Azure Linux 4.0 against Ubuntu LTS or RHEL on equivalent Azure VM SKUs have not been formally published by Microsoft. Engineering teams should execute empirical synthetic workload tests prior to migrating production database tiers.

Licensing Economics: RHEL, SUSE, and Zero-Cost OS Layers

The introduction of Azure Linux 4.0 presents cloud infrastructure architects with an opportunity to optimize infrastructure total cost of ownership (TCO). On public cloud platforms, operating systems generally fall into two financial categories: community distributions provided without direct software licensing fees (such as Ubuntu Server or Debian), and commercial enterprise distributions that incur premium software licensing surcharges per core hour (such as RHEL and SLES).

Commercial Linux subscriptions running on Azure Virtual Machines add software licensing fees on top of base Azure compute infrastructure costs. For large instance fleets, these software surcharges can account for 20% to 40% of total VM operational expenditure.

===================================================================
Virtual Machine Fleet Financial Comparison (500 VM Instances)
Configuration: Standard_D8s_v5 (8 vCPUs, 32 GB RAM)
Assumed Operating Profile: 24x7 Continuous Execution (730 Hours/Month)
===================================================================

[ Option A: Commercial Enterprise Linux (RHEL / SLES) ]
+-----------------------------------------------------------------+
| Base Azure Compute Cost (~$0.384/hr x 500)       : $140,160/mo  |
| OS Software License Surcharge (~$0.06/core/hr)   : $175,200/mo  |
+-----------------------------------------------------------------+
| TOTAL ESTIMATED MONTHLY OS & COMPUTE EXPENDITURE : $315,360/mo  |
+-----------------------------------------------------------------+

[ Option B: Azure Linux 4.0 ]
+-----------------------------------------------------------------+
| Base Azure Compute Cost (~$0.384/hr x 500)       : $140,160/mo  |
| OS Software License Surcharge                    : $0,000,000   |
+-----------------------------------------------------------------+
| TOTAL ESTIMATED MONTHLY OS & COMPUTE EXPENDITURE : $140,160/mo  |
+-----------------------------------------------------------------+

ESTIMATED DIRECT MONTHLY LICENSING SAVINGS: $175,200 / month
===================================================================

Adopting Azure Linux 4.0 eliminates software licensing surcharges across both AKS node pools and standalone Virtual Machine Scale Sets. For organisations operating thousands of compute cores, this structural cost difference creates compelling economic incentives to standardize on Microsoft’s native distribution.

However, technical decision-makers must evaluate financial savings against potential platform coupling trade-offs:

  • Vendor Platform Coupling: Azure Linux 4.0 is optimized explicitly for and provided within Microsoft Azure infrastructure. Deploying the same operating system image across multi-cloud environments (such as AWS or Google Cloud) or on-premises bare-metal data centres is unsupported, potentially complicating multi-cloud operational strategies.
  • Support Boundaries: Enterprise software vendor subscriptions (Red Hat / SUSE) include direct, end-to-end OS software support SLAs, bug-fix guarantees, and dedicated technical account managers for guest OS internals. Azure Linux support is handled directly through standard Azure Cloud Support contracts, shifting system-level troubleshooting to Microsoft Azure support engineers.
  • Application Vendor Certifications: Certain proprietary enterprise applications (such as SAP HANA or legacy commercial databases) mandate certified execution environments restricted strictly to specified RHEL or SLES release builds. Platform teams must audit third-party vendor support matrices before planning OS migration projects.

Lifecycle and Support Window Verification

While Azure Linux 4.0 incorporates Linux kernel 6.18 LTS, Microsoft has not formally published the precise end-of-life (EOL) calendar date or enterprise support lifecycle duration for version 4.0 beyond the baseline kernel maintainer lifecycle. Platform managers should monitor official vendor announcements for confirmed support matrices.

Practitioner Guidance: Adoption Path and Deployment Strategy

Transitioning enterprise infrastructure from general-purpose distributions to Azure Linux 4.0 requires a systematic validation sequence to ensure application compatibility, security policy adherence, and operational readiness.

Step 1: Pilot Testing in Non-Production AKS Node Pools

Validate application compatibility by deploying Azure Linux 4.0 as the node pool OS within non-production Azure Kubernetes Service clusters. This isolates containerized workloads from OS userland dependencies while verifying runtime stability.

# Upgrading or creating an Azure Linux 4.0 node pool in an existing AKS cluster
az aks nodepool add \
  --resource-group rg-platform-prod \
  --cluster-name aks-core-compute \
  --name azlinux4pool \
  --os-sku AzureLinux \
  --node-vm-size Standard_D4s_v5 \
  --node-count 3

Step 2: Custom Image Creation and Scale Set Validation

For virtual machine workloads, construct baseline image templates using HashiCorp Packer or Azure Image Builder. Verify that cloud-init scripts execute reliably, network interfaces attach correctly, and local storage arrays format without manual intervention.

# Querying available Azure Linux 4.0 URN images in Azure Marketplace
az vm image list \
  --publisher MicrosoftCBLMariner \
  --offer azure-linux-4 \
  --all \
  --output table

Step 3: Security Policy Compliance and Audit Verification

Confirm that organizational endpoint protection agents, SIEM log forwarding rules, and vulnerability scanners execute cleanly under kernel 6.18 LTS and SELinux enforced states. Ensure custom eBPF programs or security monitoring tools function without throwing audit policy violations.

# Checking SELinux enforcement status and audit logs
sestatus
sudo ausearch -m avc -ts recent

Step 4: Dependency Auditing for Package Compatibility

Audit legacy application installation scripts, Ansible roles, and configuration management codebases. Replace legacy yum or custom Mariner repository references with standard dnf package definitions pointing to valid Azure Linux 4.0 mirrors.

Common Implementation Mistakes

  • Assuming Full Bit-for-Bit RHEL Identity: While Azure Linux 4.0 uses a Fedora upstream base and RPM packaging, it is not a byte-for-byte clone of RHEL. Avoid assuming proprietary RHEL-only binary blobs or specific enterprise tools will function without package validation.
  • Overriding Kernel Parameters Arbitrarily: Applying generic Linux tuning configurations designed for physical bare-metal hardware can degrade hypervisor synthetic driver performance. Maintain hypervisor driver defaults unless specific workloads dictate change.
  • Neglecting Metadata Service Security: When deploying cloud-init configurations on Azure Virtual Machines, ensure application routines restrict direct access to IMDS endpoints (169.254.169.254) to prevent SSRF credential exposure risks.

Key Takeaways for Enterprise Cloud Infrastructure Teams

Azure Linux 4.0 represents an evolution in Microsoft’s cloud platform strategy. By replacing CBL-Mariner with an upstream Fedora baseline, Microsoft aligns its internal cloud operating system with standard enterprise Linux package conventions while directing its engineering focus toward hypervisor tuning, kernel optimizations, and cloud control plane integrations.

For cloud architects, platform engineers, and financial operations (FinOps) leads, key strategic takeaways include:

  • Financial Impact: Eliminating OS licensing surcharges across Azure Virtual Machines, scale sets, and container hosts provides a mechanism for reducing infrastructure overhead on large compute fleets.
  • Technical Architecture: Kernel 6.18 LTS integration coupled with custom Hyper-V synthetic drivers ensures optimized network throughput, storage IOPS, and host clock synchronization across Azure VM families.
  • Operational Consistency: Adopting the standard RPM ecosystem simplifies software packaging pipelines, allowing sysadmins to leverage standard dnf workflows and existing Red Hat operational expertise.
  • Scope of Application: Azure Linux 4.0 is no longer restricted to lightweight container nodes; it is fully capable of hosting general enterprise applications, high-performance database engines, and GPU-accelerated machine learning pipelines.

Enterprise infrastructure teams should initiate pilot evaluations within non-production AKS clusters and virtual machine scale sets to benchmark application compatibility, assess operational management tooling, and quantify financial savings across their Azure cloud footprint.

Frequently asked questions

What is the primary difference between Azure Linux 3.0 and Azure Linux 4.0?

Azure Linux 4.0 replaces Microsoft’s proprietary Common Base Linux (CBL-Mariner) foundation with an upstream Fedora base. This updates the package ecosystem to standard Fedora-derived RPMs using dnf, while updating the base OS kernel to Linux 6.18 LTS with custom Hyper-V synthetic device optimizations.

Does Azure Linux 4.0 incur any additional licensing costs on Azure Virtual Machines?

No. Azure Linux 4.0 is provided by Microsoft with zero additional OS licensing surcharges across Azure cloud platforms. Users pay only for the underlying Azure compute infrastructure, RAM, storage, and networking resources consumed by the virtual machine instances.

Can Azure Linux 4.0 be deployed outside of Azure Kubernetes Service (AKS)?

Yes. While earlier versions targeted container node pools, Azure Linux 4.0 is explicitly structured for general-purpose infrastructure deployment. It can be provisioned across standalone Azure Virtual Machines, Virtual Machine Scale Sets, relational databases, web application tiers, and GPU-accelerated AI/ML nodes.

Which package management system does Azure Linux 4.0 use?

Azure Linux 4.0 uses the RPM package ecosystem derived from upstream Fedora. Systems administrators interact with the distribution using standard dnf and rpm package management utilities, sourcing packages signed and distributed through Microsoft’s cloud repository networks.

What Linux kernel version powers Azure Linux 4.0?

Azure Linux 4.0 runs Linux kernel version 6.18 LTS. The kernel is custom compiled by Microsoft with integrated Hyper-V guest drivers, vMBus transport mechanisms, memory ballooning capabilities, and platform-specific tuning designed to maximize synthetic device I/O throughput on Azure hypervisors.

Sources and further reading

This article was drafted with AI assistance from the publicly cited sources and passed automated checks for structure and sourcing. Verify critical details against the vendor advisories linked above before acting.