Baking every application into the golden image makes the image huge, slow to build and painful to update. MSIX App Attach flips the model: applications live in their own packages on a share and are attached to session hosts at runtime — so the image stays lean and apps update independently.
The problem App Attach solves
In the traditional model, each app you add to the image means another rebuild, retest and redeploy cycle for the whole host pool. App Attach decouples the application lifecycle from the image lifecycle: package once, store on a share, attach dynamically, and update the package without touching the image.
| Approach | App updates | Image size | Best for |
|---|---|---|---|
| Apps in image | Rebuild image | Large | Ubiquitous core apps (Office, browsers) |
| MSIX App Attach | Swap the package | Lean | Line-of-business & departmental apps |
| Per-user install | N/A (not scalable) | — | Avoid on pooled hosts |
How App Attach works
- You package the application as an MSIX and expand it into a VHD(X)/CIM image on an SMB share.
- The application is registered to a host pool as an App Attach package.
- At (or before) user logon, the package’s disk is staged and mounted on the session host.
- Windows registers the app for the user so it appears installed.
- At logoff it’s deregistered and detached — the host stays clean.
MSIX vs. MSIX App Attach
MSIX is the modern application package format. App Attach is the AVD feature that delivers those packages to session hosts at runtime from a share, rather than installing them.
Storage and packaging considerations
- Store packages on resilient SMB storage (Azure Files / Azure NetApp Files) with read access for the session hosts’ identity.
- Not every app MSIX-packages cleanly — apps with drivers, services or deep shell integration can be problematic; test each one.
- Code-signing matters: packages must be signed with a certificate the hosts trust.
- Keep a versioning scheme so you can stage a new package and switch over predictably.
Where it shines — and where it doesn’t
App Attach is excellent for line-of-business and departmental apps that change on their own cadence, or that only some users need. It’s usually not the right tool for the universal core (Office, your browser, security agents) — those belong in the image where they’re always present and fully integrated.
Combine, don’t choose
The strongest pattern is hybrid: core apps in a lean golden image, everything else delivered via App Attach. You get fast image builds and independent app updates at the same time.
Operational tips
- Stage packages ahead of logon where possible to avoid first-launch delay.
- Pilot each newly packaged app on a test host pool before production registration.
- Document the package source, version and signing cert — App Attach issues are usually packaging or permissions, not the feature itself.
- Watch share performance; many hosts mounting many packages is real I/O.
MSIX App Attach is what keeps a golden image small and a host pool maintainable as your app catalogue grows. Reserve the image for the universal core, deliver the long tail via App Attach, and test packaging app-by-app.
Need a hand with your AVD platform? 🚀
I help organisations design, migrate and optimise Azure Virtual Desktop. If you’re planning or troubleshooting a deployment, get in touch.
