Several of our coworkers at my organization experience an issue after a password reset where sometimes Outlook will not accept their recent credentials. When looking in the Okta logs for the account you will see  Authentication of a user via Rich Client Failure entries at the time they were trying to sign into Outlook.

1) Cleared cached windows credentials

2) Created new outlook profile (will actually get stuck during the Profiles setup wizard when asking for password)

3) Reset password in AD will temporarily resolve it, but user calls back a day later for the same problem

4) Logging into OWA works fine which makes me think it's not an issue with the new password getting to our domain controllers. Coworker has no issue logging into other system as well that use their Active Directory account information.

5) This has happened in both Office 2013 and now Office 365 which we use the Office 2016 build (most recent)

6) I also know sometimes the mapi component gets corrupt and we have to run fixmapi.exe found in the c:\windows\system32 (or syswow64) folder, but that hasn't fixed it in these cases.

I do have a .csv file of some of these logs, but did not see an option to include that with the post.

Hope I included good information to get some ideas what could be causing this in our environment.