Separate APP policies

Nice 😎
If APP Monitor shows the BYOD policy landing on the BYOD device and the COBO policy landing on the COBO device, then your filter split is doing exactly what you intended.

What I was trying to say (poorly!) is just this:

• APP (MAM) policies are designed mainly for “Unmanaged”/BYOD-style devices (MAM without full device management).
• For Android Enterprise COBO (Fully Managed/Dedicated/COPE) devices, settings like “block screenshots” are often better enforced via Android Enterprise device restrictions (configuration profiles), because those are device-level controls and are more consistent across apps.
  
  

So you’ve got two valid options:

1. Keep what you have (two APP policies + your filters). If it’s working and you’re happy, that’s totally fine.
2. Simplify long-term: keep one APP policy for BYOD only, and move “COBO differences” (like screenshot behavior) into Android Enterprise device restrictions instead of a second APP policy.
   
   

One small tip: if a user has both a BYOD and a COBO device, your approach still works, just make sure the filters stay mutually exclusive so you never end up with both APP policies applying to the same device context.

If you tell me whether your corp devices are Fully Managed (COBO) or COPE, I can point you to the exact restriction setting to use for screenshots so you don’t have to maintain two APP policies unless you really want to.

You’re on the right track, and your targeting approach (same user groups + split via filters) is exactly how most people keep APP manageable without multiplying groups.

If APP Monitor shows the BYOD policy landing on the BYOD test device and the COBO policy on the COBO test device, then your filter split is working as intended.

One small tip: keep an eye on users who have both a BYOD and a COBO device. Using the same user groups is fine, but make sure the filters remain mutually exclusive so you don’t accidentally apply both policies to the same sign-in context. 😊