Outlook 2016 doesn't accept password or app password

I have the same problem for 1 week....been running Office 2016 for 8 years on Windows 10 and 3 yrs on Windows 11 and never a problem with authentication unless I changed the password. This is a fix Microsoft has to make. Its so annoying you could be browsing or working on a word document and the password window pops up.

HELLO MICROSOFT THIS IS REALLY IRRITATING. HAD THIS EMAIL ACCOUNT SINCE WINDOWS 95 BEEN USING WITH OUTLOOK SINCE THE EARLY DAYS NEVER HAD A PROBLEM UNTIL JANUARY 2024 WITH OUTLOOK 2013 TRYING TO LOGIN EVERY TIME I OPEN THE CLIENT. YOU DID THIS, ALL BY YOURSELVES.

WHAT HAVE YOU DONE TO FIX THIS IDIOTIC UPGRADE MESS FROM OVER A MONTH AGO, EARLY JANUARY? WHY WON'T THE STUPID CLIENT RETAIN MY PASSWORD AND LOGON AUTOMATICALLY? WHY MUST I INPUT THE PASSWORD MULTIPLE TIMES BEFORE THE CLIENT FINALLY SYNCS UP???????????????????? WHAT IS WRONG WITH THIS GENERATION OF MS EMPLOYEES????????????????????????????????

51 PAGES OF COMPLAINTS 2/17/24 AND STILL NO PATCH?!?!?!?!?!?!?!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

So obviously either another attempt at a fix, or an extended period of the server dropping. All account settings reset and required resetting this morning. 2 outlook.com accounts. 9Folders. Exchange Activesync. Hrumph. .

Gabriel, I am the CTO of Morgen Calendar, a calendar client that connects, among other things, to personal Outlook accounts and O365. Our users are also affected by this intermittent issue, even with an app-specific password.

Some technical info for your team.

• We are using EWS to fetch calendar info
• We have to use Basic authentication (email + password) because OAuth does not work for EWS on personal accounts. It works for O365 work accounts but not for personal Outlook accounts. Weird thing is, Apple Calendar is able to use OAuth with personal Outlook accounts, but nobody else using the EWS API can (meaning Busycal, Fantastical, etc.).

If we could switch to OAuth for these accounts, the problem would be solved for those clients that are willing to support modern authentication.

You're misunderstanding (maybe instead of just quoting a couple lines, read the entire post, it contains further context). I'm not being tolerant or accepting, I'm explaining to you how corporate minds work.

A small percentage of inconvenienced users that are not huge corporate clients is not even a blip on their radar. I hate to break it to you, but for the most part MS could care less if anyone in this thread was a client of theirs or not. There has not been any publicity or news coverage around this, which is the only thing that would actually make them care.

Do you really think all the people making threats and stomping their feet in this thread is going to make any difference at all? I think the duration of the outage, lack of urgency, and the fact that they clearly are NOT going to roll back whatever change they made answers that question.

The best you can expect here is other users providing what they've found as workarounds/temporary fixes, and hopefully some sort of updates from MS every so often. The MS employee here has been actively collecting info and feeding it back, honestly that's far more than you'll usually see on this forum.

Rather than wasting so much time here, you should probably be focused on why your supposedly Oauth2 enabled accounts/clients are having problems, when those have not been impacted for others.