Forum Discussion
Teams Phone device refuse login with 1449/1.0.94.2021033002 firmware and ADFS
Has anybody been using ADFS with Teams noticed an issue with the last two firmware updates, when performing logins off-network?
I have a customer running Yealink MP56 phones and the latest firmware 122.15.0.36 running Teams App 1449/1.0.94.2021022403 or 1449/1.0.94.2021033002 can no longer login using either the device login code or typing user/pass. The login seems to get stuck in a loop between device registration and preparing the device.
I suspect this is partially to do with the ADFS configuration not using UPN for authentication, but this wasn't an issue prior to 1449/1.0.94.2021022403.
So I have a small update from Microsoft on this, and it's more of a temporary fix from what I understand.
- Login to https://endpoint.microsoft.com/#blade/Microsoft_Intune_DeviceSettings/DevicesEnrollmentMenu/enrollmentRestrictions
- Create a new Device Type Restriction
- Give it a name
- On "Platform Settings" change "Android Enterprise (work profile)" to BLOCK
- Make sure "Android Device Administration" is set to ALLOW
- Click Next
- Click Next
- Under Assignments click Add Group and select the group of users that are signing into devices.
- Click through to finish the setup
Wait a few minutes, and reboot the phone, login again.
I'm still trying to find out how to resolve the issue correctly, but this seems to have helped most of the cases I've had issues with so far.
82 Replies
- We are having the same issue with Poly C60 conference room phones once updated to firmware 7.0.2.1071. This firmware comes with Teams App 1449/1.0.94.2021022403 and we get the same login loop. I've tried updating to Teams App 1449/1.0.94.2021033002 but problem persists. I have tried both the original web login method as well as the new remote provision/login method and both result in the same login loop.
If I roll the firmware back to 5.9.5.3153 and Teams App 1449/1.0.94.2020121001, I can web login the phone again without issue. I can then fully upgrade the phone's firmware and Teams App version to latest and the phone will stay logged in. However, if I log it out, I can't log it back in as it gets stuck in the same loop. - I originally opened this thinking it might have been ADFS related, but also seeing this across tenants not using ADFS. This seems like a big issue!
- The biggest issue of all is that there's no way to stop these phones from automatically getting the update eventually! Deferring for 90 days is the best we can do and that's a very manual process to have to set each and every phone as they come in. Imagine how rough it's going to be when you have hundreds of phones!
- Has anyone found a real solution to this issue? I am about to start rolling back firmware but was hoping someone has an answer.
- KruthikaPonnusamy
Microsoft
Are you able to open a support ticket with Microsoft? Can you send me the ticket number as a message you've opened it?- Don't know if this helps anyone, but I opened tickets with Microsoft Teams support, Azure support, and Yealink. So far, everyone is saying it's someone else's issue. This has been going on for about 9 days.
- KruthikaPonnusamyIt would be helpful if you can send me a message with the Microsoft Teams ticket details. I am a PM in the team, and would like to see this ticket.
- Same issue here. Yealink MP54 and AudiocodesC450HD.
- Same issue here. Yealink VP59.
- I'm having the same issue with a Yealink T55A. Once the update was completed, the phone will not receive a device code for provisioning.
