This will reset the primary auth method and you should be good to go.Īnd because I’m still pissed off, have some more rants around Skype. Simply use your favorite browser, open a Private session to or any other service associated with the Microsoft ID, and when prompted to login select the “Use password to login” option. Which is done by accessing any page that will trigger the login process, apart from the IE instance hosted in the Skype process. If you have your Skype account associated with Microsoft ID and have enabled Azure MFA as authentication provider for your Microsoft ID and using it as primary authentication, you will have to disable it. While the description doesn’t specifically mention my case, the root cause is the same.
Just goes to show you how often the different teams at MS talk to each other, or how much they validate code, even when it comes to things as fundamental as authentication.Īnyway, after wasting some more time in useless troubleshooting, I run into the following issue reported on the Skype Status page: So funnily enough, JavaScript is enabled and working OK, and does so across all other processes, passing any verification test I threw at it. Of course, the Skype folks decided to have their own take at implementing the login process instead of relying on the ADAL/MSAL libraries, so they use a host process which launches an IE instance instead. Skype worked just fine with another account. To find out whether your browser supports JavaScript, or to allow scripts, see the browser’s online help. This web browser either does not support JavaScript, or scripts are being blocked. Microsoft account requires JavaScript to sign in. Only to run into an even crappier experience – the moment I pressed the “use password” link, the embedded IE instance used for the login process threw in a JavaScript related error:
Talk about good user experience.Īnyhow, after trying few more times and getting nowhere, I decided to try the good old fashioned method of login via username and password instead. Then, Skype simply started showing the progress indicator over a blank window. Since the account I use is now associated with my Microsoft ID, and since I have two-factor authentication enabled on the account and actually configured Azure MFA as primary auth factor, after entering my username I received the familiar login prompt via the Authenticator app. I installed the latest version available and was immediately greeted with some login issues.
Well, few weeks later and a newer version, I finally had enough of this crap. I promised myself I will be patient this time, even though it was immediately visible how incomplete the product was. With the beginning of the new year, I tried to give the new Skype a chance, so I removed the classic version and took the new one for a test.
0 kommentar(er)
