Virtual desktop infrastructure for SMBs: when it pays off, and when it is over-engineering

Virtual desktop infrastructure gets pitched as the answer to every endpoint headache: lost laptops, patching sprawl, data walking out the door. Sometimes it is. More often, for a small or mid-size office, a well-managed laptop is faster, cheaper and less fragile than a virtual desktop — and the VDI bill arrives mostly as Microsoft licensing nobody budgeted for. We run Windows Server RDS, Azure Virtual Desktop and self-hosted desktops on Proxmox for clients, so here is the honest version: what a virtual desktop actually is, the specific reasons to build one, and the reasons not to.

Three different things people call a virtual desktop

Most confused VDI conversations are two people meaning different things. There are three models, and they differ in cost, isolation and who operates them.

• •Session-based (RDSH). Many users share one Windows Server and each gets a session, not a machine. This is classic Remote Desktop Services (terminal services). It is the cheapest per seat because one server carries dozens of light users, and the weakest on isolation — everyone is on the same OS.
• •Client VDI. Each user gets their own virtual machine running a Windows client OS. Stronger isolation and a desktop that feels personal, at a real cost in compute and licensing — one VM per person instead of one server for many.
• •DaaS (Cloud PC). Someone else runs the infrastructure and you rent desktops by the seat — Windows 365, or a managed Azure Virtual Desktop, or Omnissa Horizon / Citrix in their cloud. Least to operate, priced per user.

The cost ladder runs RDSH (cheapest, shared) → client VDI (dearer, isolated) → DaaS (simplest to run, per-seat). Reaching for client VDI or DaaS when shared sessions would do is the most common way the budget doubles. We compare the concrete products — Windows 365, Azure Virtual Desktop, RDS and self-hosted — in picking a virtual desktop stack.

When a virtual desktop actually pays off

A virtual desktop earns its complexity when something about the work breaks the laptop model. If none of these is true, buy laptops and a decent MDM and stop reading.

• •Shift workers who share devices. Call centres, clinics, shop floors, warehouses — three people using one screen across a day. A session that follows the person, not the hardware, is the whole point of RDSH, and this is where it shines.
• •Data that must not leave. Regulated records, client data, source or design IP. By default only screen pixels travel to the endpoint and the files stay in the datacentre, so with clipboard, drive-mapping, printing and downloads locked down a lost or stolen device holds little or nothing sensitive. It reduces exposure rather than eliminating it, and pairs with the controls in an Entra ID and Microsoft 365 hardening pass.
• •Contractors, BYOD and short engagements. Standing up a desktop for a three-month contractor on their own laptop, then deleting it cleanly, beats shipping and recovering hardware.
• •A heavy application that lives next to its data. Large CAD, GIS, BI or analytics datasets are painful to pull down to a laptop. Put the desktop next to the data and move pixels instead of gigabytes.
• •One image instead of two hundred laptops. Patch, configure and secure a handful of golden images rather than chasing every endpoint. The control story is real — it is just not free.
• •Seasonal or burst capacity. Tax season, enrolment, a project team that triples for a quarter. Spin desktops up and down instead of buying hardware that sits idle for nine months.

When it is over-engineering

The same honesty in the other direction. A virtual desktop is the wrong tool when:

• •You have a small, stable team of individual knowledge workers. Good laptops, disk encryption, MDM and cloud apps already solve what VDI would solve, with less to break.
• •People work offline or on bad links. A virtual desktop is useless without a connection, and painful on a flaky one. Latency-sensitive and creative work (video editing, heavy design) needs GPU-backed VDI or it will frustrate everyone.
• •Your apps and data are already SaaS. If the work lives in a browser and Microsoft 365, a managed laptop reaches it directly. Adding a virtual desktop in front is a layer that only adds cost and a dependency.
• •You cannot run it to a high standard around the clock. This is the big one, below.

A virtual desktop concentrates risk. Two hundred laptops fail one at a time; a broker, host pool or connection outage takes everyone offline at once. You are trading distributed, survivable endpoints for one thing that must not go down — so budget for its high availability, its backups and its restore test, or do not build it. The failure-testing discipline we apply to database clusters applies here too.

The licensing reality that surprises people

The hardware or Azure bill is rarely the shock. Microsoft licensing is. Price the licences before the servers, because they often decide the model.

• •Windows Server RDS needs three things, not one: a Windows Server licence, a Windows Server CAL per user or device, and an RDS CAL per user or device. The RDS CAL alone budgets at a few hundred per user, and it swings widely with the agreement, Software Assurance and region — get a current quote rather than trusting a headline figure.
• •Running Windows client VMs on your own hypervisor is not covered by OEM or retail Windows. The legal route is Windows Enterprise E3/E5 per user or a Windows VDA subscription, and the right is assigned to the user, not the VM. Treating an OEM key as a VDI licence is a compliance landmine.
• •Azure Virtual Desktop desktop rights are included with Microsoft 365 Business Premium, E3/E5, F3, or Windows Enterprise E3/E5 / VDA — but AVD still bills Azure compute, disks, profile storage and networking separately. There is no single per-user AVD price. Do not assume every Microsoft 365 plan qualifies; the lower-tier and standalone plans do not.
• •Windows 365 is the exception that is simple to price: a fixed per-user, per-month Cloud PC. A 2 vCPU / 8 GB / 128 GB Cloud PC lands on the order of US$30–45 per user per month depending on edition and commitment, rising as you add CPU, memory and storage. Check Microsoft's current pricing for your edition and market rather than a headline number.

A rough cost sanity check

Before committing, put the real seat cost of each model next to a laptop. The point is not a precise quote — it is to see which shape fits your team, because the cheapest per seat at ten users is rarely the cheapest at two hundred.

How we approach it

We start from the trigger, not the product. Name the one thing that breaks the laptop model — shared devices, data residency, a heavy app, burst capacity — and pick the lowest-complexity model that answers it. In practice that means RDSH or Windows 365 for most small offices, Azure Virtual Desktop when there is already an Azure footprint and real session density to exploit, and self-hosted only when sovereignty or cost justify owning the whole stack and the team can actually run it. If you are already re-platforming — say, leaving VMware after the Broadcom changes or retiring Windows Server 2016 — fold the desktop decision into that project rather than bolting it on later. The next step once the model is chosen is the product and licensing detail, which is its own comparison. This is part of our server and virtualisation work and our infrastructure services.