ConfigMgr to Intune App Migration - better Lifecycle Management

Enterprise customers migrating from Configuration Manager to Intune rarely move all applications at once. Instead, migrations are often long‑running, phased projects where applications remain co‑managed in both ConfigMgr and Intune for extended periods of time.

As customers progress through migration, they continue to make active changes to their applications in Configuration Manager, such as:

1. Updating detection rules

2. Modifying install or uninstall command lines

3. Adjusting dependencies, supersedence, or requirements

4. Updating content, scripts, or configuration settings

Today, once an application is migrated to Intune, these subsequent changes made in ConfigMgr are not automatically reflected in the Intune version. Customers must manually track changes and reapply them, which becomes increasingly difficult

Customer impact: Introducing a ConfigMgr ↔ Intune synchronisation mechanism for migrated apps would have meaningful impact

1. Reduced duplication and manual effort
   Customers no longer need to manually reapply Configuration Manager changes in Intune. Updates made in ConfigMgr automatically flow to the migrated Intune application, significantly reducing operational overhead during long migration.

2. Consistency across co‑managed environments
   Keeping ConfigMgr and Intune apps in sync helps prevent configuration differences, where the same application behaves differently depending on where it is deployed.