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-06T12:48:56+00:00

    Mine is not fixed.

    If there a Microsoft account contact page that we can get instructions on how to resolve.

    This is more that silly. Over two weeks

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2024-02-06T09:02:20+00:00

    From not the community crew:
    If the client is modern authentication ready, if the really old EWS function works? (Personal account EWS method?)
    h t tp s :/ / as k u b u n t u . c o m / q uestions/109548/evolution-and-office-365
    Host URL: https://outlook.live.com/EWS/Exchange.asmx
    OAB URL: https://outlook.live.com/OABThough

    The *.office365.com,  *.outlook.com, pop3.live.com, *.hotmail.com, outlook.live.com seem to have numerous ipv4 and ipv6 IPs in the d n s c h e c k e r . o r g

    The imap.live.com, imap-mail.live.com, pop.live.com, smtp.live.com, smtp-mail.com, eas.live.com are mostly the same 204.79.197.212 or 2620:1ec:c11::212 from most dns in the d n s c h e c k e r . o r g

    It recalls me that if the IPv6 affects since the webpage of outlook.live.com have several third party MS owned website and some are ipv4 only, some has ipv6.My ISP is dualstack but sometimes it will be only ipv6 or sometimes IPv4 only at first or lost one of them after sometime.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2024-02-06T08:42:23+00:00

    Perhaps I should mention that my private account @outlook.de (outlook.com account) is added as guest account to an organization. Normally this is done by creating an alias within the organization which is something like "*** Email address is removed for privacy ***" and policies are set for this alias. I only have to log in to my outlook.com account, verify with my authenticator for this private account and then verify again with my authenticator for the organization account.

    I do not get E-Mails via this alias at all, so its only to sign in to their teams. Also the auth problem is only with my mobile devices third party app trying to connect via EAS to my private account, not to the alias, also with app passwords enabled. But perhaps it has something to do with that.

    By the way: Since app passwords are only shown once when they are set up, it is really annoying when having a new password prompt since you have to generate a new app password just to get another authentification failure...

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2024-02-06T03:22:30+00:00

    It's not resolved though they marked it as such. They are lying

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2024-02-06T02:46:46+00:00

    Issue is still not fixed. Just had a burst of password prompt in the last several hours. I again deleted and re-added the account and went through a 2FA verification on my Android phone. Within 30 min, it's again prompting me for password. I don't know in what world this issue is considered as resolved when people are still having issues with Google Pixel and Apple iPhone running the LATEST Microsoft's own clients. I don't care if MS marked the issue "Resolved". This is done by the same set of people that caused the issue in the first place. It's very much a move to improve their KPI and is detached from reality.

    Was this answer helpful?

    0 comments No comments