Aug 07 2019 08:22 AM
Aug 07 2019 08:22 AM
Good morning everyone,
Over the past several months we've been experencing a very random issue where Outlook loses users credentials, and then when loading Outlook it prompts for the password, but goes away so quickly you don't have a chance to enter the password.
Steps we have taken to resolve the issues.
1. We've cleared credential manager on the system
2. Repaired office (both quick and online).
3. Created new Outlook profiles (including deleting the .ost file).
4. Uninstalled/reinstalled Office completely.
Most times it works itself out after a few days, but I don't get why this issue continues to happen.
Any helpful tips?
thanks in advance
Aug 12 2019 12:37 PM - edited Aug 12 2019 12:38 PM
There is a known outage from Microsoft which is still in effect..
User Impact: Users may be unable to connect to the Exchange Online service when using the Outlook client.
It started 7/31 - present. The workaround is to use Office online. We have few users report this issue as well.
Are you in a Hybrid setup or Office 365 Exchange online setup?
Aug 16 2019 11:56 AMSolution
@Ash365 I was able to resolve this issue by adding the following registry keys
Credit to this article also
Aug 20 2019 07:48 AM
Dec 16 2019 09:05 AM - edited Dec 16 2019 09:20 AM
We have the same problem on our new WVD system.
Outlook after day or 2 disconnects and says 'need password'.
We managed to go around by putting:"HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\Identity, create a DWORD value named EnableADAL and set it to zero." into users profiles.
We don't want to leave it like this as customer might want to switch to 2FA in the future and this will cause problems.
Feb 09 2020 06:16 AM
Mar 10 2020 07:19 AM
Found the solution here:
So make sure you:
Mar 21 2020 04:10 PM
@prelek Thank you SOOOOOO MUCH! I've been struggling with this for months! Even Azure/Office 365 support told me to use the registry keys to disable modern authentication. That's NOT a solution! I was on the right path to get it working but was missing the critical piece where the hosts need to be Hybrid Azure AD joined. The moment the hosts showed up as Registered in Azure the "Need password" flickering authentication window issue changed to "Connected to: Microsoft Exchange"!
Apr 10 2020 10:31 AM
I had a client that kept having this same issue, even after I did every thing you did. What I found was going on is that she was logged into Outlook under one account and logged into OneDrive and other Office apps under another. Once I logged her out of the other account in OneDrive and the other apps and logged her back into those apps using the same account she used for Outlook the issue had resolved.
May 06 2020 09:55 AM
Aug 26 2020 07:41 AM
We have been using this fix as of late. However, new reports show the issue returning. Registry item still in tact. On the new reports, issue goes away randomly on reboots, then returns. So the general population is gonna need more than just this registry fix. :( @dhendrix24
Sep 11 2020 07:13 AM
Hey guys, not sure if anyone else is continuing to have issues with this. As luck will have it, we ran into this same issue and noticed the password prompt would "flash" and immediately disappear as well for Outlook.
Read through this thread and disabling MFA is definitely NOT an option I would entertain.
I noticed End User was not logged into OneDrive... logged user into OneDrive and was immediately prompted afterwards for credentials which resolved the issue with Outlook.
I am waiting to see if we run into this issue again to test it again but just thought I would put this out there in case it is able to help someone.
Oct 01 2020 03:59 PM
We had this exact same problem for about 3 users. (out of thousands) and we do not have onedrive enabled for our users nor do we use Hybrid Domain join.
Any other ideas? other than disabling MFA support? in fact is that all that EnableADAL 0 does ? Is disable MFA support for Office Apps?
Oct 02 2020 06:33 AM
@Robert Bollinger Disabling MFA was not in our list of options. Try the following also:
I understand this is a work-around but I still do not know what is causing the original issue and as I said before, disabling MFA is not one of the options to consider.