Forum Discussion

jangliss's avatar
jangliss
Iron Contributor
Apr 13, 2021
Solved

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 firmwa...
microsoft teams
  • jangliss's avatar
    jangliss
    Jun 30, 2021

    So I have a small update from Microsoft on this, and it's more of a temporary fix from what I understand.

     

    1. Login to https://endpoint.microsoft.com/#blade/Microsoft_Intune_DeviceSettings/DevicesEnrollmentMenu/enrollmentRestrictions
    2. Create a new Device Type Restriction
    3. Give it a name
    4. On "Platform Settings" change "Android Enterprise (work profile)" to BLOCK
    5. Make sure "Android Device Administration" is set to ALLOW
    6. Click Next
    7. Click Next
    8. Under Assignments click Add Group and select the group of users that are signing into devices.
    9. 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.

Jacob_B's avatar
Jacob_B
Copper Contributor
Apr 14, 2021
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.
KruthikaPonnusamy's avatar
KruthikaPonnusamy
Icon for Microsoft rankMicrosoft
Apr 14, 2021
It 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.
  • Jacob_B's avatar
    Jacob_B
    Copper Contributor
    Apr 15, 2021
    I sent the ticket information in a DM. The ticket with Azure was closed because it was a 'duplicate' ticket. Yealink also said it may be a problem with too many devices for the user, but only one is assigned and I have set my company limit to 20, so that should not be an issue. I am going to try to downgrade it today, similar to what jangliss did, to see if my problem is fixed.
    • jcoopr's avatar
      jcoopr
      Copper Contributor
      Apr 15, 2021
      If possible, could you send this ticket information to me as well? I am deploying an MP56 with the same firmware/Teams version, and the same problem.

      Also, to confirm, are you seeing the "Oops, you can't access this right now." error when attempting to login?
      • Jacob_B's avatar
        Jacob_B
        Copper Contributor
        Apr 15, 2021
        DM sent.
    • jangliss's avatar
      jangliss
      Iron Contributor
      Apr 15, 2021

      Jacob_B 

       

      I am assuming you are using ADFS? Did Microsoft gather the ADFS logs from your failed attempts? I'm working on gathering those myself.

       

      I've gone back and done additional testing and it doesn't appear to be limited to a particular vendor. I've tested with Poly CCX 400, CCX 500, and CCX 700, AudioCodes HD450, Yealink T56A, T58A, and MP56.  It's after deploying the February update which appears to be bundled with most of the latest firmwares from the vendors, things break.  Going to roll back a few firmware and do additional testing to verify.

      • Jacob_B's avatar
        Jacob_B
        Copper Contributor
        Apr 15, 2021
        I was not able to find any failed logins in any of the Microsoft cloud services, it's like the device is not connecting or seeing Microsoft at all. I checked my firewall to verify that no ports needed to access and run Teams are being blocked. Downgrading did not help, so no luck there. I sent a video of the issue to Microsoft today for them to view the problem that I am running into.
  • jangliss's avatar
    jangliss
    Iron Contributor
    Apr 15, 2021
    DM sent with ticket number. I did speak with a contact at Yealink yesterday and they suggested a possible issue with device count limits, but I realized this morning I'm trying to login to the same device I already have registered under the tenant so it shouldn't (in theory) be that.

    Rolling back to an earlier firmware and Teams app from last year seems to resolve the issue. Upgrading again breaks it.

Resources