Azure Linux 4.0 Preview: Microsoft Splits Its Linux Strategy

Microsoft just formalized something developers on Azure have been waiting for: two Linux distributions for two distinct jobs. At Open Source Summit North America this week, the company pushed Azure Linux 4.0 into public preview — a Fedora-derived, RPM-based OS for virtual machines — while simultaneously shipping Azure Container Linux to general availability for AKS and container workloads. The split ends years of a single distro trying to serve two incompatible goals, and it’s the right call.

Two Products, Two Jobs

The distinction is now clean. Announced at Open Source Summit North America, Azure Linux 4.0 is a mutable, package-managed server OS for virtual machines. Azure Container Linux is an immutable, minimal container host for AKS nodes and Azure Container Instances. They share a heritage and a supply chain philosophy, but they solve different problems — and Microsoft has stopped pretending otherwise.

This mirrors patterns established by Red Hat (RHEL for servers, CoreOS for containers) and Google (Debian-based OS for VMs, Container-Optimized OS for GKE). It took Microsoft longer to get here, but the result is architecturally sound. An OS optimized for dnf install apache2 and one optimized for sub-5-second container boots cannot be the same binary.

Azure Container Linux Is GA — Start Migrating

The more immediately actionable announcement is Azure Container Linux reaching general availability. New AKS clusters and Azure Container Instances can use it today, with full Microsoft support and a 3-year lifecycle tied to the AKS LTS window.

The performance numbers matter for teams running at scale. Azure Container Linux delivers a 40% smaller disk footprint compared to Ubuntu Server on AKS, boots in under 5 seconds on most VM sizes, and benchmarks show up to 15% better container density per node. That last number compounds: better density means fewer nodes, which means lower bills.

Migrating an existing AKS cluster is an in-place operation. Update your infrastructure-as-code to specify the new OS SKU and redeploy:

# Terraform
default_node_pool {
  os_sku = "AzureLinux"
}

# Bicep
osSku: 'AzureLinux'

# Azure CLI (add new node pool)
az aks nodepool add --cluster-name myCluster \
  --name newpool --os-sku AzureLinux

The cluster handles the rest — surging capacity and rolling through node restarts. You can roll back by reverting the SKU in your template. The migration guide on Microsoft Learn has the full walkthrough.

Azure Linux 4.0: The Fedora Pivot

Azure Linux 4.0 is a bigger architectural shift than the version number implies. Previous versions (based on CBL-Mariner) maintained their own package tree. Version 4.0 pivots to Fedora-sourced packages with Azure-specific overlays — and Microsoft’s policy is to keep those overlays minimal to avoid upstream divergence.

Key changes in 4.0:

• Kernel: Jumps from 5.15 LTS to 6.6 LTS
• Package manager: Migrates from TDNF to DNF (TDNF stays for scripted environments)
• Packages: 3,000+ precompiled, Microsoft-verified — Python 3.12, Node.js 22, .NET 9
• SELinux: Enforcing by default (was permissive in 3.0) — audit your apps before migrating
• Dev tool: azl-shell — a containerized dev environment mirroring the Azure Linux filesystem for local compatibility testing

The SELinux change is the one most likely to break existing workloads silently. If your application relied on permissive mode to get away with something it shouldn’t, Azure Linux 4.0 will surface that. That’s a feature, not a bug — but plan for it.

Azure Linux 4.0 is still in preview. GA is expected in H2 2026. Test now in non-production if your team runs Linux VMs on Azure.

Check Your Clusters: Azure Linux 2.0 Is Already Gone

If none of this feels urgent, consider: Azure Linux 2.0 support ended in November 2025, and node images were removed on March 31, 2026. Clusters still on 2.0 cannot scale their node pools. This isn’t a future concern — it’s a current operational blocker for teams that ignored the deprecation notices.

What to Do Now

• Running AKS? Migrate node pools to Azure Container Linux. It’s GA, supported, and faster than what you’re likely running.
• Running Azure VMs with Linux? Start testing Azure Linux 4.0 in non-prod. Plan for GA in H2 2026.
• Still on Azure Linux 2.0? Stop what you’re doing and migrate immediately — you’re already blocked from scaling.
• Using SELinux permissive mode? Audit your applications now. Azure Linux 4.0 enforces by default.

Microsoft’s open source posture in 2026 is genuinely different from where the company stood a decade ago. Azure Linux 4.0 and Azure Container Linux aren’t marketing exercises — they’re the plumbing under a significant portion of Azure’s AI and cloud-native workloads. The two-track split makes that plumbing better, and it’s overdue.