Hello All,
PKlapwijk We use this at the moment as adviced by MS, it does find some older android admin devices but that is no issue for us:
((device.deviceOwnership -eq "Company") and (device.deviceOSType -contains "Android"))
We do seem to have a problem with this and i like to know how you guys have managed this in your environment(ps i am not trying to steal the topic).
I have assigned my AndroidEnterprise policies to the dynamic group(device group) stated in this message.
When we enroll a device the policies are not deployed fast enough because the device is still unknown in azure as @AndyH16 @JonMRoberts1984 said before.
I know by now this is wrong and i am trying to fix it:
This preview supports the following features for Android Enterprise fully managed devices:
- Device configuration for user groups
Do you have a group with all users assigned or do you add a user to a special group prior to an enrollment.
Thank you for your thoughts on this.
Regards,
Wietse