5.3. Reflection Checkpoint
Key Takeaways
- Choose Win32 whenever you need dependencies, supersedence, requirement rules, more than one command-line argument or reliable installs during classic Autopilot — and don't mix Win32 and MSI apps while the ESP is tracking installs.
- Deploy Microsoft 365 Apps as a Win32 app built from the ODT when it must install during classic Autopilot; remember Semi-Annual Enterprise Channel merged into Monthly Enterprise from Version 2606, and cloud update overrides Intune and Group Policy update settings.
- Resolve app intent conflicts by rule: Required beats Uninstall, Uninstall beats Available (except User Available against Device Uninstall), and intent is evaluated before filters.
- App protection policies work without enrollment and are assigned to users; Android needs Company Portal, and selective wipe removes only org data.
- Build new Conditional Access policies with Require app protection policy; Require approved client app was retired on June 30, 2026 and survives only as read-only, still-enforced legacy policies.
Connecting Forward
Phase 6 turns from individual devices and apps to running the whole estate: automating Intune with PowerShell and Microsoft Graph, extending compliance with scripts, working with Security Copilot in Intune, and using reports, Endpoint analytics, remediations and service health to catch problems — including app reliability issues — before users report them.
Self-Check Questions
- A Win32 app shows as installed on a device, but after you configure a newer version as superseding with "Uninstall previous version = Yes", nothing changes. Walk through the two most likely causes.
- Why can Cloud Policy enforce Office settings on a contractor's unmanaged PC when an Intune settings catalog profile can't, and why would assigning it to a device group fail?
- A personal iPhone user can open work email in Outlook but is blocked in a third-party mail app after you enable a Conditional Access policy. Explain which components produced each outcome.