Category filter

Configuration profile to disallow account changes on iOS

This document helps you create a configuration profile to disallow account changes on iOS devices.

Administrators can disable account changes on the devices to limit the ability of users to make changes to account configurations. This can help to prevent unauthorized changes to Apple ID, email, contacts, or other account configurations deployed on the device. By disabling account modification, IT administrators or owners of the device can maintain control over the device and ensure that these configurations are not modified if the device is lost or stolen. With Hexnode’s Deploy Custom Configuration feature, you can push a profile to disallow users from making any account modifications on iOS devices.

Note:

This configuration profile is supported only on supervised iOS devices running iOS 7 and above.

Disclaimer:

The sample configuration profiles provided below are created using various profile creator applications.

Disable account modification

Here is the .plist file of a configuration profile to disable account modification on your iOS devices:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>PayloadContent</key>
    <array>
        <dict>
            <key>allowAccountModification</key>
            <false/>
            <key>PayloadIdentifier</key>
            <string>com.example.myrestrictionspayload</string>
            <key>PayloadType</key>
            <string>com.apple.applicationaccess</string>
            <key>PayloadUUID</key>
            <string>53bec1be-ffec-4f88-acbd-b02aee8f04a9</string>
            <key>PayloadVersion</key>
            <integer>1</integer>
        </dict>
    </array>
    <key>PayloadDisplayName</key>
    <string>Restrictions</string>
    <key>PayloadIdentifier</key>
    <string>com.example.myprofile</string>
    <key>PayloadType</key>
    <string>Configuration</string>
    <key>PayloadUUID</key>
    <string>6020206c-12c2-4ada-987a-dd4c560ca73a</string>
    <key>PayloadVersion</key>
    <integer>1</integer>
</dict>
</plist>

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">

<dict>

<key>PayloadContent</key>

<array>

<dict>

<key>allowAccountModification</key>

<key>PayloadIdentifier</key>

<string>com.example.myrestrictionspayload</string>

<key>PayloadType</key>

<string>com.apple.applicationaccess</string>

<key>PayloadUUID</key>

<key>PayloadVersion</key>

</dict>

</array>

<key>PayloadDisplayName</key>

<string>Restrictions</string>

<key>PayloadIdentifier</key>

<string>com.example.myprofile</string>

<key>PayloadType</key>

<string>Configuration</string>

<key>PayloadUUID</key>

<key>PayloadVersion</key>

</dict>

</plist>

What happens at the device end?

After associating the configuration profile policy on the device, the user will be unable to modify their accounts. For instance, the user cannot make changes to the configured Apple ID from the device settings.

Notes:

To create and customize configuration profiles, you can use tools like Apple Configurator, Profile Manager or manually create them using text editors.
Use non-encrypted .mobileconfig, .xml, or plist files to deploy profiles across devices.
Ensure that you do not associate conflicting configurations with the devices.
Use wildcards to fetch key values from the portal.
It is recommended to manually validate the configuration profile on a system before executing it in bulk.
Hexnode will not be responsible for any damage/loss to the system on the behavior of the configuration profile.

Need more help?

Raise a Ticket

Ask Community

Chat With us