Something I do quite a bit in Config Manager that isn't doable in Intune:
For many apps that are deployed as available to devices, I have an app that is the current version and an app that is superseded by the current version and the detection methods for these use the application's exe and version number. The current version app will have the current version string with greater than or equal and the superseded app will have the current version string with less than.

This allows for apps to be deployed as available to all devices and will install the superseding version over any older version regardless of how the old version was installed. This is helpful for devices migrated to Intune management or for users with admin rights or if users are allowed to install apps with EPM. When we want to deploy a new version, all I have to do is update the content and possibly install string for the current version app and the detection method in both apps with the new version string. This does not work in Intune because supersedence is only applicable if the previous app was installed via Intune and is still deployed. This is much worse than the supersedence behavior in Config Manager where I only need the current app deployed and the detection methods handle everything during an app deployment evaluation cycle.