MicrosoftHi BillyD , I think it is a problem with the MFS challenge for normal user. If the normal user use MFA to login, you should get the MFA challenge on you desk if you use the weblogin. Which vendor do you use, if Yealink it would the best to open a ticket with Yealink support and the can check the logs.
Hi hbunkradt, We use Poly CCX 500 phones. Yes, our users are required to use Microsoft MFA, it usually, and still does on old firmware, pop up on the phone display and requires using either the Authenticator app or by sending a text message to the user, before the login process continues. The only thing I get on the computer is, entering the code, logging in with the user, entering the password if needed, and acknowledging the broker login. I saw the original post on Poly/HP's site by NateL1010, and they basically said you have to take it up with Microsoft, since it's their software. Seems the new process doesn't play very well with multi-factor authentication.
Hi NateL1010
If MFA required through CA policy, two options:
Interesting, thanks for sharing. It sounds like there are two separate issues here.
Hi NateL1010, I saw the same result, problem seems to be with the MFA. We too have some common area phone accounts, and during my testing, those did login properly via the web browser, although it did log out during the upgrade process. Hopefully Microsoft can use these comments to do some more troubleshooting/testing to get the process worked out. Thanks for your testing/comments as well, Sir!
hbunkradtGlad it's not just me. We also have several Yealink MP54s and MP56s, but I haven't done any testing with those, as I wasn't sure they had released the AOSP firmware yet. 99.9% of our deployment is on the Poly CCX 500s, so that was the platform I was testing. Until we know for sure, I'm holding on the old firmware. Thank you for your testing, it is a great help.
In my case I have the Poly CCX 400 set up as Teams Common Area Phones with Teams Shared Device licenses. These common area phone accounts do not have MFA enabled so I didn't encounter any issues with MFA when using Device Code Authentication to remotely sign in the devices that got signed out after the AOSP update.
BillyD have try to reproduce the problem with my yealink mp54 and it looks like, something is change with the latest CP firmware. The MFA prompt is no longer shown on my desk where I use microsoft,com/devicelogin and instead on my phone display. This is not working with my yealink mp54E2 on AOSP. I have open a MS ticket for deeper investigation now
