Windows 11 Multi-Session vs Windows Server for Azure Virtual Desktop

By David, 2026-10-02

Every new Azure Virtual Desktop deployment answers the same question early, usually before anyone has sized a VM: should pooled session hosts run Windows 11 Enterprise multi-session or Windows Server? Teams coming from Remote Desktop Services (RDS) or Citrix often reach for Windows Server out of habit. Teams starting fresh usually pick Windows 11 multi-session. Both are supported on AVD, and both work. They differ in how users are licensed, which apps and Microsoft 365 features are supported, how they're managed, and how long each release is supported.

This guide compares them side by side, covers the cases where Windows Server is still the right answer, and ends with a recommendation matrix you can apply pool by pool. It's vendor-neutral until the section on how Atlas AVD fits.

The short version: for most pooled desktops, choose Windows 11 Enterprise multi-session. Users with Microsoft 365 E3, E5, F3 or Business Premium are already licensed for it, Microsoft 365 Apps and new Teams are fully supported, it can be managed with Intune, and users get the Windows 11 desktop they know. Choose Windows Server where an app's vendor only supports or licenses it on Windows Server, where you already own RDS CALs with Software Assurance and your users lack an eligible Windows license, or for server roles that need a server OS. For personal desktops, use Windows 11 Enterprise.

Microsoft changes licensing terms and support dates from time to time. Everything below reflects Microsoft Learn as of October 2026, with links to each source so you can check what has changed since.

New to AVD? What Is Azure Virtual Desktop? explains host pools, session hosts and licensing first.

1. What "multi-session" means, and why it only exists on AVD

For most of Windows' history, only Windows Server could host many interactive users on one machine at the same time. That's the Remote Desktop Session Host role, the basis of RDS and of Citrix's server-based desktops. Desktop editions of Windows allowed one interactive user at a time.

Windows 10 and Windows 11 Enterprise multi-session changed that. They're editions of Windows Enterprise that allow several concurrent interactive sessions on one VM, so a pooled host pool can give each user a normal Windows 11 desktop while sharing the hardware (Windows Enterprise multi-session FAQ). Microsoft's stated reasons are a familiar Windows experience for users and the ability to use existing per-user Windows licensing instead of RDS Client Access Licenses (CALs).

Four facts from Microsoft's FAQ shape everything else in this guide:

• It only runs on Azure Virtual Desktop. Running Windows Enterprise multi-session in production outside the AVD service is against the licensing agreement, and it won't activate against an on-premises KMS server. Only Microsoft and the AVD Approved Providers, Citrix and Omnissa, can provide access to the service. So it isn't an option for an on-premises RDS farm or for other clouds.
• It reports itself as a server. Multi-session sets the operating system's ProductType to 3, the same value as Windows Server, to stay compatible with RDS tooling and RDS-aware apps. A side effect is that some installers that check for a client OS refuse to install on it.
• You can't convert a VM to it. An existing Windows Pro or Enterprise VM can't be upgraded to multi-session, and a multi-session VM that's switched to another edition can't be switched back. You deploy it from an image.
• In-place OS upgrades aren't supported on pooled hosts. Moving from Windows 10 to Windows 11, or between feature releases, means a new image and new hosts, not an upgrade on each host.

Windows Server, by contrast, runs anywhere: on AVD, in an RDS farm on-premises, in any cloud. That portability is one of the few things it still has over multi-session.

2. Side by side

Licensing: M365 rights vs RDS CALs

This is where the decision is usually made. Each user who connects to AVD needs an eligible license, and which one depends on the session host operating system (Licensing Azure Virtual Desktop):

• Windows 11 or 10 Enterprise, and Enterprise multi-session: Microsoft 365 E3, E5, A3, A5, F3, Business Premium or Student Use Benefit; Windows Enterprise E3 or E5; Windows Education A3 or A5; or Windows VDA per user.
• Windows Server 2016, 2019, 2022 or 2025: an RDS CAL with Software Assurance, per user or per device, or an RDS User Subscription License.

If your users already have Microsoft 365 E3 or Business Premium, they're already licensed for Windows 11 multi-session hosts and you pay nothing extra for access. Put the same users on Windows Server hosts and you need RDS CALs as well. Note that Microsoft 365 Business Basic and Business Standard aren't on the list, so a Business Standard estate needs an upgrade, Windows VDA or RDS CALs either way.

