Azure Local 2411: New Versioning, New OS, New Era

Hot on the heels of the Azure Local rebrand at Ignite, the first release under the new name has arrived. Azure Local 2411 is significant not just for its features, but for what it represents in terms of how the platform is versioned, updated, and lifecycled going forward.

A New Versioning Model

If you’ve been following along since my April post about Azure Stack HCI in 2024 , you’ll remember the release train model. Two concurrent release trains, each consisting of an OS baseline plus cumulative updates, running in parallel for six months. It was a big step forward from the annual release cadence of the Windows Server world.

Azure Local 2411 evolves this further. The versioning model now follows a YYMM format, so 2411 means 2024, November. Each release is supported for six months, and the platform includes multiple release trains running concurrently. The numbering scheme is cleaner, more intuitive, and aligns naturally with a monthly release cadence.

What hasn’t changed is the fundamental principle that Azure Local features are decoupled from the OS updates. Whether you’re on the 23H2 OS baseline or the new 24H2 OS baseline, the Azure Local features delivered through the Arc Resource Bridge and Arc Extensions remain consistent. This was one of the best design decisions in the 23H2 era, and it carries forward.

The 24H2 OS Baseline

The 2411 release introduces the 24H2 OS baseline, built on the same kernel generation as Windows Server 2025 . This brings all of the kernel-level improvements I discussed last month, including native NVMe support, improved security defaults, and the foundational work for hotpatching.

For existing deployments on the 23H2 OS baseline, this is an important planning point. You don’t need to jump to 24H2 immediately. The 23H2 release trains continue to be supported and receive updates. But you should start thinking about when you want to make the move, because the 23H2 OS baseline will eventually reach end of support.

For new deployments, 2411 on the 24H2 OS baseline is the way forward. You get the latest kernel, the latest security improvements, and you’re starting on the current generation from day one.

What’s New in 2411

Beyond the versioning and OS baseline changes, the 2411 release includes several feature improvements worth noting.

The Azure Arc integration continues to tighten. Improvements to the VM management experience in the Azure portal, better monitoring and diagnostics through Azure Monitor integration, and enhanced extension management all contribute to a more polished day-to-day operational experience.

From a security perspective, the 24H2 security baseline builds on the already strong posture established in 23H2. If you recall, 23H2 introduced enforced WDAC policies, HVCI, and over 300 security baseline settings by default. The 24H2 baseline adds additional hardening on top of this foundation.

Lifecycle management improvements continue as well, with the Lifecycle Manager receiving updates that improve the reliability and observability of the update process. For Dell AX customers, the Solution Builder Extension continues to integrate Dell firmware and driver updates into the lifecycle management flow, ensuring that updates are validated end to end from disk to cloud.

What This Means for You

If you’re running Azure Local (or Azure Stack HCI, same thing, new name) in production today, the key takeaways are:

1. No rush to move OS baselines. Your 23H2 deployment continues to work and receive updates. Plan the move to 24H2 on your own timeline.

2. New deployments should target 2411. If you’re deploying fresh, start on the current generation.

3. The versioning model is simpler. YYMM format, six months of support per release, concurrent release trains. It’s easier to reason about than the old model.

4. Features are still decoupled from the OS. This remains the key architectural decision that gives you flexibility in how you manage your update cadence.

5. Dell SBE updates align with the new model. Dell continues to provide validated updates through the Solution Builder Extension, now aligned to the new versioning.

The pace of change in this platform has been remarkable over the past year. From an operating system to a hybrid cloud solution, from Azure Stack HCI to Azure Local, from release trains to monthly versioning. Through all of this change, the core value proposition remains the same: a consistent Azure experience, running on validated Dell hardware, with enterprise-grade lifecycle management. The wrapping has changed, but the substance keeps getting stronger.