Ongoing Outlook login issues

%3CLINGO-SUB%20id%3D%22lingo-sub-279834%22%20slang%3D%22en-US%22%3EOngoing%20Outlook%20login%20issues%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-279834%22%20slang%3D%22en-US%22%3E%3CP%3EIn%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FOutlook%2FOffice-365-Outlook-2016-random-weird-login-issues%2Fm-p%2F155466%22%20target%3D%22_self%22%3EFeburary%3C%2FA%3E%20I%20posted%20about%20this%20and%20now%20it%20has%20an%20incident%20in%20the%20Admin%20Center%3A%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22Outlook%20Login%20issue%20warning.png%22%20style%3D%22width%3A%20845px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F58543iD498A77DD7F9C191%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20title%3D%22Outlook%20Login%20issue%20warning.png%22%20alt%3D%22Outlook%20Login%20issue%20warning.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3EThere%20is%20a%20%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F4025962%2Fcan-t-sign-in-after-update-to-office-2016-build-16-0-7967-on-windows-1%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Esupport%20article%20with%20a%20potential%20workaround%3C%2FA%3E%20posted.%20It%20seems%20there%20is%20updated%20guidance%20on%20registry%20edits%20posted%20on%20%3CA%20href%3D%22https%3A%2F%2Fcommunity.spiceworks.com%2Ftopic%2F2025536-outlook-2016-365-keeps-asking-for-credentials%3Fpage%3D6%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3ESpiceworks%20thread%3C%2FA%3E.%20It%20is%20unclear%20however%20what%20builds%20are%20needed%20to%20use%20these%20registry%20fixes.%20Curious%20if%20anyone%20has%20further%20details%20on%20this%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-279834%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOutlook%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-280297%22%20slang%3D%22en-US%22%3ERe%3A%20Ongoing%20Outlook%20login%20issues%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-280297%22%20slang%3D%22en-US%22%3EYeah%20I've%20experienced%20it%20even%20on%20my%20own%20account%20in%20the%20past%2C%20deleting%20mail%20profile%20and%20setting%20back%20up%20fixed%20it%2C%20but%20curious%20and%20thinking%20this%20is%20random%20and%20spread%20through%20my%20users%20at%20my%20previous%20company%20as%20well%20now%20that%20I%20think%20about%20it.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-280295%22%20slang%3D%22en-US%22%3ERe%3A%20Ongoing%20Outlook%20login%20issues%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-280295%22%20slang%3D%22en-US%22%3E%3CP%3EYes%20we%20have%20ADAL%20running.%20All%20machines%20are%20Local%20AD%20joined%20and%20then%20Hybrid%20AAD%20joined%20so%20they%20do%20auto%20login%20to%20office%20365%20services.%20The%20problem%20never%20affects%20anything%20other%20than%20Outlook%20Win32%20program.%20They%20are%20in%20fine%20to%20OneDrive%20or%20web%20version%20of%20Outlook.%20It%20never%20seems%20to%20affect%20more%20than%20one%20user%20at%20a%20time%20and%20rarely%20repeat%20people.%20It%20is%20about%201%20a%20week%20for%20a%20few%20hours.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-280283%22%20slang%3D%22en-US%22%3ERe%3A%20Ongoing%20Outlook%20login%20issues%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-280283%22%20slang%3D%22en-US%22%3EThat%20sounds%20horrible.%20Assuming%20you%20guys%20turned%20on%20Modern%20Auth%20in%20your%20tenant%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-280282%22%20slang%3D%22en-US%22%3ERe%3A%20Ongoing%20Outlook%20login%20issues%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-280282%22%20slang%3D%22en-US%22%3E%3CP%3EIn%20our%20cases%20it%20is%20never%20connected%20to%20a%20password%20change.%20Rebooting%20doesn't%20fix%20it.%20The%20fix%20is%20time%20usually.%20After%20some%20period%20of%20hours%20it%20magically%20starts%20working%20again.%20It%20is%20frustrating%20from%20a%20support%20standpoint%20since%20I%20can't%20solve%20it%20for%20users.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-280042%22%20slang%3D%22en-US%22%3ERe%3A%20Ongoing%20Outlook%20login%20issues%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-280042%22%20slang%3D%22en-US%22%3EThis%20always%20happens%20around%20usually%20when%20users%20change%20their%20passwords.%20Usually%20a%20reboot%20fixes%20it%2C%20but%20that%20shouldn't%20be%20required%20for%20something%20like%20a%20password%20change.%20Hopefully%20it%20gets%20fixed%20%3Ap.%3C%2FLINGO-BODY%3E
Highlighted
Contributor

In Feburary I posted about this and now it has an incident in the Admin Center:

Outlook Login issue warning.png

There is a support article with a potential workaround posted. It seems there is updated guidance on registry edits posted on Spiceworks thread. It is unclear however what builds are needed to use these registry fixes. Curious if anyone has further details on this?

5 Replies
Highlighted
This always happens around usually when users change their passwords. Usually a reboot fixes it, but that shouldn't be required for something like a password change. Hopefully it gets fixed :p.
Highlighted

In our cases it is never connected to a password change. Rebooting doesn't fix it. The fix is time usually. After some period of hours it magically starts working again. It is frustrating from a support standpoint since I can't solve it for users.

Highlighted
That sounds horrible. Assuming you guys turned on Modern Auth in your tenant?
Highlighted

Yes we have ADAL running. All machines are Local AD joined and then Hybrid AAD joined so they do auto login to office 365 services. The problem never affects anything other than Outlook Win32 program. They are in fine to OneDrive or web version of Outlook. It never seems to affect more than one user at a time and rarely repeat people. It is about 1 a week for a few hours.

Highlighted
Yeah I've experienced it even on my own account in the past, deleting mail profile and setting back up fixed it, but curious and thinking this is random and spread through my users at my previous company as well now that I think about it.