メインコンテンツへスキップ

129: Client Apps

Implementation Effort: Medium to High
User Impact: Medium

Overview​

In co-management, the Client apps workload determines how application deployment responsibility is split between Configuration Manager and Microsoft Intune. This is a strategic decision because application packaging, assignment, user self-service, reporting, and update ownership can become confusing quickly if both systems are used without a clear operating model. In Zero Trust terms, the goal is a governed app-delivery path that keeps approved software current while reducing unmanaged installs and excessive local admin dependency.

Implementation Guidance​

  1. Decide which app types stay in Configuration Manager temporarily and which app types move to Intune first. Many organizations move modern Win32 apps, Microsoft 365 Apps, and self-service deployments earlier than highly customized legacy packages.
  2. Document the source of truth for each application. If the same app can be deployed from both Configuration Manager and Intune, administrators need clear rules to avoid duplicate install intent, detection conflicts, or competing uninstall behavior.
  3. Pilot the Client apps workload with a controlled device group before broad rollout. Validate Company Portal experience, install timing, user notifications, supersedence logic, and reporting.
  4. Use the migration as an opportunity to retire obsolete packages and reduce app sprawl. Moving old software into a new management plane without cleanup only preserves technical debt.
  5. Align app delivery with least privilege. The approved app catalog should be easier and safer than local admin installs or unmanaged downloads.
  6. Review whether the co-management split is still needed every quarter and continue moving workloads toward the target cloud model.

Reference​