This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(112.00000000000001, 80%, 20%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
We have a MTR room (yealink A20 with CTP18).
I can sign in with the teams room account (licensed) on the A20 just fine, but on the touch the device loops back to sign in after the ”regestering device” and ”company portal” progress bars. Its running latest firmware and the may Teams version (tried updating via teams admin portal without luck)
The account has no MFA, excludes from all conditional access and all Intune compliancy policies. Hardware firmware updated , factory reset. Nothing seems to work, though it did work once before until one day the device disconnected from the host. I remember being able to sign in to the A20 once I deleted it from AAD , though not sure.
It seems like a stale device, that it’s somehow related to Intune or Android.
It’s frustrating because these devices are supposed to be certified for teams, cost thousands of dollars per room and then IT still cant get them to work reliably.
I need a good guide of a checklist I can follow to see what the issue might be. Since the account itself seems fine I figure it has to be some colliaion with the CyP18 and Microsofts Intune servers during sign in.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(112.00000000000001, 24%, 20%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJM%3C/text%3E%3C/svg%3E)
Hi @Agneum
Are there any error messages when you login in Microsoft Teams Room?
Firstly, please check if the Microsoft Teams Rooms device is loaded with the latest version of the app.
Then, you could try to change another network connection to determine if this problem is related to your network.
In addition, please notice if the time was correct set up on the device. Some customers fixed clock and activated 'internet time synchronization' and after reboot the device, it was able to log in again.
Hi @JimmyYang-MSFT ,
There are no errors displayed att all. Just to see if I could sign in to another account I tried even to sign in with a global admin account on it that has E3 license, then I got "something went wrong" generic message in red. If you keep trying to sign in with the room account multiple times, I think on the third attempt it does let you through, but it doesn't display the room name, shows no booked meetings, it's signed in to some unkown account.
The network should be no problem, our router does not block any traffic , we use no VLANs, our setup is very 'friendly'. Then again if this was the issue then surely the A20 device connected to the same network switch would fail.
I tried updating the touch panel to the latest version via Teams Admin Center, still no luck.
What is frustrating is that I cannot see the current time of the device, nor set in the time zone. The Teams app for android just doesn't seem to allow it. There are only a few options for me to select in the settings menu. I can of course set up IPV4, change admin password and things like this, but not set the clock which I do know is a classic source of many IT-related issues.
I will provide a screenshot of how it looks, so you can see, there is no option to set in the time.
Hi @Agneum
I found a guidance shows this problem troubleshooting steps. Hope it can help you.
Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link.
It turns out I had to Allow Android device administrator, as it was a restriction set in Intune. Yealink support sent out a guide there was more things I did, but got it working. It's definately Intune enrollment thing.
Thanks for sharing your ideas about it. So do you mean this problem has been fixed now?
Yes, Android Device Manager needs to be enabled as per above. There can be multiple reasons the acc fails to sign in, typically enrollment restriction, device restriction etc.
"There are two kinds of restrictions. Azure restricts the total number of simultaneous account logins, Intune restricts the total number of simultaneous login devices for accounts, and the limit configured by Intune is applied to the company portal. In other words, if the device does not have company portal software (such as PC) installed, it will not be intercepted by Intune login"
I will upload a document that will help others with the same problem, and I hope Microsoft Intune team can give better error codes to the end user for the various errors that can occur (device enrollment restrictions, etc).
The document:
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(291.2, 34%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMS%3C/text%3E%3C/svg%3E)
@Agneum We had the same issue with Yealink devices. We fixed it by enabling Android device administrator in Endpoint Manager because these devices do no support Android Enterprise (yet).
For more information, take a look here:
https://learn.microsoft.com/en-us/mem/intune/enrollment/android-enroll-device-administrator
Yes, I believe this setting for BYOD scenario was set to "blocked" in our endpoint manager. I could also see the account had enrollment status "failed", when trying to enroll.
The common issues seems to be a limit on maximum devices to enroll to AD per user (can be changed from AAD -> Device s -> device settings)
There is also a restriciton for up to 15 devices a user can enroll in Endpoint manager, which I believe can be wiped via help from support ticket to MS or by deleting the devices from "all devices" and bulk device actions.
I can't set in the time anywhere. There are only a few options to choose.