The VM itself differs too. Customers licensed for AVD can run Windows client session hosts without paying for another Windows license; the VM's LicenseType is set to Windows_Client, which the Azure portal does automatically when it creates hosts (Apply Windows license to session host VMs). A Windows Server VM in Azure is billed for Windows Server unless you apply Azure Hybrid Benefit with eligible Windows Server licenses. Windows Server hosts also need a Remote Desktop Services license server they can reach, on-premises or in Azure, and Microsoft notes that the AVD host pool wizard can assign a Windows Server host the wrong license type, so check it after deployment.

Two other licensing points matter less often but are decisive when they apply:

• Selling an app to external customers? AVD's per-user access pricing works only with Windows client session hosts. It isn't available for Windows Server.
• Windows 10 multi-session hosts get Extended Security Updates at no extra cost on AVD. Windows 10 reached end of support on October 14, 2025. Single-session and multi-session Windows 10 VMs on AVD are automatically eligible for ESU, though you still have to enable the ESU policy on them (Windows 10 ESU on AVD). It's a bridge, not a destination: plan the move to Windows 11.

For the cost side of the VM bill, including what reservations and savings plans do and don't discount on each OS, see Azure Reserved Instances vs Savings Plans for AVD.

App compatibility

Most Win32 apps that run on Windows 11 run on Windows 11 multi-session, and most apps that ran on an RDS session host run on either. The exceptions come in three kinds:

• Installers that refuse multi-session. Because multi-session reports ProductType 3, an installer that checks for "client OS" can refuse it. Microsoft's advice is to ask the vendor for an updated version. In practice most current versions are fine, but old installers are where this bites.
• Apps that require, or are only certified on, Windows Server. Some line-of-business and engineering apps check for a Server SKU, depend on a server role or feature, or are only supported by the vendor on Windows Server with RDS.
• Per-user state. Anything a user installs into their own profile disappears at sign-out on a pooled host with FSLogix. That's the same on both operating systems; install apps for all users, in the image or at runtime.

Test every app on the OS you choose before you commit, and test the installer, not just the app. App delivery on AVD covers where each app should come from.

User experience

Windows 11 multi-session gives users the same Windows 11 desktop they have on a laptop: the Start menu, Settings, Store apps if you allow them, and the same look as Windows 365 and their physical device. That consistency cuts training and support calls.

Windows Server with the Desktop Experience is close, but it's a server: some consumer and client features are missing or off by default, a few in-box apps aren't there, and users notice. For RemoteApp-only pools, where users never see the desktop, the difference mostly disappears.

Microsoft 365 Apps and Teams

This is the newest reason to move off Windows Server.

• Microsoft 365 Apps. Microsoft supports Microsoft 365 Apps on a Windows Server version only while that version is in mainstream support (Windows Server end of support and Microsoft 365 Apps). Support on Windows Server 2016 and 2019 ended on October 14, 2025, and on Windows Server 2022 it ends with Windows Server 2022's mainstream support in October 2026. All three keep getting security updates until October 10, 2028, but stay on a frozen feature version. Windows Server 2025 is supported until its own mainstream support ends in 2029. Microsoft's recommendation for anyone stuck on an unsupported Windows Server version is to move to Azure Virtual Desktop or Windows 365.
• New Teams. New Teams in VDI supports Windows 10 and 11, including multi-session, and Windows Server 2022 and 2025. Windows Server 2016 and 2019 aren't supported (Teams for VDI). Media optimization works the same way on both supported families; Teams on Azure Virtual Desktop covers the setup checklist.

So a Windows Server pool that needs Office and Teams is, in practice, a Windows Server 2025 pool. On Windows 11 multi-session, Microsoft 365 Apps is supported for as long as the Windows release it runs on is, and Microsoft even publishes Azure Marketplace images with Microsoft 365 Apps pre-installed.

Management

Microsoft Intune manages Windows 11 multi-session hosts that are Microsoft Entra joined or hybrid joined. Intune doesn't support Windows Server, so Windows Server session hosts are managed with Group Policy from Active Directory, local policy, or Configuration Manager (AVD prerequisites). If your device management has moved to Intune, a Windows Server pool means keeping a second toolset alive just for it.

Lifecycle

The two follow different policies, and that changes how often you rebuild.

• Windows 11 Enterprise follows the Modern Lifecycle Policy: each annual feature release, including the multi-session edition, is supported for 36 months (Windows 11 Enterprise and Education lifecycle). As of October 2026, 23H2 ends in November 2026, 24H2 in October 2027, 25H2 in October 2028, and 26H2 is supported until October 2029. Plan one OS image upgrade every one to three years.
• Windows Server follows the Fixed Lifecycle Policy: about five years of mainstream support and five more of extended support. Windows Server 2025 is in mainstream support until November 2029 and extended support until November 2034 (Windows Server 2025 lifecycle). Windows Server 2016 extended support ends in January 2027.

