Enrolled

A device state indicating the device has an active MDM enrollment profile and is communicating with an MDM server.

What to Know

Enrollment establishes the trust relationship between a device and its MDM server, enabling the server to push configuration profiles, install apps, run commands, and enforce policies. Without enrollment, devices operate as unmanaged consumer devices with no organizational oversight. Enrollment status directly determines whether IT can inventory, secure, or control a device.

Common Scenarios

Enterprise IT: All corporate-owned devices should be enrolled before deployment to users. Enrollment can occur automatically through ADE during Setup Assistant, or manually by installing an enrollment profile. IT teams should monitor enrollment status dashboards to catch devices that fall out of management due to profile removal or certificate expiration.

MSP: Client onboarding workflows typically include bulk enrollment of existing devices alongside ADE setup for new purchases. MSPs should track which devices are enrolled vs. awaiting enrollment to ensure complete coverage and avoid gaps in client billing or SLA compliance.

Education: Student devices are enrolled through ASM during initial provisioning or via manual profile installation for BYOD programs. Teachers and lab managers rely on enrolled status to deploy classroom apps, enable Shared iPad, and enforce content restrictions during instructional time.

In Addigy

Enrolled devices appear in the Addigy Devices list with a green status indicator when they are checking in successfully. Addigy displays the enrollment date, enrollment type (ADE, Manual, User Enrollment), and last check-in time. Devices that stop checking in may indicate profile removal, network issues, or expired MDM certificates.