Thank you everyone for your valuable feedback! Below are the topics addressed during the live session, along with associated timestamps. As noted, comments will be open for your continued feedback through Friday at 12p PT.

Feedback/question – Is there a plan to provide more visibility to the supersedence portion of app deployment? For example, I have an app that I deployed an update to that supersedes an existing deployment. If I deploy an app that supersedes both the update an the original deployment, then weeks later go back and delete the original deployment, I have to find the app that is preventing the deletion because of the supersedence relationship. In SCCM, I can at least see the offending app. In Intune, I'm not able to other than that there's a supersedence rule applied. – answered at 3:06.

Feedback/question – Also, what about dependencies? You can see down the chain but not up. As I'm modifying an app, it'd be good to know which other apps depend on it. – answered at 5:07.

Feedback/question –What about adding the running process check like in ConfigMgr, before upgrading or superseding an application. If the native app is running, alert user first. – answered at 5:22.

Feedback/question – Will there ever be a way to create a dynamic group of devices that have a particular program installed in Intune? I have this set up in Config Manager and this helps with program deployment. – answered at 8:18.

Feedback/question – Most of our applications are migrated to Intune from ConfigMgr. However, we have some rather large packages, like AutoDesk applications (some take up to 25-30GB), that we prefer to push via ConfigMgr, since it is typically much faster than going from the internet. --- Similar feedback from Sinan -- We deploy big CAD software (100+ GB) via SCCM. How to do that with Intune? – answered at 11:05.

Feedback/question – The inclusion of a bespoke "Microsoft 365 Apps" app type is useful and simplifies the deployment of the M365 apps to endpoints. However, the process of adding an individual app to a pre-existing install is not smooth; for example, where the company base profile excludes Microsoft Access but some users later require Access, it's tricky to add it when the suite is already installed, largely because most users have at least one of the M365 apps open at all times, which blocks config changes. It's also infeasible to have users self-service via Company Portal since the apps are all delivered as a single bundle. This adds to the request for adding support for running process handling natively in Intune. – answered at 17:27.

Feedback/question – Can you work on integrating app discovery with App Control for Business.  My concern is that our endpoints already have a large number of apps installed through previous deployment processes, and so even with "managed installer" allowed, that does not cover previously deployed apps which then get blocked.  The whole app control for business side of intune would be much easier to deploy if that team was totally looped in with the teams building app deployment, app inventory, and app updates for Intune. – answered at 22:02.