Azure Virtual Desktop and hosted desktops: when they make sense

What a hosted desktop actually is

Instead of Windows running on the laptop in front of you, it runs on a virtual machine in a data centre. The laptop, a thin client or even a tablet acts as a window: it shows the screen and passes through keyboard, mouse, printing and sometimes audio. Close the connection at the office, open it at home, and the same desktop appears exactly as you left it.

Azure Virtual Desktop is Microsoft's version, running in Azure, and it can let several users share one larger Windows machine, which reduces cost. Other providers offer similar hosted desktops built on their own platforms. The idea is the same in each case: the work happens in the data centre, not on the device.

Situations where it works well

The strongest case is a line-of-business application that must run near its database. A construction firm with a job costing system on a server, or an accounting practice with desktop tax software, can host both the database and the application together, so staff at home or on site get the same speed as in the office. Without that, remote users may be stuck with slow VPN connections to a database designed for the local network.

Hosted desktops also suit businesses with seasonal or contract workers who use their own devices, because nothing is stored on the personal laptop. When the contract ends, you remove their access and there is no data to retrieve. Call centres, branch offices and teams that hot-desk across sites can benefit in the same way.

Where it is the wrong tool

If your staff mainly use Outlook, Teams, a browser and cloud apps such as Xero, a hosted desktop adds cost and complexity for little gain. Those apps already work from anywhere. Video calls through a hosted desktop need extra configuration to perform well, and graphics-heavy work such as design or CAD needs expensive GPU-equipped servers. Hosted desktops also depend entirely on the internet. If the connection drops or is poor, the user cannot work at all, whereas a laptop with synced files can carry on offline. People on patchy rural connections or working from vehicles tend to find them frustrating.

The costs to weigh

You pay for the virtual machines while they run, the storage for user profiles, the licences that allow Windows to be used this way and the setup work. Some Microsoft 365 plans include the right to use Azure Virtual Desktop, but compute and storage are billed separately; check current licensing terms because they change. Automatically shutting down or scaling back servers outside working hours makes a large difference to the monthly bill.

Staff still need a device to connect from, though it can be modest. In some cases a business can extend the life of older PCs or buy cheaper devices, which offsets part of the hosting cost. Compare the full monthly cost per user against the alternative of laptops plus a server or a cloud version of your software.

Getting the experience right

A poorly set up hosted desktop feels sluggish, and staff will hate it. Locate the servers in the nearest region, size them for the real workload, test printing, scanning and any USB devices early, and make sure profile storage is fast. Run a pilot with a few staff for a couple of weeks before moving everyone, and listen to their complaints rather than explaining them away. Security needs attention too: multi-factor sign-in on every connection, limits on copying data to personal devices if that matters to you, and regular patching of the hosted Windows machines, which are still computers that need care.

A simple test before you commit

Before signing up, write down the three or four tasks that matter most to your staff: entering a timesheet, running the month-end report, printing a delivery docket, joining a client video call. Have a pilot group do exactly those tasks on the hosted desktop from the office, from home and from a phone hotspot. Measure how long they take compared with today. If the important tasks are as quick or quicker and nothing breaks, you have real evidence to justify the change.

Ask the pilot group about the small irritations as well: a second sign-in screen, a printer that appears with the wrong name, a keyboard shortcut that behaves differently. These rarely kill a project on their own, but together they decide whether people accept the new setup or quietly work around it. Fix them before the wider rollout, and give everyone a one-page sheet showing how to connect and who to ask when it does not work.