Deploy a custom APN .mobileconfig to iOS devices with HexnodeSolved

Hi @ruthg_ ,

You can deploy a custom APN payload to iOS devices by creating a .mobileconfig profile using iMazing Profile Editor and uploading it to Hexnode UEM via Deploy Custom Configurations.

Step 1: Create the .mobileconfig file in iMazing Profile Editor 

1. Open iMazing Profile Editor and create a new profile.
2. Under General, configure:
   • Name: Custom APN Profile
   • Payload Scope: System
   • Identifier: Enter a unique reverse-DNS identifier (e.g., com.example.apn.private).
3. Add the Cellular / APN payload.
4. Configure the APN settings:
   • Access Point Name: <private-apn>
   • Username: Leave blank
   • Password: Leave blank
   • Authentication Type: PAP
   • Supported IP Versions: IPv4
5. Save the profile as a .mobileconfig file.

Step 2: Deploy the profile via Hexnode UEM

1. Log in to your Hexnode UEM portal.
2. Go to Policies > New Policy (or select an existing policy).
3. Navigate to iOS > Configurations > Deploy Custom Configurations.
4. Click Configure and upload your .mobileconfig file.
5. Move to Policy Targets to assign the policy to your target iOS devices or device groups.
6. Click Save to apply the policy.

Once the policy is applied, verify whether the APN updates automatically on the device.

Regards,
Isabel Lora
Hexnode UEM

What about the Identifier field in iMazing? It marks it as required, but does it need to match anything specific from Hexnode or the carrier?

The Identifier does not need to match a carrier value or a Hexnode value. Apple requires configuration profiles to have a unique reverse-DNS identifier so iOS can distinguish one profile from another.

A generic format like the following is fine:

com.example.apn.private

If you later create an updated version of the same APN profile, you can use a new identifier such as:

com.example.apn.private.v2

In many cases, iMazing may prefill the Identifier automatically when you create the profile. You can keep the generated value as long as it is unique and follows the reverse-DNS style.

Regards,
Isabel Lora
Hexnode UEM