Outlook 2016 doesn't accept password or app password

That being said, it has not been "down". Webmail (accessible via phone browser) has been fine, albeit inconvenient, and bouncing network or cancelling password prompts has worked for most.

Running webmail your mobile browser is not reliable for when you are waiting for incoming emails or events. Power management at the browser level or OS level will choke the browser and connection, so you will not get incoming emails/data unless you are back on the browser tab and refreshing. This is not a solution, unless you keep that tab alive and constantly check it, you will not get timely event notification. Mobile browser has a lot more power savings techniques enabled, and I am not going to disable all those just so we can cuddle to MS' unreasonable stance of not rolling back whatever they changed.

You seem to have an unreasonable level of tolerance to MS issues. What next? Blame mobile email client for generating notification event for the password/auth error? And they should just go quietly? Or pretend it didn't happen? These are critical issue and naturally the client will throw a critical/urgent level event and notification.

They don't need to roll changes per se, they just need to provide working patch.

Problem with whole thing is mix of old and new code and whole bunch of "cultural layers" which now is out of control. Outlook as program uses same tool of account management as it was in Win XP (may be not XP but 7 for sure) on top of modern or not so modern shell. Whole thing should connect to Windows account management and such. Corporate use different windows with different set of rules and privilege management. There is huge and fundamental difference between home windows log in and corporate server based log in. Not really my thing so explanation is bit vague here. Corporate did experienced fallout but was out of woods in 2-3 days. Personal e-mails are here and there. Web to my surprise on some logins suppressed MS advertisement (no complaints here) and on other did not. Same goes for some links in the e-mail body. My point here. Issue is more complex than it seems. I won't be surprised if it affected e-mails on certain servers (physically served by them) more than others. As much as it fun to guess there is no help in guessing. I wish MS would of cleaned the house like Apple did and provided actually new system. Changes to Office been more cosmetic in all 2013/16/19 and last 21. So i assume MS don't need to do that much to fix them all rather fix one and it will work on the rest.

I continued to use standalone Office because 365 was at mercy of developers thinking arbitrary changes in interface count as improvement in software. I had access to 365 for about 6 years and never was better experience.

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.

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.

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. .