Forum Discussion
Poly devices and the transition to Android Open Source Project (AOSP)
Today we had a handful of our Poly Teams meeting devices sign out and then refused to re-enroll afterwards. Our devices included Poly Studio X30, X50, X70 and TC8 touch panels. on the screens that were attached to the equipment, upon failure of sign-in and re-enrollment we saw a message on the screen saying "Signing out... This device isn't enrolled in device administrator. Contact your admin". The devices were still available in the Teams admin center so I was able to retrieve diagnostics from the devices. Within the CompanyPortalEventsLog* file in the root of the zip file containing the diagnostic data there was the following line
TIMESTAMP CompanyPortalReasonCode: WORK_PLACE_JOINED CompanyPortalStatus: UNKNOWN FailureReason: ENROLLMENT_RESTRICTIONS
After further investigation, the devices also had updates applied to them during the early morning hours.
After some searching and reading through this article Moving Teams Android Devices to AOSP Device Management | Microsoft Community Hub - even though my devices weren't supposed to be available until February, I followed Step 1 to create an enrollment profile for Android Open Source Project (AOSP) with the settings outlined. However, in my tenant, "For Microsoft Teams Devices" was still being marked as preview. Once this profile/policy was in place I was successful in logging our devices in with their resource accounts. Lucky us that it happened on Friday and not one of our core work days. So, watch out for your Android Teams Room devices with this change/transition happening. Try to work ahead of it to prevent Teams Meeting Room Android devices and Android phones from experiencing downtime in your offices and set the policy up as soon as you can. There's a secondary step to make sure to have a Compliance policy in place for AOSP devices as well, be sure to have that set up so that your devices are still flagged as Compliant in your tenant. https://learn.microsoft.com/en-us/mem/intune/protect/compliance-policy-create-android-aosp
If anyone else sees any other symptoms of this issue post them to this thread to help others troubleshoot.
This documentation is indicating that the release of the Teams firmware in the 2nd half of 2024: Migration guide Android AOSP management for Microsoft Teams Android devices - Microsoft Teams | Microsoft Learn Also it mentions in the steps that this is a manual update that needs to be applied... And now that I'm thinking about it, we do manual updates in our console to test first and then slowly move them out to inventory of devices. So, my associates applied the update without realizing it.
At this point in the game with the rollout imminent, just get the policy in place. It took me a few minutes and it will lead to fewer issues in your environment with Teams Android devices.
we have Poly CCX devices and created AOSP enrollment profile. But it doesn't allow me to sign in with AOSP, instead it used ADA to sign in.
maybe there is difference between Poly Studio Meeting and Poly Phones.I don't think it was any issue related to the firmware, but issues related to backend services. There were devices from AudioCodes that have the firmware that supports the New AOSP - if that's the case then most likely there are services and whatnot to support it. So, my theory is that we hit some infrastructure that may have had some code deployed to it that Microsoft is moving towards and not compatible with the classic enrollment flow.
afaik the firmware for AOSP is not yet generally released in TAC so any device would still need to enroll using the legacy device administrator. what is the firmware version installed on the device?
