From Legacy VDI and AVD to Windows 365
Assess which VDI and AVD user groups fit Windows 365, build a defensible TCO case, prepare legacy applications, and migrate without losing day-two ownership.
Find avoidable Microsoft 365 and Azure spend, agree changes with the right owners, and confirm the result before reporting savings.

35 pages. Reviewed 23 August 2026.
Written by Ryan Mangan at EfficientEther.
Walk into the renewal meeting with a cost baseline that finance and IT both accept.
Most Microsoft renewals arrive with one number attached, the quote. The figures that would let you challenge it, purchased against assigned seats, real activity, service dependencies and the Azure resources still sized for last year's project, sit in separate reports owned by separate people. By the time they are assembled the renewal window has usually closed.
This handbook builds the baseline first, then works through licences and Azure separately, because the evidence and the owners are different. Chapter 1 sets the scope, the decision and the deadline before data collection starts. Chapter 2 separates what is purchased, assigned, active and required. Chapter 3 reduces Azure waste without creating service risk.
It also holds a hard line between an opportunity and a verified saving. Every worked quantity in the book is illustrative and is meant to be replaced with your own tenant, agreement and billing data, so the figure you report to finance is one your own evidence supports.
IT managers, Microsoft 365 administrators, Azure operations teams, finance partners, procurement leads and MSP practitioners preparing a renewal or a recurring cost review. Most useful to teams running tenants of roughly 50 to 600 users, where one person often covers several of those roles.
Get the handbookEtherInsights lists inactive and downgradeable seats and oversized Azure resources, each with a named owner.
14-day free trial on your own tenant, read-only by default. From £0.79 per licensed user per month.

Assess which VDI and AVD user groups fit Windows 365, build a defensible TCO case, prepare legacy applications, and migrate without losing day-two ownership.
The Windows 365 case stalls when the endpoint estate and the sizing evidence sit in different conversations. See how both ends close on one comparable term.
Purchased, assigned and actively used licences are not the same thing, and the evidence needed to act sits across billing, activity and identity reports. Build a reclaim list finance can approve and IT can defend before the next renewal.