Infographic showing Azure Linux 4 support for Azure VMs, scale sets, and container images, but not bare-metal servers.
Microsoft has declared Azure Linux 4 production-ready, and the support fine print matters as much as the headline. Microsoft's first-party Linux distribution launched in public preview at Build on June 2, 2026. On November 17, 2026, Microsoft's own Linux distribution, purpose-built for Azure, reached general availability for Azure Virtual Machines and Virtual Machine Scale Sets. Microsoft separately announced general availability for the Azure Linux 4 container images.

This is not a distro you can install anywhere and expect Microsoft to answer the phone. Here is what is covered, what isn't, and what to check before you commit.

Infographic showing Azure Linux 4 support for Azure VMs, scale sets, and container images, but not bare-metal servers. What actually went GA​

Microsoft's announcement names two things as generally available:

  • Azure Linux 4 on Azure VMs and Virtual Machine Scale Sets
  • Azure Linux 4 container images

Microsoft describes the OS as a Fedora-derived, RPM-based distribution that it builds and maintains itself. It is tailored for cloud workloads and designed with a minimal footprint. It is also explicitly not designed for desktop use or GUI applications.

The lineage is worth knowing. Microsoft's October 2026 retrospective traces the project back to CBL-Mariner, which emerged publicly in 2020. It became Azure Linux, and in May 2023 it became generally available to customers as a container host for AKS. Azure Linux 4.0 is the first version that Microsoft positions as a general-purpose server OS for customer VMs. It uses Fedora package sources as its upstream foundation, and Microsoft says it curates them for Azure rather than simply reproducing Fedora.

The support boundary​

Microsoft's Learn documentation says the project is open source, but Microsoft's support and lifecycle commitments apply only to Azure scenarios.

Deployment scenarioMicrosoft support
Azure VMs and VM Scale SetsSupported
AKS container hostSupported
Azure Linux container imagesSupported
Bare metal, ISO images, on-premises, other cloudsNot supported
Customized image built on a prebuilt Azure Linux image (for example, with Image Customizer)Supported
Image built from scratch from the GitHub sourcesNot covered

Microsoft's documentation adds that issues outside this scope might be closed.

This is a real consideration for anyone who has seen the downloadable ISO. Coverage in the preview period noted that Microsoft's GitHub page describes ISO support as community-based. Formal support applies to Azure deployments.

Production issues go through Azure support​

The Learn page says production issues or outages should go through an Azure support request in the Azure portal. GitHub issues are not monitored for production support. GitHub is for bug reports, documentation issues and feature requests. Triage there is best effort, with no guaranteed SLAs. Microsoft also lists reasons it will close issues, including these:

  • Incomplete reports
  • Duplicates
  • Out-of-scope scenarios
  • Issues with no activity for 30 days (these might be closed automatically)

Microsoft asks bug reports to include these details:

  • The Azure Linux version and image name
  • Reproduction steps
  • Logs
  • The Azure service involved
  • The VM size and region

A note on WSL​

Microsoft's GA post says developers can use Azure Linux on WSL to build and test on the same OS they deploy to Azure, using VS Code and CLI workflows. The Microsoft sources I could verify do not state a formal WSL support tier. Some secondary coverage describes WSL support as "best-effort", but I could not confirm that against a current Microsoft page. Treat WSL as a development convenience, not a production support path.

The preview post gave the install command as wsl --install -d AzureLinux. That was written while WSL support was still pending, so confirm it against current documentation before scripting it.

What "no licensing fee" means​

Microsoft says there is no additional OS licensing fee, and that you pay only for the underlying Azure compute. That does not make a workload free. The announcement gives no VM prices or cost comparisons, so any savings claim against a paid Linux subscription is yours to calculate. Microsoft's "lower cost" pitch also cites faster boot and scale-out from a leaner OS. The GA post gives no benchmarks for that.

The container image options​

All Azure Linux 4 images are published on Microsoft Artifact Registry. Microsoft says they come from the same supply chain as the VM images, with the same security updates and compliance posture.

  • Core: full flexibility to install whatever packages you need.
  • Runtime: preconfigured for Python, Node.js, Java or .NET.
  • Distroless: no shell and no package manager, for a minimal attack surface.

Runtime images were marked "not available at preview", so their arrival at GA is a meaningful step for application teams. Separately, Microsoft says Azure Linux 4 supports multiple container runtimes, including containerd and Podman. That is a statement about the OS, not about what the images bundle.

The component stack​

ComponentVersion
Linux kernel6.18 LTS
Package managerdnf5
systemd258
glibc2.42
RPM6.0
Python3.14
OpenSSL3.5 (post-quantum cryptography and improved QUIC support)

If you have scripts written around tdnf or older Azure Linux releases, the move to dnf5 and a Fedora-based stack is the first thing to test. That is my inference from the version changes. Microsoft's post does not say which tooling breaks.

Security claims and the FIPS question​

Microsoft says SELinux is enabled by default, drivers are signed, and OpenSSL 3.5 brings post-quantum cryptography support. It also lists optional built-in support for Microsoft Defender for Cloud, Azure Monitor and Trusted Launch. Security partners named at GA include Palo Alto Networks, AquaSec, Qualys, Upwind and Wiz.

FIPS 140-3 needs care. The June preview post listed FIPS 140-3 as in progress and said it would be available at GA. The GA announcement as I could inspect it does not confirm that validation has completed. Regulated shops should check Microsoft's current compliance documentation before treating Azure Linux 4 as FIPS-validated. Microsoft Learn still describes the status as in progress.

Lifecycle​

Microsoft's pre-GA post says Azure Linux 4.0 is designed around four years of full support. It says routine servicing will stay conservative, with more impactful package changes placed into planned refresh windows. The preview material also described a monthly security update cadence and an LTS kernel with monthly CVE backports. These are Microsoft's stated plans, not independently verified guarantees.

Should you move?​

The pitch is consistency: one Microsoft-supported base across VMs, Kubernetes nodes and containers. Microsoft is also candid that it remains one choice among many Linux distributions on Azure. It says customers should choose what fits their workload, ecosystem and support needs.

A practical checklist:

  1. Confirm every target runs on Azure, because on-premises and other clouds fall outside support.
  2. If you customize images, start from a prebuilt Azure Linux image, not a source build.
  3. Check your compliance requirements, especially FIPS 140-3, against current documentation.
  4. Test scripts and automation against dnf5 and the new component versions.
  5. Price the Azure compute for your VM sizes, because the free OS does not make the VM free.

Pilot it before a wholesale migration. A new distribution is a long-term commitment, however polished the launch post.

 

References

  1. Azure Linux 4 is generally available: what Microsoft supports NeoTeo 2026-11-20T05:01:31+00:00
  2. Announcing Azure Linux 4.0: Purpose-Built for Azure, Now in Public Preview techcommunity.microsoft.com
  3. Azure Linux 4 is generally available | Microsoft Community Hub techcommunity.microsoft.com