Win32 supersedence auto-update applies to available apps installed through Company Portal, not apps obtained through required assignments. Removing the user from the targeted group, removing the assignment, or changing its available intent removes the recorded consent. Restoring available targeting later does not restore that auto-update path. A superseding app also needs explicit targeting; its relationship alone is insufficient. Microsoft Learn.
\nUse this review for an existing Company Portal installation with available intent. Record the superseded and superseding app identities, current assignments, and how the user originally obtained the app.
\nReview planned group cleanup and assignment changes with the app owner before editing them. Treat the established user-consent path as part of the deployment design, not just the presence of application files. Document the expected update population and any devices that require a different approved installation route. Review detection rules and installer behavior separately from targeting.
\nUse a test device that obtained the old app from Company Portal and compare it with an otherwise similar device outside that path. Confirm that the intended new app is targeted and that the observed update matches the planned relationship. If targeting has already changed, investigate the recorded installation route before repeatedly recreating the same relationship. Preserve the assignment history and actual installed result; do not promise that retargeting alone repairs the lost consent.
\n