Configmgr MSIX deployment with phone experience
Deploying a new verion of a msix application via Configmgr requires a new deployment.
Why not change this behavior so it is possible use the same deployment to do update?
Application01 version 1 is an msix application, and it is deployed via Configmgr.
When there is an update available, it is deployed by updating the source directory and content is distributed to the DP's
then next time a user start Application01 it will be updated.