Virtualization and hybrid cloud: what the new Magic Quadrants tell us about Microsoft

In September 2026, Gartner published the new editions of two reports that are particularly relevant for anyone shaping the future of their IT infrastructure: the Magic Quadrant for Distributed Hybrid Infrastructure, published on September 7, and the Magic Quadrant for Server Virtualization Platforms, published on September 14. Microsoft is positioned as a Leader in both, with an evaluation that covers Azure Local, Azure Arc and Windows Server 2025 Hyper-V according to the scope of each analysis.

Reading these two reports together offers, in my view, an interesting perspective: choosing a virtualization platform and defining a hybrid operating model are increasingly connected decisions. Azure Local holds a significant position precisely where these needs meet.

The Distributed Hybrid Infrastructure quadrant, or DHI, examines the platforms that make it possible to distribute infrastructure and services across datacenters, edge sites and public cloud while maintaining coordinated control. The central theme is the ability to apply cloud principles, such as automation and API-based management, in customer-controlled environments as well.

The Server Virtualization Platforms quadrant focuses instead on the platforms used to run and administer virtual machines: hypervisor, centralized management, live migration, security, and integration with storage and networking. Its scope therefore covers the capabilities required to manage a virtualized environment over time. The two analyses address complementary needs, with distinct criteria and areas of evaluation.

In the DHI, Microsoft’s evaluation covers Azure Local and Azure Arc. Gartner highlights the unified architecture of the offering, its growing adoption and the flexibility between hyperconverged and disaggregated configurations, with the option to scale compute and storage separately. It also points out aspects to consider: implementation complexity, the requirements of the new multi-rack configurations, and the still-evolving maturity of some local AI capabilities.

Microsoft also points out that it has been recognized as a Leader in this market for the fourth consecutive year, with the highest position on the Ability to Execute axis. This result refers specifically to the DHI quadrant, and it helps to put into context the continuity of investment in distributed infrastructure. Microsoft announcement.

In the quadrant dedicated to server virtualization, Gartner evaluates Azure Local and Windows Server 2025 Hyper-V. Among the strengths, it cites the hybrid capabilities enabled by Arc, the ecosystem of enterprise integrations and the investments in infrastructure security. The areas to watch include the presence of multiple administrative consoles, the dependency on Azure for some hybrid functionality, and the operational impact of Windows Server updates. Gartner analysis of Microsoft. On this point, I think it is worth adding a personal consideration: as of today, the main weakness of Windows Server 2025 with Hyper-V remains the overall management of the ecosystem, especially for organizations that want to keep a fully on-premises infrastructure without adopting a hybrid model. Windows Admin Center offers important capabilities; in my view, however, what is still missing is a management experience able to bring together maturity, simplicity and operational consistency at a level comparable to what vCenter represents in the VMware ecosystem. This aspect weighs on the evaluation of the platform, because it has a direct impact on administrators’ day-to-day work.

Microsoft is working on this need, as shown by the introduction of Windows Admin Center Virtualization Mode, dedicated to the centralized management of Hyper-V hosts, clusters and infrastructure resources. I see this evolution as a positive signal, and I am confident that further news will arrive soon, making the management of Microsoft virtualization more complete and consistent, including for those who favor an on-premises operating model. Microsoft deep dive on Virtualization Mode.

This dual presence helps to appreciate the breadth of Microsoft’s offering. To translate it into architectural choices, however, it is useful to distinguish the role of each technology:

Technology	Role in the architecture
Hyper-V	The virtualization technology at the foundation of Windows Server and a core component of Azure Local.
Windows Server 2025 with Hyper-V	Provides a platform for hosting VMs with infrastructure flexibility and local management, extensible through Azure services.
Azure Local	Provides an infrastructure platform for running workloads at customer sites, integrating management and lifecycle with the Azure ecosystem.
Azure Arc	Extends Azure management and governance capabilities to servers, Kubernetes and other distributed resources, according to the supported functionality.

The strategic value of Azure Local comes from the connection between running workloads locally and an operating model integrated with Azure. Applications and data can reside in the corporate datacenter, in a branch office or in a plant, while the platform introduces experiences and tools consistent with those of the cloud. Latency, operational continuity and local control thus become elements of the design.

Azure Arc broadens this perspective, making it possible to bring distributed resources into a common model of inventory, organization and control. For an organization with many sites, this can translate into the ability to apply shared policies and make management more uniform. How far these capabilities actually extend depends on the type of resource and on the services adopted.

My reading of Microsoft’s positioning is therefore that of an offering able to support different needs: maintaining and renewing existing virtualization, introducing an on-premises platform integrated with Azure, and building broader governance of the distributed environment. Each organization can assess the path in light of its own applications, the skills available and its operational objectives.

This becomes particularly concrete when a project starts from an infrastructure refresh. Replacing a cluster is an opportunity to examine provisioning, monitoring, updates, data protection and recovery procedures as well. It is on these processes that a substantial part of the benefit of a new platform is measured.

For example, a manufacturing company could keep latency-sensitive applications close to production while adopting common management policies across multiple plants. An organization with numerous branch offices could focus on standardizing configurations and reducing manual activities. In both cases, the assessment should start from application requirements and include total cost, functionality, connectivity and operational responsibilities.

This is also a perspective that runs through Azure Local Unleashed: Modernizing Hybrid Infrastructure with Cloud-Consistent Management and Governance, the book I wrote together with Silvio Di Benedetto. In the book we approach Azure Local by connecting architecture, management and strategic decisions: where to run workloads, how to protect them and how to govern their evolution. The reference to cloud as an operating model, extensible to different contexts, is one of the themes that make reading these two quadrants together particularly interesting. For those planning their next investments, the Gartner reports are a starting point to be paired with a check against concrete needs. Microsoft’s positioning brings a specific possibility into focus: connecting the virtualization refresh to a broader evolution of infrastructure management, while preserving the freedom to place workloads where they best meet the needs of the business.