Memory hook: Workspace publishes; pool groups; host runs.
Must remember
- A host pool groups session hosts; application groups publish desktops or RemoteApps; a workspace exposes assigned application groups to users. Assignments and user access must align across these objects.
- Pooled hosts serve multiple users with breadth-first or depth-first distribution; personal hosts assign a desktop to an individual. Choose supported client/server OS and licensing for the use case, including multi-session eligibility.
- Breadth-first distributes new sessions across available hosts to balance load. Depth-first consolidates sessions toward configured host limits, which can leave other hosts available to stop under a coordinated scaling policy. Neither mode overrides drain state, session limits or the need for enough real memory/application capacity. Reconnection to an existing session differs from allocating a new session.
- AVD uses service-mediated reverse connectivity rather than requiring public inbound RDP on every host. RDP Shortpath and supported Multipath improve transport when network conditions and prerequisites allow.
- Plan latency, bandwidth, DNS, required service endpoints, NSGs, UDRs and firewall access. Private Link changes supported access paths and DNS requirements; test client and host connectivity separately.
- Choose region, VM size, host count, quotas and resource organization from concurrency and application demands. GPU, memory or per-user workload may dominate sizing.
- Deploy through portal, PowerShell, CLI or ARM/Bicep, using a controlled host registration and image process. A host appearing in a pool still needs a healthy agent, identity join and working applications.
Choose under exam pressure
| Requirement | Choice and reason |
|---|---|
| Many task workers with similar apps | A pooled host pool with sized capacity and profile separation. |
| One user requires a persistent dedicated desktop | A personal host pool with explicit assignment. |
Traps
- A workspace is not the VM running the desktop.
- Opening public TCP 3389 is not the standard requirement for user AVD access.
Active recall
1. What publishes a RemoteApp?
An application group assigned to users and associated with the appropriate workspace.
2. What does depth-first balancing favor?
Filling hosts toward their configured session limit, which can support consolidation.
3. Why test UDP transport?
Shortpath performance depends on supported network reachability and policy.
4. What determines host count?
Concurrent sessions, workload resource demand, availability and scaling requirements.
5. Why check licensing separately?
OS choice and user eligibility determine licensing obligations beyond Azure VM cost.