macOS Blocklist/Allowlist policy fails with “Action not supported” on older enrolled MacsSolved

Hi @lucaas,

This can happen if the final effective configuration being deployed to the Mac differs between devices, even when the same policy appears to be assigned. For macOS Blocklisting/Allowlisting policies, check the following on an affected device:

1. Confirm whether the policy is assigned only through the intended dynamic device group, or whether it is also directly associated with the device or user.
2. Check for any other app blocklist/allowlist policies targeting the same Mac through another group, user assignment, or test policy.
3. Remove conflicting or duplicate policies if the same restriction is being applied from multiple sources.
4. Reapply the Blocklist Apps policy after cleaning up the assignments.
5. Compare the Action History status again after the effective profile is regenerated.

If the policy works for newly enrolled Macs but fails only on older enrolled Macs, also test the same blocklist policy with another known macOS app. That helps confirm whether the failure is caused by the policy deployment in general or by a specific app entry in the blocklist.

Regards,
Sienna Carter
Hexnode UEM

I’ve run into something similar with app restriction policies where direct assignment plus group assignment made troubleshooting confusing. The device page showed the policy, but the effective profile wasn’t always what we expected until we removed the extra assignment and deployed the policy again.