Outlook 2016 doesn't accept password or app password

LOL why would I start a new account? I couldn't care less if you find my posts helpful or not. The problem has been totally solved for me as far as I can tell.

I am wondering the same thing. Where did this guy come from accusing those of us who have been contributing to the thread from the beginning as "hijackers", calling for moderation of us who are providing feedback on relevant information being discussed and suggestions brought up by Microsoft themselves no less?

It is true the thread topic only specifically mentions Outlook 2016, but it quickly became known that the authentication prompt error problem is much more widespread affecting many other clients and devices from Thunderbird to 9Folders, from Windows desktops to iPhones. At this point it is hardly "hijacking" the thread discussing these other clients being identified simply because the thread topic in the early days of the issue, when less information was made known, only mentions Outlook 2016.

This thread became the main thread for discussion of this issue for all these clients and devices as referenced by Microsoft themselves.

https://support.microsoft.com/en-us/office/outlook-and-other-apps-are-unable-to-connect-to-outlook-com-f4202ebf-89c6-4a8a-bec3-3d60cf7deaef

It is my humble observation that the newcomer lacks standing and understanding from the last 40+ pages of discussion and the context in which things such as "New Outlook" are brought up and discussed and why.

While IMAP/SMTP is working much better for us at least with normal/basic password authentication using 2FA and app passwords under Thunderbird, Windows Live Mail, and Samsung Email clients, many still report issues. As Microsoft makes changes to one aspect of this, it may inadvertently affect another, such as I reported yesterday regarding extreme throttling taking place.

These issues are not necessarily isolated incidents and it is relevant to discuss them since it is difficult to determine just how interconnected experienced behaviours are as a result of changes being made to try and resolve this as we work towards a solution that works for everyone using email clients, MS or 3rd party, that conform to some sort of standard.

I ran more experiments.

When I have EnableADAL added to both 2013/2016 versions' regkey settings, I can connect to my work email account with OAuth MFA enabled. The connection readout is "Bearer*" and at least I can get through the account settings. The behavior is similar to the current M365 Outlook latest stable channel build.

When I use this same Outlook and added my personal Hotmail account, in which I selected "Outlook.com..." as account type, it finished the setup and "Microsoft Exchange" shows as account type. The connection readout is "Clear*" as others have posted.

I read through all searchable MSDN articles and such, and all suggest EnableADAL will enable OAuth but it listed out a negotiation sequence which suggest it only go to "Clear" when the server declined OAuth. If these articles are to be believed, it again points this to a server-side issue.

Again, you ignored others' feedback - someone else called you out on the same issue and that this is relevant. The suggestion of using or moving to "new Outlook" as a workaround is not viable and it should be discussed here so people are aware of the risks. I concur with those that brought up the same issue.

The problem of this thread is still NOT solved! I added my personal Hotmail account to my work computer Outlook client today just to see if it made any difference and the answer is NO! I am getting constant pops for password. That Outlook is absolutely the latest with all the updates on the stable channel. Simply put, whatever authentication-related code changes MS made to the "Live' email accounts and servers (Outlook.com/Hotmail/MSN/Live brands) is broken. I do not count "new Outlook" as a true EAS client because it isn't - it's basically Outlook for Web wrapped up in a PWA - one might as well use Outlook for Web directly.

I also want to point out you started your User Profile just a couple of days ago, at the onset another user was called out for being not helpful. I wonder why a new user of 2 days believe he/she earned enough standing to accuse others of posting non-relevant info and call for moderation for on-topic discussions.

"You keep saying "new Outlook" or email client is not relevant to this issue"

Yes I do, this thread is about, as the title said "Outlook 2016 doesn't accept password or app password" and not about the new free Outlook client which you are trying to get your unrelated concern answered here, how's that you don't get it, are you purposely doing this? You are just hijacking this thread with a new issue, this is call sliding or hijacking a thread with the intention of sliding the topic from the current issue to a new one.

How your concern for the new Outlook client, as you put it using "ads masqueraded as email", and for other "privacy issue" has to do with this topic,?

Your concern is about the "new Outlook client" (which you apparently are even using) or whatever you want to call it, it's not related to the issue that users in this thread are experiencing and discussing, which once again is related to authentication and not about the new Outlook client, ads, privacy, scraping or its feature limitations.

Just because a mod here mentioned it "as a temporary workaround" to use the "free" new native Outlook doesn't mean that we are or want to discuss this topic, which apparently you are the only one that is concerned with.

So if that is the case, what is stopping you to open a new thread regarding whatever your concerns are about the new Outlook client?

Is anyone moderating this topic?