Multi-Session Windows
What Windows Enterprise multi-session is, how it differs from classic terminal servers, what it saves — and when it is the right choice.
What is multi-session Windows?
Windows Enterprise multi-session is a special edition of Windows tied to Azure Virtual Desktop — available in Azure regions and on Azure Local in your own datacenter, but explicitly not supported on Azure Virtual Desktop Hybrid. It allows several users to sign in to a single Windows VM at the same time — just as with the old terminal server, but with a full Windows desktop instead of a server interface.
That means: instead of running ten VMs for ten users, one or two powerful VMs suffice. Users see their familiar Windows desktop with the Start menu, taskbar and all their applications — they notice no difference.
Important distinction: Multi-session Windows is not the same as Windows Server with Remote Desktop Services (RDSH, the terminal server). It is a Windows client edition in its own right — with the look and feel of Windows 11, not of Windows Server 2022.
Vorher vs. Nachher
10 users = 10 VMs
Every user gets their own VM with its own Windows, its own CPU and its own memory. Those VMs often sit idle 80% of the time.
10 users = 1 VM
Ten users share one powerful VM. The operating system distributes CPU and memory intelligently. Each has their own desktop, their own profile and their own applications.
Architektur: Single- vs. Multi-Session
What does the user see? In both cases: a full Windows desktop with the Start menu, taskbar and all applications. The user notices no difference and has no idea whether they are alone on the VM or sharing it with four others. Only the IT department sees the difference: a tenth of the machines.
Multi-Session vs. Terminal Server (RDSH)
The comparison that comes up most often in projects — and the biggest point of misunderstanding: multi-session Windows is not a server operating system with the RDSH role.
Windows Server RDSH (classic)
- BaseWindows Server 2019 or 2022
- InterfaceThe server desktop with Server Manager, no consumer features
- Application compatibilitySome applications refuse to install on a server operating system
- LicenceWindows Server CAL plus RDS CAL pro User
- Available onJeder Plattform (Azure, on-prem, AWS, etc.)
Windows Enterprise Multi-Session
- BaseWindows 11 Enterprise (a client operating system)
- InterfaceA full Windows 11 desktop — Start menu, widgets, snap layouts
- Application compatibility100% as on an ordinary PC — no server-side restrictions
- LicenceAlready included in Microsoft 365 E3/E5 — no extra CALs
- Available onMicrosoft Azure only
Cost comparison: what does multi-session actually save?
An example: 100 office users (light to medium profile) in Azure West Europe:
| Scenario | VMs | SKU | Running time |
|---|---|---|---|
| Single-session1 user = 1 VM | 100 VMs | D4s_v5 (4 vCPU, 16 GB) | around the clock |
| Multi-session16 users = 1 VM | 7 VMs | E8s_v5 (8 vCPU, 64 GB) | around the clock |
| Multi-session + autoscalingshut down in the evening and at weekends | 7 VMs | E8s_v5 + scaling | about 9 h on 22 working days |
Autoscaling-Hinweis: With tools such as Nerdio Manager or Login Enterprise (Hydra), VMs are shut down automatically outside office hours. Because Azure bills by consumption, you pay only for the hours the VMs actually run.
Performance: does the user notice a difference?
The short answer: no, provided it is sized correctly. The longer answer:
When multi-session is ideal
Office work (Word, Excel, Outlook, Teams, a browser), SAP GUI, ERP clients, light line-of-business applications. Typically 2 to 4 GB of memory and 0.5 to 1 vCPU per user. 8–16 User pro VM are readily achievable.
When single-session is the better choice
CAD and 3D (a GPU is needed), software development (compiling), video editing, data analysis on large datasets. These users need dedicated resources and often GPU VMs (NVv4, NCas).
The “Noisy Neighbor” problem
If one user on a multi-session VM suddenly starts a heavy Excel calculation, that can affect the other users on the same VM.
The remedy: FSLogix CPU and memory limits per user, plus autoscaling that starts additional VMs automatically under load.
Which DaaS platforms support multi-session?
| Platform | Multi-Session | Note |
|---|---|---|
| Azure Virtual Desktop (AVD) | ✓ Nativ | A core feature of AVD — fully integrated |
| Citrix DaaS | ✓ Auf Azure | Citrix can use multi-session Windows, but only when deployed on Azure |
| Omnissa Horizon | ✓ Auf Azure | Horizon Cloud Service on Azure supports it — on-premises does not |
| Parallels RAS | ✓ Auf Azure | Works on Azure VMs running the multi-session operating system |
| Windows 365 | ✗ | Every Cloud PC is dedicated — multi-session is not possible |
| oneClick™ | ✗ | Multi-session only through Windows Server (RDSH), not through the Windows client |
Prerequisites
Licence
One of the following licences pro User is required — multi-session Windows is already included, with no extra cost for the operating system:
- Microsoft 365 E3 / E5 (the most common)
- Microsoft 365 A3 / A5 (Education)
- Microsoft 365 Business Premium
- Windows 10/11 Enterprise E3 / E5 standalone
- Windows VDA (for legacy scenarios)
Lizenzfalle: Microsoft 365 Business Standard and E1 are not sufficient, nor is Office 365 on its own. The Windows Enterprise component has to be explicitly included.
Infrastruktur
An Azure subscription with a virtual network, FSLogix for profiles (recommended) and Microsoft Entra ID (formerly Azure AD) for identity.
Management
The Azure portal (free of charge), or a management layer for autoscaling and image management — Nerdio Manager, Hydra / Login Enterprise or ControlUp, for example.
Multi-session in practice
DaaS Maps sets multi-session in a feature comparison across AVD, Windows 365, Citrix, Horizon and other platforms — including real user densities and cost examples. For a deeper conversation, you will find me on LinkedIn.