Automatically apply policies to Apple Configurator-enrolled iPads synced from ABMSolved

Participant
Discussion
2 weeks ago Jun 04, 2026

We are enrolling second-hand iPads using Apple Configurator and adding them to Apple Business Manager. The devices are assigned to our Hexnode MDM server in ABM, and an ADE enrollment profile is associated with them in Hexnode.

The issue is that the policy linked to the enrollment setup does not seem to get applied automatically after enrollment. We expected the policy to attach as soon as the iPad enrolls.

Is there a way to choose a specific Hexnode enrollment profile directly from ABM instead of the default one when assigning the device to the MDM server? Or is there a better way to make sure these iPads receive the required policy automatically?

Replies (2)

Marked SolutionPending Review
Hexnode Expert
2 weeks ago Jun 04, 2026
Marked SolutionPending Review

Hi @isaiah,

Apple Business does not provide an option to preselect a specific Hexnode enrollment profile while assigning a device to an MDM server. From Apple Business, you can only assign the device to the required MDM server. During activation, the iPad contacts the assigned MDM server and receives the enrollment configuration from Hexnode.

If the enrollment profile or its associated settings were modified after the ADE payload had already been deployed to the device, those changes will not be reflected on that already activated device. In that case, the device must be factory reset and activated again so it can fetch the latest ADE enrollment profile.

For policy assignment, a more scalable approach is to use a device group:

  1. Go to Manage > Device Groups in Hexnode.
  2. Use the default iOS device group, or create a new dynamic device group with criteria that match the enrolled iPads.
  3. Associate the required policy with that group.

Once configured, newly enrolled iOS devices that match the group criteria will be added automatically and receive the assigned policy.

Regards,
Sienna Carter
Hexnode UEM

Marked SolutionPending Review
Participant
2 weeks ago Jun 04, 2026
Marked SolutionPending Review

That makes sense. Since factory resetting adds an extra step for our deployment flow, we went with the dynamic device group method instead. Assigning the policy to the iOS dynamic group worked better for newly enrolled iPads.

Save