Outlook 2016 doesn't accept password or app password

Anonymous
2024-01-25T09:40:42+00:00

I have this problem - Outlook 2016 doesn't accept password or app password - and i think it is a growing World wide Microsoft problem :-(

See also here: https://www.reddit.com/r/Outlook/comments/19dx64p/outlook_2013_windows_10_suddenly_not_accepting/Outlook gives me this: (startede yesterday)

I have 2 PC's with HOTMAIL accounts in Outlook 2016 ...

They both have this error.

I do get mails ... but I can´t send mails. Yesterday it did work for 1-2 hours ... but right now the error is there all the time :-(

Please help me.

Thanks in advance

Pierre

Outlook | Windows | Classic Outlook for Windows | For business

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

862 answers

Sort by: Most helpful
  1. Anonymous
    2024-02-24T18:44:49+00:00

    Same here. At least they could of provided some kind of patch too. Outlook for desktop functionally is not same as outlook (part of the MS Office) plus some dubious benefits of new design. That said it won't be first time Microsoft forced something on users and resisted changing it back to better way it was. What it looks like they decided to kick everybody out of older Office into subscription Office. In the end i will migrate to Mozilla. don't like desktop app.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2024-02-24T18:34:45+00:00

    I now cannot not log into Office 2016 Desktop at all even though I paid for it. I don't recall getting any notice they were migrating away from this but found a comment here on this forum you need to install their web app. I wish MS would have sent out an email rather than trying to figure out how to fix it.

    Most people use multiple email accounts and having to log into all of them with your user name and password was utterly frustrating. So I capitulated and now using the web based app.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2024-02-24T17:43:13+00:00

    Same problem for me, unfortunately.

    I totally agree with rest of the customers: I also paid for the Outlook Desktop application and it is extremely disappointing from Microsoft to have activated this mandatory OAuth implementation in Outlook without informing us previously. If we would have been informed with enough time, at least we would have been able to take some corrective actions time in advance.

    This unannounced change feels like a slap in the face and for sure this isn't just a minor annoyance, it's indeed a major disruption to our daily life and a complete disregard for us, the Microsoft's paying customers.

    And as other customers are telling, Microsoft should at least offer some compensation for the inconvenience and disruption that such change is causing us in the last weeks.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2024-02-24T17:24:11+00:00

    Hi all,

    The Outlook Team has updated the guidance about this issue, Outlook and other apps are unable to connect to Outlook.com when using Basic authentication - Microsoft Support.

    A key take away is that everyone needs to work towards being on apps that support OAuth for Outlook.com. If you are using Outlook 2013 and Outlook 2016 an immediately available free option is to install the New Outlook, Outlook for Windows - Microsoft Apps. We will continue to update the guidance with learnings and status updates as we go.

    Well, I guess we are screwed, its seems that also Google is moving to OAuth starting September this year, is not really clear if they will continue to support "app passwords" or you will also have to switch to a client that supports OAuth as well.

    So having to bite the bullet, how's the free "New Outlook" is that bad?

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2024-02-24T16:36:39+00:00

    Hi David,

    As a vendor (Morgen Calendar) this change is very concerning.

    1. As far as I know, this was not clearly communicated in advanced.
    2. Our calendar client is based on the EWS API for which OAuth does not work. We would love to get rid of Basic auth as well, but Microsoft is not providing a mechanism to use OAuth with EWS. What is more frustrating is that Microsoft and Apple are able to use EWS+OAuth but this seems to be enabled only on those specific client ids, which leaves other vendors not able to make the switch to OAuth.

    You might ask, why are you not using the Graph API?

    Not all the functionalities on the EWS API are supported by Graph at this time. Performing a full calendar sync with the Graph API is very painful and requires to use the Beta endpoint, which according to your documentation is subject to change. Additionally the Graph api does not allow us to access Exchange on Premise.

    All this to provide a piece of feedback from the vendor point of view: we would switch all accounts to OAuth tomorrow if this was working with EWS.

    Was this answer helpful?

    0 comments No comments