Using classic Outlook for Windows in business environments
Nope. Just now "authentication error"
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I have this problem - Outlook 2016 doesn't accept password or app password - and i think it is a growing World wide Microsoft problem :-(
See also here: https://www.reddit.com/r/Outlook/comments/19dx64p/outlook_2013_windows_10_suddenly_not_accepting/Outlook gives me this: (startede yesterday)
I have 2 PC's with HOTMAIL accounts in Outlook 2016 ...
They both have this error.
I do get mails ... but I can´t send mails. Yesterday it did work for 1-2 hours ... but right now the error is there all the time :-(
Please help me.
Thanks in advance
Pierre
Using classic Outlook for Windows in business environments
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Nope. Just now "authentication error"
Maybe it's fixed?
You need to enable 2FA and use modern authentication, which Outlook 2016 should support by default now. App password doesn't solve the current issue (though it should work fine once this is resolved, at least until they totally do away with app passwords).
For me, my phone has prompted me a few times yesterday and today but I just refresh my inbox and it goes away and mails send and receive fine. So still not fixed, but better than a few days ago. Why it was fine for a couple days and now backtracked, who knows.
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more
The issue is back on our accounts too.
We're in a loop. It works for several hours without any action by us. And while staying in the same network it stops again for several hours.
The new test account I created some days ago has absolutely not the issue.
So this looks more and more that the account itself is part of the problem. Maybe a special setting is there on the new account, but not on the ones that existed as the issue came up end of January.