Windows Server's longer lifecycle looks like an advantage, but it's mostly an advantage for the OS. The apps on top, Microsoft 365 Apps above all, follow the mainstream date, not the extended one. On pooled AVD hosts that are rebuilt from an image every month anyway, a feature release upgrade is one more image build, not a project.

3. When Windows Server still wins

Windows 11 multi-session is the default, not the only answer. Windows Server is the better choice when:

• A line-of-business app is only supported, or only licensed, on Windows Server. Some vendors certify their apps for RDS on Windows Server only, or license them per server or per concurrent RDS user in a way that doesn't cover multi-session. If the vendor won't support it on Windows 11 multi-session, a support contract is worth more than the licensing savings.
• An installer or app checks for a Server SKU and fails on multi-session even though multi-session reports ProductType 3, or the app depends on a server role or feature.
• You already own RDS CALs with Software Assurance and your users don't have an eligible Windows license. If your users are on Microsoft 365 Business Standard or Office-only plans, the CALs you already own may be cheaper than upgrading every user to an eligible license. Do the sums per user, not per VM.
• The same image has to run outside AVD. An on-premises RDS farm, another cloud or a disaster recovery site that isn't AVD can't run multi-session.

Even then, keep Windows Server to the pools that need it. Most estates that start this way end up with one Windows Server pool for a handful of legacy apps, often published as RemoteApps, and Windows 11 multi-session for everything else. AVD supports a different OS per host pool, so mixing is normal.

If you're migrating from Citrix or RDS with Server OS VDAs today, Citrix to Azure Virtual Desktop migration covers how to map those catalogs onto AVD host pools.

4. Personal desktops: Windows 11 Enterprise single-session

Everything above is about pooled host pools, where users share hosts. Personal host pools give each user their own VM, and there the usual choice is Windows 11 Enterprise, the ordinary single-session edition. It's covered by the same licenses as multi-session (Microsoft 365 E3, E5, F3, Business Premium, Windows Enterprise E3/E5 and the rest), with no separate Windows license charge on the VM.

Personal desktops make sense for developers who need admin rights, users with heavy or GPU workloads, and apps that must keep state on the machine. With one user per VM there's no density benefit from multi-session. Windows Server is rarely the right choice for a personal desktop: it needs RDS CALs and gains nothing over Windows 11.

The trade-offs between the two pool types, and how to run both side by side, are covered in Pooled vs Personal Host Pools in AVD.

5. Image and patching implications

The OS choice decides what your golden image looks like and how often you rebuild it.

• Start from the right Marketplace image. Microsoft publishes Windows 11 Enterprise multi-session images with and without Microsoft 365 Apps, updated monthly after Patch Tuesday, and FSLogix comes pre-installed on all of them (Windows Enterprise multi-session FAQ). For Windows Server you install Microsoft 365 Apps and FSLogix yourself.
• Configure Microsoft 365 Apps for shared computer activation on any multi-user host, on either OS (Install Microsoft 365 Apps on a custom VHD image).
• Windows Server hosts need the RDS license server configured in the image or through policy, and the RD Session Host role installed. Multi-session needs neither.
• Feature upgrades mean a new image. Because in-place upgrades aren't supported on pooled hosts, a move from Windows 11 24H2 to 25H2 is a new image version and a rolling replacement of hosts. On Windows Server the same happens less often, but it's a bigger jump when it does.
• Monthly patching is the same on both: a new image version each Patch Tuesday, tested on a pilot pool, rolled out in batches that drain first.

AVD Golden Image Management covers building, versioning and rolling out the image, with a monthly checklist that works for either OS.

6. Recommendation matrix

Once you've picked the OS, size the hosts for it: Azure Virtual Desktop sizing guide covers users per vCPU and VM families for multi-session hosts.

How Atlas AVD fits

Atlas AVD deploys and runs session hosts in your own Azure subscription, so the OS decision above stays yours. Here's how each choice looks in Atlas, and where it stops.

Windows 11 is built in. When you deploy session hosts, the image picker lists Microsoft's current Windows 11 images in three groups: Multi-session (pooled), Multi-session + Microsoft 365 Apps and Single-session (personal). That covers Windows 11 Enterprise multi-session 25H2, 24H2 and 23H2, with or without Microsoft 365 Apps, and Windows 11 Enterprise 25H2 and 24H2 for personal desktops. The list only shows images available in the region you're deploying to. Windows 10 and Windows Server aren't in the built-in list.

Any other OS comes from your gallery. Atlas deploys from any image definition in your Azure Compute Gallery, without filtering by OS. So a Windows Server pool runs from your own Windows Server image, built and versioned in Image Management the same way as a Windows 11 one, with Sysprep run on a temporary copy so the source VM is left untouched. Image Management is included on every plan.

