What's changed: Created AZ-140 Chapter 2 (Domain 1 second-half: host pool architecture (pooled/personal, breadth/depth load balancing, Windows Enterprise multi-session, RDS CAL/Windows access entitlement, resource organization, VM-capacity design); implementation (Azure portal wizard, registration token, PowerShell/Azure CLI/ARM templates/Bicep IaC, validation-environment flag); session-host images (manual/Sysprep, Azure VM Image Builder, Azure Compute Gallery versioning/replication, update lifecycle/recreate)).
2.1Planning host pool architecture
Understand host pools (pooled/personal) and load-balancing algorithms, session-host OS and licensing models, organizing resource groups/subscriptions/management groups, and designing performance/VM-capacity requirements.
A host pool is a set of identically configured session hosts (VMs). The first design fork is "shared by multiple users or dedicated to one"—pooled or personal.
2.1.1Pooled vs personal, load balancing
A pooled host pool shares the same session hosts among multiple users (multi-session, cost-efficient); a personal host pool dedicates one host per user (preserves state, specialized use). Pooled load balancing is breadth-first (spread new sessions across all hosts for even experience) or depth-first (fill one host to its limit to reduce cost). For "uniform experience for all," breadth; for "fewer VMs and lower cost," depth.
2.1.2OS, licensing, and resource organization
For multi-session use Windows 11/10 Enterprise multi-session; for single-session or specific needs, Windows Enterprise or Windows Server. Licensing depends on whether target users hold Windows client access entitlement (M365/Windows E3/E5, etc.); Windows Server requires RDS CAL. Organize resources via resource groups/subscriptions/management groups along environment (prod/test), billing, and delegation boundaries. Size VM capacity by "vCPU/memory per user × concurrent connections."
Cues: "shared by many, cost-efficient" = pooled (multi-session). "dedicated per user, state preserved" = personal. "uniform experience" = breadth-first; "fewer VMs/lower cost" = depth-first. Windows Server needs RDS CAL; client OS needs Windows client access entitlement.
Watch the mix-ups: (1) Pooled (shared, multi-session) vs personal (dedicated). (2) Breadth-first (spread, even experience) and depth-first (consolidate, lower cost) have opposite goals. (3) Multi-session requires Windows Enterprise multi-session—distinct from a regular single-session Windows client.
2.1.3Section summary
- Pooled = shared/multi-session/cost-efficient; personal = dedicated per user/state preserved
- Load balancing = breadth-first (spread/even) / depth-first (consolidate/cost)
- Multi-session = Windows Enterprise multi-session; Server needs RDS CAL, clients need Windows access entitlement
Sign in to track progress — Log in.
Quick check
(just a quick review)Q1. You want multiple users to share session hosts and operate cost-efficiently with fewer VMs. Which host pool type?
Q2. You want to assign each user a fixed dedicated desktop that preserves state across reboots. Which host pool type?
Q3. You want to spread new sessions evenly across all session hosts for a uniform experience. Which load-balancing algorithm?
Q4. You want to minimize running VMs and reduce cost by filling one host to its limit before the next. Which load balancing?
Q5. When using Windows Server as a session host, which license is required?