5.1. Deploy and Update Apps
💡 First Principle: Every app deployment answers four questions in order: what is the package, which devices can run it, how Intune knows it's installed, and who gets it with what intent. Intune acts only on what you tell it, so most failed installs trace to one wrong answer — usually the detection rule or the intent — not the app.
Why care? Apps are the most visible part of endpoint management: a user never notices a missed setting, but does notice a laptop that arrives without Teams.
Think of a pipeline ending in one decision, the assignment intent, which pushes, offers or removes the same app per group.
| Intent | What the user sees | Unenrolled devices? | Key behavior |
|---|---|---|---|
| Required | Installs automatically | No | Reinstalled, updated or removed within 24 hours |
| Available for enrolled devices | Offered in Company Portal | No | User groups only, except Win32 apps and Android Enterprise fully managed and corporate-owned work profile apps, which can also target device groups |
| Available with or without enrollment | Offered to users without enrollment | Yes (users only) | Users still need an Intune license |
| Uninstall | App removed | No | Removes only apps Intune installed through a Required or Available for enrolled devices assignment of the same deployment |
⚠️ Common Misconception: Because Win32 and MSI line-of-business (LOB) apps both deploy fine on a device in use, many admins assume they can be mixed during classic Windows Autopilot. They can't: both use the Windows Trusted Installer service, so while the Enrollment Status Page (ESP) tracks both, one install fails with "Another installation is in progress" and the ESP fails with it. Use Win32 apps consistently (repackage the MSI as a Win32 app); Autopilot device preparation is the documented exception: it supports mixing them.