Forum Discussion
Yealink Devices - Not Compliant
- Mar 06, 2024
Teams devices (like Yealink) are automatically registered in Intune. See here for example: phones-displays-deploy They are registered as Device Administrator type of devices and not as Android Enterprise. This is by design. Why they are showing up as non compliant should be related to the compliancy policy that is attached to these devices. When you look at the device details intune > Device compliance you should see the Compliancy policy targeted to this device.
So Intune is actually managing the devices but with an old protocol (Device Administrator). Be aware that Device Administrator is deprecated this year August: https://learn.microsoft.com/en-us/mem/intune/enrollment/android-enroll-device-administrator Teams devices need to use AOSP (Android Open Source Project) management, see here: https://techcommunity.microsoft.com/t5/intune-customer-success/microsoft-intune-ending-support-for-android-device-administrator/ba-p/3915443#:~:text=Due%20to%20these%20changes%2C%20Microsoft,running%20Android%2014%20or%20earlier.
"Microsoft Teams certified Android devices will be migrated to Android Open Source Project (AOSP) management in Intune with a firmware update in the first half of the 2024 calendar year. Policies will not be migrated automatically, so IT admins will need to create the appropriate new policies for AOSP management. You can read more about this in the Microsoft 365 or Microsoft Intune admin center Message center under MC665936."
------
Please click Mark as Best Response & Like if my post helped you to solve your issue.
This will help others to find the correct solution easily. It also closes the item.
If the post was useful in other ways, please consider giving it Like.
Teams devices (like Yealink) are automatically registered in Intune. See here for example: phones-displays-deploy They are registered as Device Administrator type of devices and not as Android Enterprise. This is by design. Why they are showing up as non compliant should be related to the compliancy policy that is attached to these devices. When you look at the device details intune > Device compliance you should see the Compliancy policy targeted to this device.
So Intune is actually managing the devices but with an old protocol (Device Administrator). Be aware that Device Administrator is deprecated this year August: https://learn.microsoft.com/en-us/mem/intune/enrollment/android-enroll-device-administrator Teams devices need to use AOSP (Android Open Source Project) management, see here: https://techcommunity.microsoft.com/t5/intune-customer-success/microsoft-intune-ending-support-for-android-device-administrator/ba-p/3915443#:~:text=Due%20to%20these%20changes%2C%20Microsoft,running%20Android%2014%20or%20earlier.
"Microsoft Teams certified Android devices will be migrated to Android Open Source Project (AOSP) management in Intune with a firmware update in the first half of the 2024 calendar year. Policies will not be migrated automatically, so IT admins will need to create the appropriate new policies for AOSP management. You can read more about this in the Microsoft 365 or Microsoft Intune admin center Message center under MC665936."
------
Please click Mark as Best Response & Like if my post helped you to solve your issue.
This will help others to find the correct solution easily. It also closes the item.
If the post was useful in other ways, please consider giving it Like.
- UpNorthIntuneMar 07, 2024Iron ContributorI setup a Android Device Administrator policy within Intune, setup and logged in to the Yealink device. And the device is now Compliant.
Very happy with your quick reply and suggested fix.
Many Thanks - UpNorthIntuneMar 06, 2024Iron ContributorHi SebastiaanSmits
Many thanks for the speedy reply.
As luck would have it, the office has a spare Yealink coming in today 🙂
Will try and create a policy and profile for it, and hopefully get it reporting as Compliant.
Will report back later.
Thanks