Edit

Overview of Apple Automated Device Enrollment for Apple mobile

Automated device enrollment (ADE) is an Apple enrollment method for corporate-owned devices purchased through Apple Business or Apple School Manager. With ADE, you configure and deploy enrollment policies to devices over the air — without touching the devices. When someone turns on a device for the first time, Apple Setup Assistant guides them through setup and enrollment automatically.

Note

The steps in ADE articles are the same whether you're using Apple Business or Apple School Manager. For brevity, those articles refer to Apple Business only, except where clarification is necessary.

Supported platforms

Microsoft Intune supports automated device enrollment for Apple mobile devices, which include iOS/iPadOS, tvOS, and visionOS. As an administrator, you can create, edit, delete, and assign a platform-specific automated device enrollment policy to devices.

Platform Setup article What it's for
iOS/iPadOS Create an enrollment policy for iOS/iPadOS User affinity, no user affinity
tvOS Create an enrollment policy for tvOS No user affinity
visionOS Create an enrollment policy for visionOS No user affinity

tvOS and visionOS support automated device enrollment without user affinity only. These platforms enroll using a userless provisioning model and support device-targeted management policies. Device setup is completed through Apple Setup Assistant and device-targeted policies are applied after enrollment.

For macOS information, see Overview of Apple Automated Device Enrollment for macOS.

Supported scenarios

Scenario Supported
Supervised mode ✅ ADE devices are supervised by default, giving you more management control.
Corporate-owned devices ✅ Designed for devices purchased through Apple Business or Apple School Manager.
Zero-touch deployment ✅ Devices can ship directly to users. Enrollment starts when they turn on the device.
Bulk enrollment ✅ Enroll a few devices or thousands using a single enrollment policy.
Devices with a single assigned user ✅ Supported on iOS/iPadOS, not tvOS or visionOS.
Userless devices (kiosk, shared-use) ✅ Supported on all Apple mobile platforms.
Microsoft Entra shared device mode ✅ Supported on iOS/iPadOS for frontline worker scenarios.
Apple Shared iPad ✅ Supported on iPadOS.
BYOD or personal devices ❌ Not supported. Use MAM or user and device enrollment instead.
Device enrollment manager (DEM) accounts ❌ Not supported.
Devices managed by another MDM provider ❌ Users must unenroll from their current MDM provider before enrolling in Intune. For help migrating devices, see Apple making device migration to Microsoft Intune easy with upcoming OS 26 release on the Microsoft Community Hub.

How ADE works

Setting up ADE in Intune involves three main tasks:

  1. Get an enrollment program token: Create a trust relationship between Intune and Apple Business. This is typically a one-time setup task per token. For more information, see Set up enrollment token.

  2. Create and assign an enrollment policy: Configure the enrollment experience for your devices, including user affinity, authentication method, and Setup Assistant screens. Then assign the policy to device groups.

  3. Sync and distribute devices: Sync device records from Apple Business to Intune, then distribute devices to users. Enrollment starts automatically through Apple Setup Assistant when a device is turned on. For more information, see Managed Apple mobile devices and tokens.

What is supervised mode?

Supervised mode provides more management control over corporate-owned devices, so you can do things like block screen captures and restrict AirDrop.

Corporate-owned devices running iOS/iPadOS 11 and later and enrolled through automated device enrollment should always be in supervised mode, which you can turn on in the enrollment policy. For more information about supervised mode, see Enable supervised mode. Microsoft Intune ignores the is_supervised flag for devices running iOS/iPadOS 13.0 and later because these devices are automatically put in supervised mode at the time of enrollment.

Certificates

This enrollment type supports the Automated Certificate Management Environment (ACME) protocol. When new devices enroll, the management profile from Intune receives an ACME certificate. ACME provides better protection than the SCEP protocol against unauthorized certificate issuance through robust validation mechanisms and automated processes, which helps reduce errors in certificate management.

ACME is supported on:

  • iOS 16.0 or later
  • iPadOS 16.1 or later
  • tvOS 26.0 or later
  • visionOS 26.0 or later

Enrolling devices in shared device mode

You can set up automated device enrollment for devices in shared device mode. Shared device mode is a feature of Microsoft Entra ID that enables frontline workers to share a single device throughout the day, signing in and out as needed. For more information about how to enable enrollment for devices in Microsoft Entra shared device mode, see Automated device enrollment for shared device mode.

Before you begin

Before setting up ADE in Intune, make sure you have the following in place across all platforms:

Additionally, decide how you want users to authenticate:

  • Setup Assistant with modern authentication (recommended):

    • Supported on iOS/iPadOS 13.0 and later.
    • Supports multifactor authentication and just-in-time (JIT) registration, eliminating the need for the Company Portal app if configured with a device configuration policy.
  • Intune Company Portal app:

    • Also supports modern authentication and multifactor authentication.
    • Still requires users to complete Microsoft Entra registration through the app.
  • Setup Assistant (Legacy):

    • Supports devices running iOS/iPadOS earlier than 13.0.
    • Not recommended or supported.

Important

We recommend using Setup Assistant with modern authentication for all Automated Device Enrollment (ADE) scenarios with user device affinity. Avoid using legacy authentication.

tvOS and visionOS enrollment happens without user affinity. Authentication selection isn't required for these types of devices. For more information about authentication options, see Authentication methods for automated device enrollment.