Outlook 2016 doesn't accept password or app password

Additional hint:

My account is now working set up as EWS Account with 2FA on and normal account password (not with app password). FYI: My account always has Microsoft Authenticator app connected to this account, even when 2FA is swiched of.

I have always tried it once with 2FA switched off and then with 2FA switched on and app password over the last few days with a slight delay. But for me there is no explanation why it now works with 2FA swiched on and my normal account password (no app password).

Lets see how long it works.

The thing is that we, in fact, are doing this. For example my girlfriend and myself are using the same mobile device with the same third party app and the same internet connection. My girlfriend has no 2FA and no authenticator running with her account and connection works better than for me having it enabled.

It is not only a server issue but also an account issue and due to the fact that Microsoft own clients with minimum required updates have the same issue you cannot say that it's the fault of the customers using old methods and clients.

So please stop talking about who is the better provider but focus on the still existing issue with authentification.

There is no difference for me switching app passwords on or off, my client is not working with both of them.

Not OK to me at all. But also not surprising.

Properly configured outlook clients have not had this issue at all. 2FA with modern auth (Oauth2) has not been impacted, at least not widespread, for exchange connected accounts (including personal outlook.com accounts using Outlook client).

They have been warning that legacy passwords and even app passwords are being phased out. However that was not supposed to have happened yet (not app passwords anyway) so somebody botched something, probably tested their changes against modern auth and ignored the other methods.

Anyone having issues with Outlook client needs to enable 2FA on their account and update their client to use Modern Authentication with native exchange (MAPI/HTTPS) connectivity.

Your comment is very limited in scope and ignore obvious facts. There is no such thing as "free" product. In this case, we paid Microsoft through the Windows OS license that is part of the device cost - it's not free. The Outlook clients, that we are having issues with, is also a paid product - it's not free. Hotmail/MSN Mail/Outlook mail is a free product but they use it to mine data in our emails and place ads. It's also not free, just paid differently.

If Microsoft does not want to make sure these run smoothly, i.e., I get 5-10 or so email on my personal account, versus 100-300+ a day on my work account, then Microsoft can exit the consumer market. Email is now becoming a critical part of our daily lives, it need to have certain level of care and reliability. I am not expecting 99.99999999999% up time for consumer products, but an issue of this severity and impact, effecting multiple email clients including Microsoft's own, lasting almost 2 weeks, is somehow OK to you is just mind-blowing...

This thread is not about Google or Microsoft but the issue with authentication servers. And it is not working.