Create and deploy configuration profiles to users within your organization.
Configuration profiles streamline the process of setting up a large number of devices. Custom calendar and email settings, network settings (like WiFi and VPN settings), certificates, and device restrictions, are some of the properties you can configure using configuration profiles.
You have several options for deploying configuration profiles:
Using Apple Configurator 2, available in the App Store.
In an email message.
On a webpage.
Using over-the-air configuration as described in Over-the-Air Profile Delivery and Configuration.
Over the air using a Mobile Device Management server.
Define a Profile
Configuration profiles are stored in a property list format, which any XML tool can read and write.
The configuration property list contains the properties listed in the TopLevel object. These properties describe the profile and the rules for deploying it. Specific configuration values are stored in an array of payloads in the
Each payload's contents contain profile-specific keys (see Profile-Specific Payload Keys) and keys that are common to all payloads (see the following list of key definitions).
The payload type, specified on each payload domain's reference page.
The version of this specific payload.
The reverse-DNS-style identifier for the payload. This identifier is usually the same as the TopLevel value, with an additional component appended.
The globally unique identifier for the payload. The actual content is unimportant, but must be globally unique. In macOS, use
uuidgento generate UUIDs.
The human-readable name for the profile payload. The name is displayed on the Detail screen and doesn't have to be unique.
The human-readable description of this payload. This description is shown on the Detail screen.
The human-readable string containing the name of the organization that provided the profile. This value doesn't need to match the organization payload value in the enclosing dictionary.
Encrypt and Sign a Profile
Both iOS and macOS support using encryption to protect the contents of profiles from unauthorized access. The encrypted profile can only be decrypted using a private key previously installed on a device. To encrypt a profile:
Payloadarray and serialize it as a property list. Note that the top-level object in this property list is an array, not a dictionary.
CMS-encrypt the serialized property list as enveloped data.
Serialize the encrypted data in DER (Distinguished Encoding Rules) format.
Set the serialized data as the value of as a data property list item in the profile, using the
Signing a profile guarantees data integrity. To sign a profile, place the XML property list in a DER-encoded, CMS Signed Data structure.
Example SCEP Configuration Profile
The listing below shows the contents of an example profile, containing a Simple Certificate Enrollment Protocol (SCEP) payload.