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

187: Enterprise App Management (EAM)

Implementation Effort: Low – Prepackaged catalog apps include pre-filled install commands, detection rules, and automatic update policies.

User Impact: Low – Keeps third-party applications patched automatically in the background with minimal user disruption.

Overview​

Intune's Enterprise App Management (EAM) streamlines the discovery, deployment, and continuous patching of Microsoft and third-party Win32 applications from a curated, Microsoft-maintained Enterprise App Catalog.

Key 2025–2026 updates include:

  • Included in Microsoft 365 E5 (June 2026 / 2606): Enterprise Application Management is now included directly in Microsoft 365 E5 (as well as Intune Suite).
  • Auto-Update for Enterprise App Catalog Applications (June 2026 / 2606): When you enable auto-update on an EAM app with a required assignment, Intune automatically detects when a newer version is published in the EAM catalog and deploys the update to targeted devices—eliminating manual packaging and supersedence workflows.
  • PowerShell Script Installer Support (September 2025): Admins can upload custom PowerShell scripts to install EAM catalog apps when pre/post-install customizations are required.
  • Autopilot Device Preparation & Deployment Plans Support (2025–2026): EAM catalog apps can be delivered during OOBE via Windows Autopilot device preparation and staged across rings using Intune Deployment Plans.
  • GCC High & DoD Availability (June 2026 / 2606): EAM is now supported in US Government GCC High and Department of Defense (DoD) cloud environments.
  • Published Service Level Objectives (SLOs) (2511): Automated validation of new vendor app updates typically completes within 24 hours.

Implementation Guidance​

  1. Confirm feature availability and assign clear ownership for catalog approval, pilot validation, and production rollout.
  2. Browse the Enterprise App Catalog in the Microsoft Intune admin center and identify apps that should move from manual Win32 packaging to the managed catalog model.
  3. Review install behavior, detection logic, update behavior, and architecture support for each selected app instead of assuming the defaults always fit.
  4. Pilot required or available assignments, validate coexistence with previously packaged versions, and retire duplicate packaging once the catalog version becomes standard.
  5. Monitor app deployment and update reports regularly and keep a separate standard for apps that remain outside the catalog.

Reference​