What's changed: Created AZ-140 Chapter 4 (Domain 3: FSLogix (Profile Container/ODFC/Cloud Cache/app masking); user experience and client settings (clients/device-multimedia redirection/Teams WebRTC Redirector/Universal Print/Intune/RDP properties/session timeouts/Start VM on Connect/personal-desktop assignment); app delivery (application groups desktop/RemoteApp, user assignment, M365 Apps SCA, OneDrive multi-session, App attach dynamic delivery)).
4.3Delivering apps on session hosts
Understand app deployment methods, application groups (desktop/RemoteApp) and user assignment, Microsoft 365 Apps and OneDrive (multi-session), and dynamic app delivery with App attach.
How you deliver apps is a choice of baking into the image, distributing individually, or mounting dynamically. In AVD, the publishing unit is the application group.
4.3.1Application groups and RemoteApp
There are two application group types: a desktop app group (publishes a full desktop) and a RemoteApp group (publishes individual apps as seamless windows). Assign users/groups to publish them, surfaced together to users via a workspace. Distinguish "deliver only specific apps, not a full desktop" = RemoteApp. Note design constraints on mixing desktop and RemoteApp publishing on a single host pool.
4.3.2M365 Apps, OneDrive, and App attach
Microsoft 365 Apps and OneDrive are deployed for multi-session by configuring shared computer activation and OneDrive multi-session settings. The current app-delivery method App attach (the evolution of MSIX app attach) packages apps onto storage and mounts them dynamically at logon. You can update/add apps without rebuilding the image, controlling delivery via user/group assignment. For "deliver apps dynamically without baking into the image and update easily," App attach is the norm (distinct from manual MSIX placement or recreating images each time).
Cues: "publish a full desktop" = desktop app group; "publish only specific apps seamlessly" = RemoteApp. "mount/update apps dynamically without baking into the image" = App attach. M365 Apps on multi-session needs shared computer activation.
Watch the mix-ups: (1) RemoteApp (individual apps) vs desktop app group (full desktop). (2) App attach (dynamic delivery) differs from image baking or manual MSIX. (3) M365 Apps on multi-session fails activation without shared computer activation (SCA) enabled.
4.3.3Section summary
- Application group = desktop (full) / RemoteApp (individual apps); publish via user assignment
- App attach = package apps and mount dynamically; update/add without recreating the image
- M365 Apps on multi-session requires shared computer activation (SCA)
Sign in to track progress — Log in.
Quick check
(just a quick review)Q1. You want to publish only specific apps as seamless windows, not a full desktop. Which is best?
Q2. You want to deliver apps dynamically without rebuilding the image, making updates/additions easy. Which is best?
Q3. When deploying Microsoft 365 Apps on multi-session session hosts, what is essential to avoid activation failure?
Q4. What is required to publish an application group to users in AVD?
Q5. Which correctly distinguishes App attach from traditional image baking?
Keep track of your progress
The full study guide is free to read. Sign up free to practice with the question bank, track what you have read, review your mistakes, and highlight passages.