microsoft outlook 2016 16.16.8 okta login screen loop

In the instances that this occurs the effected user is not new to MFA but has been running it for at least months.

We currently have a mixture of Win8.1 and Win10 desktops so adding the O365 account to Windows is not an option (on Win8.1).

We can't rebuild the Outlook profile when this occurs as our users have fairly large mailboxes so don't want to do this each time.

Even if temporary disabled it has to go through a higher approval process.

We can't turn off MFA for users as it is a policy requirement.

Thanks, trying not to sound like I'm being Debbie Downer, but. Has anyone else come across this, or found a permanent solution (short of turning MFA off) ? There doesn't appear to be any pattern to the issue occurring or the problem being limited to any specific computer or user. In each case the fix has either been one of the above items or a combination of them.

Open installed browsers and ensure that each one is signed out from Office365.

Open Windows Credential Manager and delete all the Office ADAL related credentials.

I have had different experiences with a fix ranging from. and so we repeat the same process again, and again. Then a couple of seconds later the modern authentication screen appears again asking for your password. You approve the sign in on your phone then the authentication window on the computer closes. Please respond to continue' (I am using the Authentication App but the same problem occurs if you are using SMS). You enter the correct password then click 'Sign in', You are then displayed with 'We've sent a notification to your mobile device. Learn about the terminology that Microsoft uses to describe software updates.Has anyone else experienced Outlook 2016 stuck in an authentication loop when you have multi-factor authentication (MFA) enabled on Office365? The sequence is that Outlook displays the modern authentication screen for you to enter your password.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the 'Applies to' section. To resolve this issue, install Cumulative Update 11 for Exchange Server 2016 or a later cumulative update for Exchange Server 2016. This example specifies the time span for signing out to 5 hours. Set-OrganizationConfig -ActivityBasedAuthenticationTimeoutInterval 05:00:00 You can set the value of ActivityBasedAuthenticationTimeoutInterval to more than 4 hours.

This issue occurs because the method that the Outlook on the web uses to request a new token from AD FS isn't correct. In this situation, users can't sign in to the Outlook on the web.

When the time out value is reached, the Outlook on the web (formerly Outlook Web App) may sign out, and then enters an authentication loop. Then you set the value of ActivityBasedAuthenticationTimeoutInterval to less than 4 hours for device registration for users. Assume that you deploy AD FS for single sign-on (SSO) by using Windows Server 2016 in Exchange Server 2016 environment.

Microsoft outlook 2016 16.16.8 okta login screen loop