Even though they say our tenant is no affected by it, but it obviously is. We finally got Microsoft to admit there is a problem and are now waiting on a resolution. We've been having this problem since Friday 7/28 around 2pm with about 60 of our users. Windows 10 should be shipped early next year, I%u2019m now trying to check ETA. Recommended if the situation is blocking). Will see legacy UI and may be prompted more in other cases, so it's only Regkey disables WAM use in Office, which can degrade the auth experience (users Workflows on Windows builds later than 15000 (Windows Version 1703, build Starting in build, Office uses Web Account Manager (WAM) for sign-in 'DisableADALatopWAMOverride'=dword:00000001ĭefault, Microsoft Office 365 ProPlus (2016 version) uses Azure Activeĭirectory Authentication Library (ADAL) framework-based authentication. I've logged a MS case, with not much feedback so far.

I'm assuming this was an update of software/OS.įollowing other cases has not lead me far, I can't choose auth method (basic/ntlm) in 2016+365Īny leads to the cause are welcome. There was no relevant change on our part afaik. This looked like it solved it for a few hours, but today impacted users report the same behaviour.Īll are on the same hardware, so it's very odd that not everyone is impacted. Yesterday I've had everyone delete their stored Windows 10 credentials. So far 15 out of our 42 active Windows Outlook users have been impacted (not counting Mac Outlook, or holiday users).Įveryone is using Outlook 2016 on Windows 10, Office 365 (hybrid setup with all user boxes in the cloud). Entering credentials just makes the prompt show again, only canceling it and clicking the 'needs password' text in the bottom of Outlook's main window allows them to keep working for a while.

Since last week, a lot of our users are bothered by Outlook 2016's credentials prompt.

Outlook 2016 email log in