Microsoft’s Azure Virtual Desktop (AVD) now supports Azure Arc–enabled on-premises servers as session hosts, marking a notable development in desktop virtualisation. This enhancement is especially advantageous for organisations with strict compliance needs, fluctuating network conditions, or substantial VMware and Nutanix investments that have, until now, limited cloud migration efforts.
In this model, management, brokering, and identity services are delivered from Azure, while desktops and applications can run much closer to the end users and their sensitive data. The arrangement provides technical flexibility, allows organisations to maximise previous investments, and addresses regulatory demands—all without the upheaval associated with full-scale cloud migration.
AVD session hosts are no longer limited to Azure-based virtual machines. Supported platforms now include physical servers, Hyper-V, VMware vSphere, and Nutanix AHV virtual machines, provided the Azure Arc Connected Machine agent is installed. Key cloud-based services such as brokering, identity management via Microsoft Entra, policy enforcement, and workspace delegation remain centrally managed from Azure, while user sessions execute on-premises. Separating the control plane from the data plane creates a stronger security posture and facilitates more consistent performance management.
Responsibilities such as provisioning, updating, and imaging of these hybrid session hosts do not fall to Microsoft. Organisations must implement their own solutions, whether by partnering with third-party providers such as Nerdio, ControlUp, LoginVSI, or Nutanix, or by developing in-house automation. The current public preview includes support for Windows Server 2016 through 2025 and Windows 11 Enterprise (single session only). Multi-session support is not yet available, which is significant for those optimising for user density and cost efficiency.
Enterprises with demanding data residency or compliance requirements can now retain both sessions and data entirely on premises, yet benefit from centralised Azure management. Organisations leveraging a mix of hypervisors have a clear path forward to modernise desktop access without committing fully to native Azure infrastructure. For high-latency sensitive applications—such as computer-aided design, local branch operations, or real-time collaboration—keeping workloads local while managing access and policy from the cloud introduces significant operational flexibility. This also enables staged approaches to migration, blending on-premises and cloud resources as business priorities shift.
Operational considerations must be addressed. Multi-session limitations will require fresh thinking on capacity and budgeting. Reliability depends on third-party or in-house lifecycle management solutions, and stable, persistent connectivity is non-negotiable—outages affecting either the Arc agent or AVD broker will impact user access. IT and finance teams must also plan for evolving cost structures associated with AVD hybrid deployments.
Expanding AVD with Azure Arc offers IT teams strategic options, particularly in regulated or complex enterprise contexts. Success with this approach requires strong coordination across network, security, and operations disciplines. Whether lifecycle management is handled internally or with partners, new operational practices will be essential for consistent service delivery.
Read the original source at windowsforum.com.
