The problem WTW set out to fix
WTW had a virtual desktop platform that had become costly, manual and slow to change. According to the story, costs were climbing, automation was too complicated, and the vendor was slow to act on requested improvements. The platform served roughly 15,000 users, and one engineer spent about half of every month preparing, publishing, staging and updating desktop images. Two other administrators then spent another six to eight hours moving those images into production during a monthly downtime window.
The trigger for change was WTW's move from on-premises data centers to the cloud. That gave the end-user computing team a chance to rethink desktop delivery. It wanted flexibility, pay-as-you-go economics, no long-term tie-in and much less manual work.
Why data location mattered
Many WTW staff around the world work on accounts for clients in North America. WTW says that data needs to stay in North America and not end up on a laptop thousands of miles away. Roger Stuart, Manager of Infrastructure Engineering, says AVD gives WTW that ability and that Azure regions help further. He also admits he was skeptical when WTW adopted AVD while the service was still young.
Be careful reading that as a product guarantee. Microsoft's documentation says:
- AVD's deployment scope is a separate matter from where user data lives. Microsoft says the service stores metadata, such as host pool and workspace names, in a geography or a single region depending on the deployment scope you choose.
- User-created and app-related data sits in whatever Azure region you choose and isn't managed by the AVD service.
- Microsoft also says it doesn't control or limit the regions from which users can reach that data.
So WTW's North America result comes from how it builds and governs its environment. It doesn't come from the AVD label alone. Virtual desktops keep data in the datacenter and send only pixels to the endpoint, which is the real mechanism at work.
Matching the desktop to the work
WTW looked at each workload and chose a different model for each.
| Workload | Platform | Why, per WTW |
|---|---|---|
| Large teams with defined jobs, including seasonal open-enrollment staff | AVD multi-session desktops | Several people share one VM, and the desktops are rebuilt monthly from a fresh company image |
| Developers and power users | Windows 365 Enterprise | Each person gets a personal cloud PC at a fixed monthly price |
Developers and power users previously had high-end machines that were expensive to run. IT couldn't tell when it was safe to shut them down. Stuart says the fixed monthly price meant WTW knew exactly what those machines would cost, however hard people used them.
Microsoft's Windows 365 documentation backs the product-level logic. Each Cloud PC is assigned to one user, uses Intune for management and AVD for remote connectivity, and is billed per user per month. That documentation says the model spares organizations from managing the variable compute and storage costs of a traditional hosted desktop.
The Windows 11 angle
The Windows 365 move doubled as the Windows 11 upgrade for those users. WTW didn't upgrade old machines in place. It provisioned new Windows 365 machines running Windows 11, with apps delivered through Intune as they would be on a laptop. Colin McGerty, Director of Infrastructure Engineering, calls Windows 365 the closest thing to a laptop in the cloud that WTW has deployed.
Don't read this as a Microsoft-mandated path. Microsoft's multi-session FAQ says in-place Windows upgrades aren't supported for session hosts in pooled host pools. WTW's developers weren't described as being on pooled hosts, so that rule isn't necessarily why it rebuilt their machines. It does show why a rebuild is the normal route for pooled environments.
Nerdio as the management layer
WTW runs AVD with Nerdio. Nerdio worked with WTW and Microsoft to design the AVD environment and wind down the old platform. Nerdio Manager for Enterprise is now the single management layer for both AVD and Windows 365.
- Nerdio builds golden images on a schedule, using one process for both services. New machines arrive with core apps already installed.
- Nerdio is WTW's first call when something breaks. It brings in Microsoft only when a fix needs the platform itself, so WTW isn't caught between two vendors.
- Nerdio's customer success manager says Windows 365 stayed an extension of the existing AVD environment, not a separate one to run.
The vendor relationship is worth noting. The story is a Microsoft showcase that features a Microsoft partner, and Nerdio sells the automation it is credited with. That doesn't make the numbers false, but it does shape what gets emphasized.
The reported results
Microsoft's story reports the following:
- Scale: about 9,000 daily AVD sessions, 15,000 monthly AVD users and about 1,700 people on Windows 365.
- Migration: roughly 500 workloads moved off the old platform before its licenses came up for renewal.
- Savings: about $2 million a year, plus an average 50% saving on AVD costs from Nerdio's auto-scaling compared with what WTW would spend without it.
- Admin time: the two weeks a month spent on images is gone, and the 6-8 admin hours a month are saved.
- Support: Windows 365 machines are managed and patched with Intune like any laptop. WTW handed their support from its virtual desktop team to its everyday end-user support team.
- Experience: one service center engineer estimates he regains about two hours a week since adding resources to his Windows 365 machine.
The story doesn't give a baseline for the $2 million, so the comparison is unclear. It also doesn't say how the 50% figure was calculated beyond "compared with AVD without auto-scaling."
Where it's heading
This year WTW moved several thousand open-enrollment call center agents onto AVD and secure thin clients. That is up from a couple of hundred in a 2025 trial. Developers with expensive, high-powered laptops are next. The team is also testing previews of upcoming Microsoft improvements to connection quality for colleagues in places like Mumbai and Manila. McGerty says business units now ask for these desktops first. He also says the platforms have expanded to developers, contractors, temporary staff and merger-and-acquisition onboarding.
Is the split a common pattern?
It appears to be. Several independent comparison guides, including ones from Nerdio itself, Venn and Apps4Rent, describe the same division. They use pooled AVD for variable or shared workloads and Windows 365 for steady users who want a predictable Cloud PC. Several of those guides come from vendors and managed service providers with their own interests, so treat their advice as general industry commentary. Even so, WTW's setup matches the standard advice.
Takeaways for IT admins
- Segment by workload. Shared, repeatable jobs suit pooled multi-session hosts. Users who install software or need more resources suit personal Cloud PCs. WTW's service center engineer notes that Windows 365 lets him install what he needs, while shared AVD pools carry the same software for everyone.
- Plan data residency deliberately. Choose regions for session hosts and storage, and check what your deployment scope does with metadata.
- Watch pooled-host isolation. Microsoft's security guidance warns against sharing multi-session hosts among users from different or competing organizations. WTW's story doesn't say how it separates contractors and third parties from employees, so don't assume they share hosts.
- Automate images. Image preparation was the biggest hidden labor cost in WTW's story, whatever tool you use.
- Treat vendor numbers as claims. The savings figures come from a Microsoft marketing story and aren't audited.
WTW's story is a case study, not a launch, and it announces no new feature. Its value is as a worked example of splitting cloud desktops by workload instead of choosing one product for everyone.
References
- Willis Towers Watson powers global work with Windows 365 and Azure Virtual Desktop - Microsoft Microsoft · Wed, 18 Nov 2026 10:02:57 GMT
- Windows Enterprise multi-session FAQ - Azure | Microsoft Learn learn.microsoft.com
- Data locations for Azure Virtual Desktop - Azure - Azure Virtual Desktop | Microsoft Learn learn.microsoft.com