Windows Virtual Desktop is being rebranded Azure Virtual Desktop (AVD). Renames are marketing until they are strategy — and this one is strategy. Microsoft is planting desktop virtualization inside the Azure brand next to the rest of the control plane. This closing note of our 2016–2021 archive arc is a look back across five years of VDI work — XenDesktop LTSR, RDS, WVD preview and GA, spring ARM update — and where the practice goes next under the AVD name.
Why the name matters
“Windows Virtual Desktop” sounded like a Windows feature. Azure Virtual Desktop sounds like an Azure service line — identity, monitor, network, cost, policy. That matches how we already operate production pools: as Azure applications with session hosts, not as a side appliance.
Expect docs, portal labels, and partner materials to shift. Architecture principles do not reset on rename day.
The arc we lived
- Citrix XenDesktop 7.x LTSR — density, HDX, ops maturity for large concurrent estates
- RDS 2012 R2 + App-V — pragmatic session hosts when full VDI was overkill
- WVD announce (2018) / preview (2019) / GA (2019) — multi-session Windows 10 in Azure
- FSLogix acquisition — profiles taken seriously
- Spring ARM update (2020) — portal-native host pools
- COVID surge (2020) — capacity and path optimization under fire
- AVD name (2021) — Azure-first branding
Availability targets, profile math, and image factories remain the job.
What we will not forget
- Profiles and storage decide user experience more than protocol brand
- N+1 and patch drains are HA, not waste
- Identity is tier-0 for desktops too
- Cost visibility without ownership is just a surprise bill
- Citrix still wins some UX and complexity contests — choose on requirements
Where the practice goes next
AVD will keep absorbing Microsoft investment. Hybrid management, broader client OS options, and deeper Azure integration will continue. Our work stays the same: design pools that meet SLAs, land identity correctly, tune FSLogix, control cost, and hand over runbooks customers can operate.
The archive from 2016 mailbox assessments through 2021 AVD is one story: production systems under real constraints. Tools change names. Discipline does not.
Extended practice notes (2021)
The remaining gap between a short checklist and a usable field note is usually scenario detail. In practice, the same engagement type described above still requires explicit answers to: what is in scope this quarter, what is deferred with a date, who can halt a wave, and how success is measured in production — not in a lab.
We document those answers before the first production change. When stakeholders disagree, the disagreement is resolved in writing, not on the bridge at cutover. That habit is independent of whether the workload is mail, identity, virtualization, desktop delivery, or security hardening.
Repeatable detail also includes communication: who tells users what changes, when the freeze starts, where status is posted, and how exceptions are requested. Technical excellence without communication still produces an outage from the user's point of view.
If you're facing this
If the AVD rename triggered a new mandate without a design, start from requirements and a pilot metric, not from the logo. We design Azure Virtual Desktop and Citrix-on-Azure estates with the same ops rigor we used on WVD and on-prem VDI — bring concurrent peaks and whether profiles are already under control.