![]() ![]() Using the longer version forced it to go to Azure AD for authentication but the issue was that he’d get login window (check this blog post for a screenshot), enter the email address (not sure why but didn’t work – because that’s not an Azure AD account I guess?), and whereas usually you’d get the next screen to enter a password in this case it would loop back to the inital page to enter the email address. ![]() Due to the vagaries of our environment he had to sign in as as simply signing as was triggering internal auto-discover and due to how our environment is setup it wasn’t finding the account. :)Ī colleague of mine was trying to sign in with an O365 mailbox in his Outlook 2016. This may not be the solution for all, but perhaps for some.This vague post is probably not going to help anyone but it’s something I spent 45 mins of my life troubleshooting today and maybe it will help the 1 other person in the world with the same issue and save him/ her some time. Wait 5 minute, pray & hopefully it's solvedĪfter which I could re-register the account I had happily deleted & reach the exchange server.Find the effected user & disable the 'Multi-factor authentication status'.Navigate to Users | Active users & select the 'Multi-factor authentication' tab a the top. ![]() The solution I applied (which may help some of you guys out there & save you some time :) was Consequently, I kept receiving the authentication prompt. Unfortunately, this W/E I my mobile phone died a death and the authentication service no longer could reach the app for secondary authentication. I had activated this function some weeks ago. It then dawned on me that MS recently made a push for 'Multi-factor' authentication, i.e better user security, which think many of us may agree with is not a bad idea.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |