Will Azure Virtual Desktop Cost Less Than Your Laptops?

Azure Virtual Desktop can cost less than the desktops it replaces, but only when four things are designed deliberately: how many users share each session host, how much capacity is reserved, how much is switched off outside working hours, and where user profiles are stored. Deployed on default settings, it can just as easily cost more.

The short answer

Cloud desktops work. That question was settled years ago. The question worth asking before you commit is whether your design will cost less than the alternative: the laptops and desktops you buy, patch and secure today, or a fixed per-user Cloud PC such as Windows 365.

Azure Virtual Desktop is billed on the Azure infrastructure underneath it. You pay for the virtual machines, their disks, the file storage that holds user profiles, and networking. That makes the bill flexible in both directions. A well-sized deployment shares compute across many users and switches most of it off at night. A poorly sized one runs oversized machines around the clock for a handful of people.

What you are actually paying for

For internal staff, most organisations do not pay a separate Azure Virtual Desktop access fee. Microsoft lists Microsoft 365 Business Premium, E3, E5, F3, A3 and A5, Windows Enterprise E3 and E5, and Windows VDA per user among the licences that already entitle users to Azure Virtual Desktop on Windows client session hosts. If your staff hold one of those, the cost conversation is almost entirely about Azure infrastructure.

That infrastructure falls into three buckets:

• Compute: the session host virtual machines, charged while they are running.
• Storage: the operating system disk of each session host, plus the file share that holds user profiles.
• Networking and supporting services: outbound data, and anything else the design adds, such as backup or monitoring.

Compute is usually the largest line, which is why three of the four levers below are about it.

Lever one: session density

Windows multi-session lets several users share one virtual machine, and how many share it is the single biggest factor in cost per user. Microsoft's own sizing guidance gives starting points per virtual CPU: up to six users for light workloads such as data entry, four for medium, two for heavy and one for power users.

Those figures are ceilings for an initial estimate, not targets. Microsoft recommends validating them with a pilot or a load simulation, watching processor, memory and disk as users are added, and leaving headroom for the morning logon rush. It also notes that several smaller session hosts usually perform better than one very large one, and are easier to switch off when idle.

The cost trap runs both ways. Put too few users on each host and you pay for idle cores. Put too many on and staff get slow sessions, complain, and the deployment is quietly upsized to machines that never come down again.

Lever two: reserved instances

Virtual machines that run every working day for a year are cheaper to reserve than to pay for by the hour. Azure Reserved Virtual Machine Instances are bought for one or three years. Microsoft quotes savings of up to 72 percent against pay-as-you-go, with its published range running from about 36 to 72 percent depending on the machine, region and term; the top figure is for a three-year Linux reservation. A monthly payment option is available, so the commitment does not have to be paid upfront.

A reservation is billed whether the machine runs or not. That makes it the right tool for your baseline, the session hosts that are on every working day, and the wrong tool for capacity that auto-scaling switches off at night and at weekends. The practical pattern is to reserve the floor and pay as you go for the peaks above it. Check the current exchange and cancellation terms before you commit.

Lever three: auto-scaling outside working hours

An office that works nine to six, Monday to Friday, uses its desktops for roughly a quarter of the hours in a week. Paying for compute around the clock means paying for the other three quarters as well.

Azure Virtual Desktop handles this with autoscale scaling plans. A plan divides each day into four phases, ramp-up, peak, ramp-down and off-peak, and for each one sets how many hosts must stay on and the capacity threshold that triggers adding or removing hosts. When hosts are not needed, autoscale shuts them down and deallocates them, so you stop paying for their compute. Scaling plans work for pooled host pools and for personal ones, where each user has their own machine.

Two details matter. Deallocated machines still carry their disk charges, so storage does not drop to zero. And the off-peak floor should be set on purpose: one small host for late workers costs far less than leaving the whole pool on just in case.

Lever four: profile storage design

In a pooled deployment, users do not own a machine, so their profile has to follow them. FSLogix profile containers do that by keeping each profile on a file share and attaching it at sign-in. Where that share lives affects both the bill and the logon experience.

Microsoft recommends Azure Files for most customers. Its guidance is that light workloads under about 200 users can run on the Standard tier, which is billed on data stored and transactions, while medium and heavier workloads should use Premium. Premium is provisioned, so you pay for the capacity you set aside whether or not it is used. Azure NetApp Files offers higher performance but starts at a 1 TiB capacity pool, which is often more than a small organisation needs.

Over-provisioning premium storage to be safe is one of the quieter ways a deployment ends up costing more than planned. Under-provisioning shows up as slow logons, which users then blame on the whole platform.

A cost review in six steps

1. Group users by workload. Separate data entry, general office and specialist users before sizing anything.
2. Pilot one host pool. Measure real sessions per host under load, including the morning logon peak.
3. Set the scaling plan from actual hours. Base ramp-up and ramp-down on when people really sign in and out.
4. Reserve only the baseline. Commit to the hosts that run every working day and leave the peaks on pay-as-you-go.
5. Size profile storage to the tier you need. Start with the smallest tier that keeps logon times acceptable, then monitor.
6. Review after the first full month. Compare the bill with the plan and adjust density, schedules and reservations.

When a fixed per-seat price is the better choice

Azure Virtual Desktop rewards organisations that can share machines and keep regular hours. If every user needs a dedicated desktop, hours are unpredictable, or you would rather have one predictable monthly figure than an infrastructure bill to manage, a fixed per-user Cloud PC such as Windows 365 can work out cheaper once management time is counted. We compared the two in Azure Virtual Desktop vs Windows 365: Which Cloud Desktop to Choose.

Frequently asked questions

Is Azure Virtual Desktop cheaper than Windows 365?

It can be, when users share session hosts and hosts are switched off outside working hours. For dedicated desktops running long hours the gap narrows, and a fixed per-user Windows 365 licence can be the simpler, more predictable choice.

Do we need extra licences to use Azure Virtual Desktop?

Usually not for internal staff. Microsoft 365 Business Premium, E3, E5, F3, A3 and A5, Windows Enterprise E3 and E5, and Windows VDA per user already include access on Windows client session hosts. You still pay for the Azure infrastructure, and access for external users is priced separately.

How many users can share one session host?

Microsoft's starting guidance is up to six users per virtual CPU for light work, four for medium, two for heavy and one for power users. Treat those as upper limits and confirm them with a pilot.

Do we pay for session hosts when they are switched off?

Not for compute, once autoscale has deallocated them. Their disks are still billed, and reserved instances are billed whether the machine runs or not.

Should we buy reserved instances straight away?

Not before you know your baseline. Run on pay-as-you-go long enough to see how many hosts are on every working day, then reserve that number.

Where to start

Onprem2Cloud IT Solutions Co. is a Microsoft CSP partner based in Muntinlupa City, Metro Manila. We size and tune Azure Virtual Desktop environments rather than just deploying them: workload grouping, pilot testing, scaling plans, reservations and profile storage.

See our Azure Virtual Desktop service, or tell us about your current desktop setup and we will point out which of the four levers matters most for you.