Forum Discussion
Turning on Modern Authentication with mixed Outlook versions
If you enable Modern auth server-side, old clients will still be able to connect via legacy auth, unless you specifically block it (whether you can actually block it is a different topic altogether). So in general, you should not see a change in behavior with them.
But any user with 2013/2013 *should* switch to using Modern auth. You can enable it client-side for few test/pilot users and make sure you don't run into any stopping issues with them. I would even advise you to clear the stored credentials in order to force the switch if it doesn't automatically happen. App passwords are an ugly hack and you should stop using them where possible.
An ideal scenario would be that we enable it for the whole organization and nothing would change for all accounts that are already configured.
We would then let most of it phase out:
-> New users would get Modern Auth
-> Existing users receiving new device would get Modern Auth
-> We would switch others in batches
This would allow us to do it at our own pace without causing a big bang by enabling it for the whole organization.
However, I couldn't find any official article that explained this in detail.Nowhere is mentioned what would happen to existing clients and older Outlook versions.
And yes, we don't like app password either. Modern Auth would allow us to get rid of it.
- I have a similar situation although slightly different scenario.
We have Outlook 2016 clients in Exchange Online with Modern Auth OFF at the tenant level. If Modern Auth is enabled, what would the Outlook behavior be? Would Outlook clients switch silently or would there be auth prompts?
Thanks.- Well, I'm curious myself. So if you figure it out please share your experience :)
