Apply different policies to Android tablets under the same Microsoft Entra domainSolved

Participant
Discussion
3 weeks ago Aug 18, 2026

I’m managing Android tablets enrolled in Hexnode with Microsoft Entra. Right now, I have a Dynamic Device Group based on the Entra domain, and a policy is associated with that group.

I need to enroll a second set of tablets under the same Entra domain, but these devices should get a different policy. Some of the new tablets are the same model as the existing ones, so using the model as a group condition will not really separate them.

What is the best way to set up the criteria so the new tablets don’t get picked up by the existing dynamic group and receive the wrong policy? I’m also open to applying the second policy manually after enrollment if that’s cleaner.

Replies (1)

Marked SolutionPending Review
Hexnode Expert
3 weeks ago Aug 18, 2026
Marked SolutionPending Review

Hello @mila_diaz ,

Since both sets of Android devices share the same Microsoft Entra domain, the domain alone should not be used as the only Dynamic Device Group criterion if different policies need to be applied.

A device should ideally match only one of the groups that has a policy assigned to it. Otherwise, the device may receive both policies, and settings from overlapping policy payloads can conflict.

You can handle this in either of these ways:

1. Use a unique device naming pattern for the new tablets If the new set can be enrolled using a separate QR code that applies a different device name format or prefix, you can use that naming pattern in the Dynamic Device Group criteria.

For example:

  • Existing group: Entra domain matches “<domain>” and device name does not match the new naming pattern.
  • New group: Entra domain matches “<domain>” and device name matches the new naming pattern. This keeps both groups dynamic while preventing overlap.

2. Use a Custom Device Group for manual assignment If there is no reliable attribute to distinguish the devices dynamically, place the required devices in a Custom Device Group after enrollment and associate the second policy with that group.

The important part is to update the original Dynamic Device Group as well. If the original group only checks for the Microsoft Entra domain, the newly enrolled tablets may still be added to it. Add an exclusion for the new device name pattern in the existing group criteria.

Then create or update the second group to include the new device name pattern. After that, associate the appropriate policy with each group.

Regards,
Simon Scott
Hexnode UEM

Save