Outlook 2016 doesn't accept password or app password

This is not resolved, I'm using the MSI version of Outlook 2016 with my Hotmail setup as Microsoft Exchange, with an App password and 2 factor authentication is enable. Every couple of days it authenticates and lets me read my new emails in Outlook but most of the time I get a prompt for my password which keeps returning.

Microsoft, are you doing this deliberately to make us take out a Office 365 subscriptions, if so then at least tell everyone rather than pretending to resolve the issue.

2FA is enabled - I believe it now has to be to enable app passwords to be generated?

Authentication error just now. Persistent. Cannot sign in. Needs to be fixed. Come in MS.

Still broken. Going on three or four weeks. Why am I paying for a service that doesn't function, Microsoft? And what credit will I receive for the period in which it doesn't function?

Why the status of this issue has been marked as "Resolved"? This issue has "NOT" been resolved at all.

Since around January 23th, every time I open Outlook 2013, (2FA enabled + app password with an @msn.com account) it prompt me with the Windows Security Outlook password prompt, if I check "Remember my credentials" it doesn't accept the password at all and keep prompting me in a loop, if I leave it unchecked, after 2 or 3 times it accept the password, but then it start asking for the password again randomly.

For some reasons, by clicking "Need Password" on the status bar connects the account to Exchange (even after if I haven't entered any password and canceled the password dialog....) but then again, it start prompt for the password randomly, rinse and repeat. The password apparently is not saved, not accepted or both or who knows what...

I'm using Outlook 2013 Professional Plus, since it was working perfectly fine until now (funny enough it works perfectly fine with all my other Gmail accounts but not with an MS one...), I also have a license for Outlook 2016 Professional Plus (that is still fully supported by MS) which is useless, since also this version is affected by the same issue.

This issue is extremely frustrating, and it's going on for almost a month now, it is supposed to be "resolved" but the fact that it is obviously not resolved and that MS is still unable to fix it (or cares to), makes you really think about what is going or not going on...