If you’re using Outlook 2010, the only way to get passed this is to use an app password.
It turns out that even if you have MFA excluded for your internal networks, as long as MFA is enabled on a user account, Office 365 will require a modern auth request before it even gets to the place of determining whether or not MFA is required. However, we were finding that users with MFA enabled were still unable to configure their Outlook profiles, and instead would just get constantly prompted for username and password, and the profile would never fully configure. This environment had ADFS configured for Single Sign On, and so MFA is configured to skip multi-factor authentication for requests from federated users on my intranet, like so: Well, here’s where things get a bit trippy… Now, I know what you’re thinking… duh! We already knew that Office 2010 doesn’t support modern auth, and so if you have MFA enabled on your account, you won’t be able to use Outlook 2010. Office 2013 only really likes Modern Auth conditionally.Office 2010 does not like Modern Auth at all and,.It basically boils down to needing to understand two things: I’ve been working on a project recently where we’ve been running into some weird issues with Modern Authentication in general, and MFA specifically.
0 kommentar(er)
