By Francesco Molfese and Silvio Di Benedetto
Co-authors of Azure Local Unleashed
In many infrastructure conversations, the first question is still, “Should this workload run in the cloud or on-premises?” It sounds reasonable, but it is often the wrong starting point. Most organizations already operate across both worlds. A more useful question is: how can each workload run where it creates the most value while management, security, and governance remain consistent?
This is where Azure Local becomes particularly relevant. It is not simply a new destination for virtual machines. Although it often enters the conversation during a hardware refresh, its value extends well beyond infrastructure replacement. As part of Microsoft’s adaptive cloud approach, Microsoft brings Azure capabilities to customer-controlled environments.
Figure 1. Azure Local enables organizations to run workloads where they make the most sense while maintaining a cloud-consistent operating model.
Hybrid is no longer a temporary phase.
For years, hybrid infrastructure was described as an intermediate step on the journey to the public cloud. Real-world projects have shown something different.
Some workloads move easily to the cloud, while others must remain close to users, factories, or regulated data. Latency, data residency, dependencies, predictable capacity, and business continuity all influence the decision.
Modernization is not the same as relocation.
A workload can remain on-premises and still adopt cloud operating principles. It can be automated, governed through policy, monitored centrally, and integrated into a common security model. The value of hybrid infrastructure comes from applying these capabilities consistently across locations rather than forcing every application into the same destination.
Azure Local goes beyond virtualization.
Azure Local builds on a hyperconverged foundation that combines compute, storage, and networking. That foundation matters, but the strategic value lies above the infrastructure layer.
The platform allows organizations to run virtual machines, containerized applications, and selected Azure services locally using familiar Azure tools and management patterns. This changes the conversation from “Which hypervisor should we use?” to “Which operating model do we want across our infrastructure?”
A hybrid platform must go beyond server consolidation by supporting lifecycle management, governance, security, observability, and application modernization across distributed environments.
Cloud-consistent management is the real differentiator.
The hardest part of hybrid IT is rarely deploying a single cluster. Complexity appears later, when environments grow, configurations drift, responsibilities fragment, and each site develops its own procedures.
Azure Arc addresses this challenge by extending Azure management, security, and governance capabilities to resources outside the public cloud. Servers, Kubernetes clusters, and other resources can be managed through Azure’s control plane.
Workloads continue to execute locally, close to users and data, while policies, inventory, monitoring, and security controls can be applied consistently. This reduces the risk of turning every location into an isolated operational island.
Figure 2. Workloads execute locally, while governance, security, monitoring, and policy remain centrally coordinated.
Consistency does not mean cloud and on-premises environments become identical. The goal is to use a common management language wherever possible, reducing the exceptions that infrastructure teams must maintain.
Modernize at the right pace.
Azure Local supports gradual modernization. Organizations do not need to redesign every application before gaining value.
Existing workloads can initially run as virtual machines, preserving compatibility and reducing migration risk. When applications are ready to evolve, Azure Kubernetes Service, enabled by Azure Arc, can provide a consistent Kubernetes experience on Azure Local.
Azure Virtual Desktop can also place session-host virtual machines on Azure Local when performance, application proximity, or data locality requirements make local execution preferable.
Legacy applications, containerized services, and virtual desktops can share the same platform while evolving at different speeds. Modernization becomes a controlled journey rather than a disruptive event.
A practical placement framework
Before deciding where a workload should run, we recommend evaluating a few practical questions.
Does the application require predictable low latency or proximity to local systems? Must data remain within a specific physical, organizational, or regulatory boundary? Can the workload continue operating if cloud connectivity is degraded? Is the application ready for containers, or does it still depend on virtual machines? Does its demand profile favor owned capacity, cloud elasticity, or both?
These questions lead to better decisions than a generic cloud-first or on-premises-first policy and make placement easier to review as requirements evolve.
The goal is not to select one permanent destination, but to create a platform where placement becomes a deliberate and reversible decision.
Turning a hardware refresh into a modernization opportunity
Azure Local often enters the conversation during a hardware refresh, and this is a valid starting point. Replacing aging infrastructure can address capacity, performance, supportability, lifecycle, and operational risk.
The missed opportunity is not the refresh itself but stopping there.
Figure 3. A hardware refresh can become the starting point for broader infrastructure, operational, and application modernization.
If the project focuses only on replacing an existing virtualization cluster, the organization may solve an immediate problem while reproducing the same operational silos on a newer platform. Monitoring, security, governance, updates, automation, and workload deployment may still depend on fragmented tools and site-specific procedures.
A hardware refresh can instead become the catalyst for broader modernization: defining how resources will be governed, how policies and security controls will be applied, how updates will be orchestrated, and how workloads will evolve.
Hardware sizing, networking, storage design, and migration planning remain essential, but they should support a broader operating model. This is where Azure Local delivers its greatest value: not simply by replacing infrastructure, but by creating a more repeatable, governable, and cloud-consistent foundation for hybrid IT.
Final thoughts
Azure Local reflects a wider change in enterprise IT. The future is not simply public cloud replacing the datacenter, nor is it a return to traditional on-premises infrastructure. It is a model in which workloads are placed deliberately and managed through a more consistent control plane.
That is also the central idea behind Azure Local Unleashed, the book we wrote together. We did not want to create an installation manual. Our goal was to explain the strategy, architecture, operating model, and real-world decisions behind Azure Local.
For architects, infrastructure leaders, platform engineers, and IT decision-makers, the key lesson is straightforward: modernize the operating model, not only the hardware. When workload placement, governance, security, and lifecycle management are designed together, hybrid infrastructure stops being a compromise and becomes a deliberate foundation for long-term evolution.
