Outlook 2016 doesn't accept password or 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.

Hi all,

I had contacted some of those that posted in this thread yesterday and shared their Outlook.com information to the service team to investigate further. The service team is investigating. Just wanted to let you know it's still being followed up on.

I also have Outlook 2013 and Outlook 2016 with numerous outlook.com accounts configured and monitoring. If I catch an auth prompt, I share that to the team as well. My accounts are configured as Exchange accounts in Outlook and in the last few days have not seen but one prompt. If you are using POP or IMAP, please consider connecting with Exchange for the most robust protocol.