This website is designed for IT and MDM administrators. It contains all aspects of mobile device management (MDM) settings as defined by Apple. If you are an Apple Developer, you can also refer to the following two documents:
What is mobile device management (MDM)?
iOS devices with iOS 5 or later, tvOS devices with tvOS 9 or later, and Mac computers with OS X 10.7 or later have a built-in framework that supports mobile device management (MDM). MDM lets you securely and wirelessly configure devices, whether they’re owned by the user or your organization. MDM includes updating software and device settings, monitoring compliance with organizational policies, and remotely wiping or locking devices. Users can enroll their own devices in MDM, and organization-owned devices can be enrolled in MDM automatically using Apple School Manager or Apple Business Manager.
After enrolled, you can wirelessly distribute, manage, and configure apps and books purchased through Apple School Manager, Apple Business Manager, or enterprise apps developed in-house. Users can install apps themselves, or apps can be installed automatically depending on the type of app it is, how it’s assigned, and whether the iOS or tvOS device is supervised.
There are a few concepts to understand if you’re going to use MDM, so see next how MDM uses configuration profiles and payloads.
How does MDM work?
Mobile device management is enabled when an MDM solution sends a properly configured enrollment profile to an Apple device. After the enrollment profile is approved, either by the device or the user, configuration profiles containing payloads are delivered to the device. The settings in the payloads determine how the device will function.
What are configuration profiles?
A configuration profile is an XML file that consists of payloads that load settings and authorization information onto Apple devices. Configuration profiles automate the configuration of settings, accounts, restrictions, and credentials. These files can be created by an MDM solution or Apple Configurator 2, or they can be created manually.
Because configuration profiles can be encrypted and signed, you can restrict their use to a specific Apple device and—with the exception of user names and passwords—prevent anyone from changing the settings. You can also mark a configuration profile as being locked to the device. The configuration profile can be removed only by wiping the device of all data or by entering the password associated with the configuration profile. Accounts that are configured by a profile, such as Microsoft Exchange accounts, can be removed only by deleting the configuration profile.
Note: Only configuration profiles manually installed need to be signed, encrypted, or locked. Configuration profiles pushed to Apple devices from your MDM solution don’t need to be signed, encrypted, or locked.
Why are there two types of configuration profiles?
Configuration profiles can be sent to users or devices, or groups of users or groups of devices.
You may also want to create separate configuration profiles for specific devices (such as iPhone devices) or a group of users (such as students). For information, see Payload best practices.
If your MDM solution supports it, you can distribute configuration profiles as a mail attachment, through a link on your own webpage, or through the MDM solution’s built-in user portal. When users open the mail attachment or download the configuration profile using a web browser, they’re prompted to begin configuration profile installation.
To learn how to prepare your organization to deploy Apple devices, see:
Note: You can use Apple Configurator 2 to add device configuration profiles (automatically or manually) to iOS and tvOS devices. To add device or user configuration profiles containing macOS-specific settings, use a third-party mobile device management (MDM) solution or Profile Manager, part of the macOS Server app.
What is a payload?
A payload can be configured to manage specific settings on Apple devices. For example, you can have different payloads to require a complex passcode, populate an Exchange account with all the Exchange server information, and add a VPN configuration to a device. Even though each payload has its own unique settings, all payloads are defined by the following:
The operating system or systems that the payload supports
The channel that does the payload work
Whether the payload requires the Apple device to be supervised
Whether the payload is exclusive or whether it can be combined with other payloads of the same type
Whether the payload can have duplicates
After payloads are configured, they are saved in a configuration profile.