That are the registry keys that are mentioned in the blog post under the Outlook section. Once you reconcile the settings service side - there could still be settings client-side that are forcing your Outlook clients to use basic auth. There are additional configuration steps required to install Kerio Outlook Connector (KOFF) on the Microsoft Outlook 2013 - Part of Microsoft Office 365 (. The bottom line is - you should check your Message Center posts and Service Health Notifications to see if Microsoft made changes to authentication in your tenant before the problem started. I do not know that this is a problem, but be aware if you see something about it, this will block all basic auth outright. Modern auth could also be turned on in Azure by a setting called Security Defaults. That basically tells Outlook clients 'you can use modern auth'. As this is Outlook for Windows we are talking about - there is also a tenant setting as mentioned under Outlook section in that blog post. So first thing that needs to be understood is - which protocol is Outlook using to connect to Exchange Online? Is basic auth turned off for it? (running the diagnostics from that blog post will show you) Are those Outlook clients using POP/IMAP as a protocols or not? (this will depend on how profiles are created) There is a per-protocols modern auth setting, which is what we are turning on for tenants starting October 1st when that happens, basically there is no more basic auth for a particular protocol. Yeah so you need to clarify what it means that 'modern authentication has been turned on'.

Outlook 2013 microsoft 365