Azure Local 2603: From Cloud-Connected to Cloud-Operated
The March 2026 release of Azure Local - version 12.2603.1002.15 - landed quietly enough. A new OS baseline (26100.32522), .NET 8.0.25, updated Kubernetes versions for AKS Arc (1.31 through 1.33, with 1.30 dropped), KMS v2 migration guidance. Nothing that would make headlines on its own.
But there’s a more interesting story underneath the release notes, and it’s one that matters if you’re deploying or planning Azure Local in an enterprise environment: Microsoft is quietly but deliberately shifting Azure Local from a cloud-connected platform to a cloud-operated one.
That distinction might sound like marketing language. It’s not.
What Cloud-Connected Meant
For most of Azure Stack HCI’s life - through 23H2 and into the early 24H2 releases - “cloud-connected” was accurate. The platform ran on your hardware, in your datacentre, and used Azure for a defined set of functions: registration, billing, monitoring extension delivery, and portal visibility. The operational centre of gravity was local. You’d SSH into nodes, run PowerShell on the cluster, manage updates through local tooling with Azure providing the plumbing.
This was a significant improvement over traditional on-premises HCI. The Arc-based management model brought Azure consistency to local infrastructure in a way that older approaches never managed. But the fundamental assumption was that local infrastructure was administered locally.
What Cloud-Operated Means
The 2603 release - and honestly, the direction of travel over the past several release cycles - tells a different story. Microsoft is increasingly building Azure Local to be managed from Azure by default, with local administration as the secondary model.
Look at the 2603 feature emphasis: cloud-based deployment and updates, cloud-based monitoring, simplified VM management through the Azure portal. Each of these points in the same direction: the control plane is Azure, and local tooling is for edge cases.
This isn’t a surprise if you’ve been watching the product closely. Each release has tightened the operational dependency on Azure. Deployment now happens through the Azure portal using the Arc-based flow. Updates are orchestrated through the Lifecycle Manager, itself a cloud-managed service. Monitoring telemetry flows through Azure Monitor. The VM management experience in the Azure portal has improved to the point where it’s a credible primary interface for day-to-day operations.
The 2603 OS update - moving every deployment, new and existing, to 26100.32522 - reinforces this. There’s now a single OS baseline across the platform, managed and distributed through Azure. The OEM path for integrated systems (download from the Azure portal, work with your OEM on drivers) formalises this operational model.
Why This Matters for Enterprise Deployments
The shift to cloud-operated isn’t just an architectural preference. It has real operational consequences.
It reduces the local skills burden. Managing Azure Local through the Azure portal, Azure Monitor, and Azure Policy is substantially more accessible than the equivalent PowerShell and WAC workflows. Teams that are already Azure-fluent can operate the platform without deep HCI-specific knowledge.
It changes the dependency model. A cloud-operated platform needs reliable cloud connectivity. For deployments where internet connectivity is intermittent or restricted, this creates friction. Microsoft has addressed this with the disconnected operations model for sovereignty scenarios, but most enterprise deployments in regional offices and secondary datacentres need to think carefully about what happens to management workflows when the Azure connection is slow or unavailable.
It tightens the support story. When deployment, updates, and monitoring all flow through Azure, Microsoft has much better visibility into what’s running and where problems are occurring. That’s good for support outcomes, but it also means your cluster’s operational state is increasingly visible to Microsoft as a matter of function rather than opt-in telemetry.
It accelerates the pace of feature delivery. Decoupling features from OS updates - a design principle established in 23H2 - means Microsoft can ship capabilities through Arc Extensions without requiring OS updates. The cloud-operated model extends this: Microsoft can update the management plane, improve monitoring capabilities, and adjust deployment workflows without customers needing to do anything.
The AKS Picture
The Kubernetes updates in 2603 are worth noting separately. Supporting Kubernetes versions 1.31 through 1.33 keeps the platform current with upstream Kubernetes, and the addition of version 1.33 - which reached GA upstream in early 2026 - suggests Microsoft’s alignment with the Kubernetes release cycle is improving.
The KMS v2 migration is significant for anyone running AKS workloads at scale. KMS v1 provided encryption key management for Kubernetes secrets, but v2 is the current standard with better performance and security characteristics. The guidance to redeploy clusters using KMS v2 is operationally disruptive - this is a redeploy, not an upgrade - but it’s the right move. If you’re running AKS on Azure Local, this should be on your planning horizon now.
The deprecation of Windows Server 2019 node pools is less surprising. The focus for Windows containers on Azure Local has been Windows Server 2022, and that’s where enterprise workloads should be targeting.
What 23H2 End of Support Means
A separate but related point: Azure Stack HCI, version 23H2 OS reaches end of support in April 2026 - now. If you’re still on 23H2, the window has closed.
The 23H2 feature release train ended with the October 2025 release (version 11.2510). The 24H2 OS baseline has been the active development target for several releases. If you haven’t completed the upgrade planning work, this is now urgent rather than optional.
The upgrade path from 23H2 to 24H2 is documented and tested, but it requires planning. Start there.
The Honest Assessment
Azure Local 2603 is a maintenance release with strategic weight behind it. On its own, the feature list is incremental. In the context of where the platform has come from and where it’s going, it’s another step in a deliberate march toward a cloud-operated infrastructure model.
For operators, this is largely good news. The platform is getting simpler to manage, more consistent in behaviour, and better integrated with the Azure toolchain. For architects, it requires honest thinking about connectivity, dependency, and what cloud-operated means for your specific environment.
The platform that existed when I first wrote about Azure Stack HCI 23H2 in 2024 looked like on-premises infrastructure with cloud integration bolted on. What exists now in 2026 looks like cloud infrastructure that happens to run in your datacentre. That’s a meaningful shift, and 2603 is another confirmation of the direction.
Deploying Azure Local on Dell AX hardware? The Dell Solution Builder Extension handles update orchestration and maintains solution-level validation through each release cycle. Worth understanding if you’re planning your 2603 update cycle.