What is the Intune AMAPI migration for personally-owned work profiles?

Microsoft has migrated its Intune personally-owned work profile implementation from a custom Device Policy Controller (the Company Portal app) to Google's Android Management API (AMAPI). This migration began in early 2026 and is now largely complete, with remaining devices being auto-migrated.

• The Company Portal app is being replaced by the Microsoft Intune app as the primary user-facing application for personally-owned work profile devices
• Web-based enrolment is being introduced, allowing users to begin enrolment from a URL rather than manually installing an app first
• Required apps cannot be uninstalled by users under the new implementation, aligning with how corporate-owned devices already behave

AMAPI is Google's modern management API and receives new features and platform capabilities before custom DPC integrations. By moving to AMAPI, Intune gains:

• Faster access to new Android Enterprise features
• Consistent behaviour across all four management modes (fully managed, dedicated, COPE, and BYOD work profile)
• Reduced maintenance burden of a custom DPC

Microsoft will automatically migrate remaining devices from the custom DPC implementation to AMAPI. Administrators should:

• Review their existing personally-owned work profile policies for compatibility
• Communicate the change to end users, as they will see the Microsoft Intune app replace Company Portal in their work profile
• Test the new enrolment flow in a pilot group before broad rollout

No. Intune's corporate-owned work profile (COPE), fully managed, and dedicated device management modes already use AMAPI. This migration only affects the personally-owned work profile scenario.

Sources:

• Microsoft Community Hub: New policy implementation and web enrollment for Android personally owned work profile
• Microsoft Learn: Android Enterprise work profile overview