This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
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.
I have Outlook 2013 (15.0.5603.1000) on Windows 10, and also configured as Exchange accounts. Got many password prompts today, and the account could never connect successfully all day despite using newly created app password.
The explanation is that every time you change something, bounce your network, etc you resolve a new DNS IP. Some of their servers are working fine, others are not. So what a lot of people think are fixes/workarounds are in fact just the normal intermittent nature of this issue.
It has nothing to do with eas.outlook.com or m.outlook.com, they all resolve to the same thing. But each time you resolve, you get a different IP. Some IPs are working, some are not. Disconnecting and reconnecting your network will have the same effect as changing the server name.
The people with modern auth properly set up are a limited impact (possibly configuration issue on their part, possibly not). There are plenty with this setup that have not had any issue. I'm simply saying it is worthwhile to update your account to the standards that they have been saying for a long time now they are going to start requiring, even if it doesn't solve the issue now, it will prevent an issue in the future.
You're a bit overly dramatic huh?
I'm not an MS employee, I can't focus on anything more with the issue.
All I can say is my clients supporting modern auth have had no issues the whole time.