The client license type is applied for you. New and re-imaged hosts get the Windows client license type (Windows_Client) by default, which is what Microsoft requires for Windows 11 hosts covered by your users' licenses. The Client License Mode setting controls it, globally or per host pool. For a Windows Server pool, turn Client License Mode off for that pool: Azure rejects a client license type on a Windows Server image. Atlas doesn't apply Azure Hybrid Benefit to Windows Server session hosts, doesn't track RDS CALs and doesn't set up an RDS license server, so those stay with your licensing team.

Pooled and personal pools both deploy from the same wizard. Choose a Host Pool Type of Pooled or Personal, and for personal pools an Assignment Type of Automatic or Direct. VM Provisioning builds each host from the image you chose, joins it to Entra ID or Active Directory and confirms it registered with the pool. How to deploy AVD in under 30 minutes walks through a first deployment.

Feature upgrades are an image rollout. Moving a pool from Windows 11 24H2 to 25H2, or from Windows 10 to Windows 11, means a new image version and replacing the hosts, which is what Re-Image All in Rolling Replace (Zero Downtime) mode does: Atlas builds each replacement first, drains the old host, and deletes it only once its last user has signed out. AVD Golden Image Management covers how that works.

FAQ

What is Windows 11 Enterprise multi-session?

Windows 11 Enterprise multi-session is an edition of Windows 11 Enterprise that lets several users run interactive sessions on the same VM at once, which used to be possible only on Windows Server. It's available only on Azure Virtual Desktop, and users are licensed for it through Microsoft 365 or Windows Enterprise licenses instead of RDS CALs.

Can I run Windows 11 multi-session outside Azure Virtual Desktop?

No. Microsoft doesn't allow Windows Enterprise multi-session in production outside the Azure Virtual Desktop service, and it won't activate against an on-premises KMS server. It can run on Azure Virtual Desktop in Azure or on Azure Local, and Citrix and Omnissa can deliver it as AVD Approved Providers.

Do I need RDS CALs for Windows 11 multi-session on AVD?

No. Windows 11 Enterprise multi-session session hosts are licensed per user through Microsoft 365 E3, E5, A3, A5, F3, Business Premium, Windows Enterprise E3 or E5, Windows Education A3 or A5, or Windows VDA per user. RDS CALs with Software Assurance, or RDS User Subscription Licenses, are needed only for Windows Server session hosts.

Is Windows Server or Windows 11 multi-session cheaper on AVD?

For users who already have an eligible Microsoft 365 or Windows license, Windows 11 multi-session is usually cheaper: there's no RDS CAL to buy and no separate Windows license charge on the VM. Windows Server can be cheaper only if you already own RDS CALs with Software Assurance and eligible Windows Server licenses for Azure Hybrid Benefit, and your users lack an eligible Windows license.

Is Microsoft 365 Apps supported on Windows Server for AVD?

On Windows Server 2025, yes, while it's in mainstream support. Support on Windows Server 2016 and 2019 ended in October 2025, and on Windows Server 2022 it ends in October 2026; all three receive only security updates until October 2028. Windows 11 Enterprise multi-session supports Microsoft 365 Apps with shared computer activation.

Should personal host pools use Windows 11 multi-session?

Personal host pools usually use Windows 11 Enterprise, the single-session edition, because each user has their own VM and gets nothing from multi-session. It's covered by the same Microsoft 365 and Windows licenses. Multi-session is designed for pooled host pools where users share hosts.

Can I upgrade Windows 10 multi-session hosts to Windows 11 in place?

No. In-place upgrades of the operating system aren't supported for session hosts in a pooled host pool. Build a Windows 11 Enterprise multi-session image and replace the hosts. Windows 10 multi-session hosts on AVD receive Extended Security Updates at no extra cost in the meantime.

Sources

• Microsoft Learn: Windows Enterprise multi-session FAQ
• Microsoft Learn: Licensing Azure Virtual Desktop
• Microsoft Learn: Prerequisites for Azure Virtual Desktop
• Microsoft Learn: Apply Windows license to session host virtual machines
• Microsoft Learn: Windows Server end of support and Microsoft 365 Apps
• Microsoft Learn: Microsoft Teams for Virtualized Desktop Infrastructure
• Microsoft Learn: Windows 11 Enterprise and Education lifecycle
• Microsoft Learn: Windows Server 2025 lifecycle
• Microsoft Learn: Extended Security Updates for Windows 10 on Azure Virtual Desktop
• Microsoft Learn: Install Microsoft 365 Apps on a custom VHD image