Last updated: July 24, 2026

How to configure corporate Google accounts on iOS devices?

This guide explains how to configure corporate Google/Gmail accounts on iOS, iPadOS, and macOS devices using a pre-built .mobileconfig file through ManageEngine MDM. Admins create an iOS/iPadOS or macOS profile, select Custom Configuration, and upload the provided configuration file after verifying it includes the correct PayloadType and a dynamic %email% variable. Publishing the profile then distributes the account setup to target devices, reducing manual configuration errors.

Description

To streamline the setup of corporate Gmail accounts on iOS devices, you can now configure them using a pre-built configuration file (.mobileconfig) through ManageEngine MDM. This method ensures consistency and reduces the chances of misconfiguration across devices.

Steps

  • Log in to the MDM Console and navigate to Device Management > Profiles.
  • Create or select a profile for iOS/iPadOS or macOS.
  • Download the configuration file from this link.
  • After downloading, upload the configuration file by following the steps below:
  • Go to Device Mgmt > Profiles > Create iOS/iPadOS Profile.
  • Select the Custom Configuration option from the list of policies.
  • Upload the downloaded .mobileconfig file.
  • Verify that the file includes necessary configuration keys such as PayloadType set to com.apple.google-oauth and EmailAddress containing a dynamic variable like %email%.
  • Click Publish to save the profile.

Sample Configuration File

You can copy the following content and save it with a .mobileconfig extension:

<?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>AccountDescription</key>
            <string>Google Account</string>
            <key>EmailAddress</key>
            <string>%email%</string>
            <key>PayloadDescription</key>
            <string>Configures a Google account</string>
            <key>PayloadDisplayName</key>
            <string>Google Account</string>
            <key>PayloadIdentifier</key>
            <string>com.apple.google-oauth.6685827E-1B07-4CB3-8893-FAE506EE7D8A</string>
            <key>PayloadType</key>
            <string>com.apple.google-oauth</string>
            <key>PayloadUUID</key>
            <string>6685827E-1B07-4CB3-8893-FAE506EE7D8A</string>
            <key>PayloadVersion</key>
            <integer>1</integer>
        </dict>
    </array>
    <key>PayloadDisplayName</key>
    <string>MEMDM Google Account</string>
    <key>PayloadIdentifier</key>
    <string>B890E0EF-F893-46BE-914F-AF14E13361F0</string>
    <key>PayloadRemovalDisallowed</key>
    <false/>
    <key>PayloadType</key>
    <string>Configuration</string>
    <key>PayloadUUID</key>
    <string>1485BEF4-9BFD-4634-89B8-E751FD934C40</string>
    <key>PayloadVersion</key>
    <integer>1</integer>
</dict>
</plist>

Final Steps

  • Save the file with a .mobileconfig extension.
  • Upload the file to the Custom Configuration section of the iOS profile.
  • Publish and distribute the profile to target devices.

Need Help?

If you have any doubts or need assistance, contact support at:

  • On-Premises: mdm-support@manageengine.com
  • Cloud: mdmcloud-support@manageengine.com

Frequently asked questions

Do I need to manually build the configuration file for corporate Google accounts?

No — you can download a pre-built .mobileconfig file and upload it directly as a Custom Configuration profile, which reduces the chances of misconfiguration across devices.

Which device platforms support this Google account configuration?

This is documented for iOS/iPadOS and macOS devices, configured through a Custom Configuration profile in MDM.

What should I verify in the configuration file before publishing it?

Confirm the file includes PayloadType set to com.apple.google-oauth and that EmailAddress uses the dynamic variable %email%, so each user's own address is applied automatically.