Basic Auth and Exchange Online – February 2020 Update

Hi @Gregg Taylor and team. Thanks for this updated post. It’s great to see the availability of basic auth reporting and some progress on the IMAP and POP modern Auth support. I have a few questions. We’re seeing quite a lot of Outlook for Windows and Outlook for Mac users in our Basic Auth reports even though our EXO tenant is configured for modern auth and we have the registry keys in our GPOs to ensure modern auth is used. It’s good to know from the above how we can check whether Outlook client is using modern auth... but what do we do to fix these Outlook users? On the Windows side it’s mostly Office 2013 users... but how do we fix them? On the Mac side the majority of users are on the latest monthly release of Outlook 365 ProPlus and yet some of them (300+) are still using Basic Auth according to reporting. What actions can we take to fix them since they should already be using modern Auth? With regards to Remote PowerShell, we’ve been told our Microsoft contact that using the new V2 version of the EXO PowerShell Module should be sufficient to ensure that we’re using modern Auth. We’ve updated all our automation scripts to use the new V2 module and as far as I can tell, based on the sign-in logs, modern Auth is being used. So why the comments in the above post about waiting for a few more months for cert based Auth in Remote PowerShell?