Azure Virtual Desktop gives your people a full Windows desktop they can reach from any device, managed from one place in Azure. Run it on Azure Local and the session hosts and their data stay on your own hardware, which matters when latency, compliance, or sovereignty rule out a purely public cloud setup.
Remote and hybrid work is normal now, but not every organization can send desktops and data to a public cloud region. In manufacturing and the public sector, latency to the shop floor and control over where data sits are real constraints. AVD on Azure Local gives you managed, secure workplaces while the data stays local. With RDP Shortpath you cut latency to a few milliseconds, so the experience holds up even next to the production line.
You run the session hosts on your Azure Local cluster, next to your other local workloads, and manage them from the same Azure portal you use for everything else. Users get a consistent desktop on any device, IT keeps one way of managing them, and the data never leaves your environment. It fits neatly alongside a VMware exit, because the same hardware that replaces your hypervisor also carries your desktops.
Azure Virtual Desktop is Microsoft’s desktop virtualization service. The control plane runs in Azure; the session hosts, the machines your people actually work on, can run on Azure Local. With RDP Short path, traffic goes directly over your own network, which cuts latency to a few milliseconds. That’s what makes it workable next to a production line. The measurements are in the blog below.
Run a real workload with your own data, in our Technology Experience Center or on your own site. Seeing it work beats any presentation.

Yes. The session hosts, the machines your users actually work on, run on Azure Local in your own datacenter. The Azure Virtual Desktop service itself stays in Azure and brokers each connection, so the platform needs a connection to Azure for users to log on.

Yes. Azure Virtual Desktop delivers published desktops and applications with Microsoft's own tooling, without a separate Citrix layer. You manage it from the Azure portal, and with Windows 11 Enterprise multi-session several users share one session host.

Fast enough for work next to the line. Because the session hosts run on-site, traffic stays on your own network, and with RDP Shortpath latency drops to a few milliseconds. We measured it in practice; the numbers are on our blog.

Sessions run on Azure Local, and user profiles and data sit on storage in or next to your Azure Local cluster, in your own datacenter. The Azure Virtual Desktop service in Azure does keep some service and diagnostic data, such as host pool settings and connection logs.

There are three parts: user access rights to Azure Virtual Desktop, the Azure Local service fee, and an Azure Virtual Desktop fee per active vCPU on your session hosts. The licenses that give users access to Azure Virtual Desktop in Azure, such as most Microsoft 365 E3 and E5 plans, also cover it on Azure Local.

Yes. Session hosts on Azure Local can use GPUs, so users can run CAD and other graphics-heavy software from a virtual desktop. We've set this up for several customers.


Control over where your data lives, provable to auditors, NIS2 regulators, and your board.

Hardware up for renewal and VMware costs climbing? Modernize instead of renewing the same setup.