Forum Discussion
Risks when enabling ADAL for Exchange Online and Skype
You are simply enabling another auth provider, it is not directly tied to MFA. As long as the client supports ADAL/Modern auth, it will follow the new auth process (with or without MFA), and if it does not support it, it will use the legacy method. Apart from some of the PowerShell modules and sme 3rd party apps, all apps should have proper support for Modern auth now.
VasilMichev sorry, just one more question before I test this out. According to the https://blogs.office.com/2015/11/19/updated-office-365-modern-authentication-public-preview/, connecting to Exchange Online via PowerShell is not currently supported. We have some automation tasks that work against Exchange Online and the Compliance Center and require unattended sign-in. Would you expect these to break once modern auth is enabled?
NunoAriasSilva Thanks, but at the moment I'm really just referring to a standard unattended connection via PowerShell. Will the normal sign-in still work once modern auth is enabled assuming MFA is not enabled for the admin user that will be used in the script? The FAQ linked above seems to indicate that the traditional methods of connecting to Exchange Online will not work with Modern Auth in general, not just MFA.
PowerShell will work just fine, in fact "pure" PowerShell to date does not support Modern authentication, yet we are still able to connect via the legacy method. Now, if you have the actual account enabled for MFA, connecting with "pure" PowerShell will not work. You will have to use the new, ADAL-aware module instead.
- Thanks Vasil! That's exactly what I was getting at!
Hi Matt, I could not be a problem to that because the method used in Powershell is different, I have connections using powershell without any problems.
Note: The faq is older than the previous link.
NunoAriasSilva Thanks! Sounds like I'm worrying over nothing!