![]() Non-browser connections (such as those from Outlook installed on user desktops) will now require Modern Authentication. They are few, but they do need to be planned for Modern Authentication Now, let’s talk about the caveats of this solution. The solution works beautifully – if we connect from outside of our network to OWA (via a web browser), the user will see Duo integrated with the ADFS login page as a next step after a successful login: Just to be sure, I also whitelisted my public IP address within Duo’s application policy. In my case, I chose to simply require 2FA only for extranet connections: This makes user onboarding simple and easy.ĭuo’s combination of access policies can be combined with ADFS’ claim rules for a very customizable experience. The great thing about this is that, when your users authenticate through a web browser (such as to OWA), if they’re not already enrolled they can be prompted to enroll at that time. In my ADFS 4.0 environment Duo’s plugin installed seamlessly and was instantly available for MFA within ADFS. In fact, I found it to be just about that easy. ![]() Duo conveniently provides a plugin for ADFS so that MFA can be bolted on to the existing SSO solution. Many organizations choose to federate their on-premise identity – Active Directory – with Microsoft so that users have a Single Sign On (SSO) experience when accessing 365 – this is, in many cases, achieved using ADFS. Duo Security is an industry leader in MultiFactor Authentication (MFA) and zero-trust security solutions.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |