Check every app relationship's install context on multi-session desktops

Source facts

Intune requires apps for Windows Enterprise multi-session to install in system or device context and target devices. Only Required and Uninstall assignment intents are supported, not Available. A system-context Win32 app will not install if a dependency or supersedence relationship points to a user-context app. Microsoft recommends a separate system-context instance or making all dependencies system-context. Microsoft Learn.

Applicability

Apply this check to Intune-managed Azure Virtual Desktop Windows Enterprise multi-session VMs that meet the documented prerequisites. Intune’s multi-session support does not extend to Citrix DaaS or VMware Horizon Cloud.

DSE recommendation

Review the complete app relationship graph before changing the parent assignment. List each dependency and superseded app with its configured install context. Identify the intended device group and assignment intent. If a user-context relationship is present, design and test the supported system-context package arrangement with the application owner. Do not assume that changing only the parent app’s context resolves its linked packages or preserves the intended application behavior.

Verification

In an approved multi-session test pool, confirm the effective assignments and the context of every linked app before checking installation results. Exercise the application with the intended users and retain the dependency outcomes, not only the parent’s status. Keep any separate package instance clearly identified in the handoff. If an app still fails, investigate its actual relationship and installation evidence before widening its target population.

Official references

Microsoft Learn: Using Azure Virtual Desktop multi-session with Microsoft Intune.