Feb 20 2019 10:08 AM
Feb 20 2019 10:08 AM
We have a couple of Ex2016 servers that have been configured to be in full hybrid mode with our new O365 tenant. Our on-prem AD has been synced with Azure AD Connect and password hash sync has been configured. Seamless Sign-On has also been configured. When an Outlook 2016 client is launched from a domain-joined desktop against a mailbox that has been moved to O365, we see the Outlook 2016 splash screen and we see a white O365 authentication box pop up but SSO takes care of that for us and we end up inside the mailbox. So, things are currently working as intended.
When we add MFA to one of our O365 accounts, that is also working. When launching Outlook 2016 from a domain-joined PC against an O365 mailbox that has MFA enabled, we get an MFA challenge and when we pass that, Outlook continues into the mailbox with no trouble.
So, what we are looking to do is to have MFA enabled on a mailbox but if the mailbox is accessed by an Outlook 2016 client from domain-joined PC, we would like for that type of login to bypass MFA. If a login happens outside the domain, we would like the MFA policy to apply.
We understand that something called Conditional Access is available when using Azure AD Premium licensing (either P1 or P2) and with Conditional Access, it looks like we could then set up Trusted IP Addresses so that we could then identify where our domain-joined clients originate from. However, we are debating on whether spending the extra money per user for Azure AD Premium is the best way to go and so we are looking for alternatives to that approach.
Does anyone know of a way to have MFA get bypassed by an Outlook 2016 client that is set up to use Modern Authentication and that is coming from a domain-joined PC?
Feb 20 2019 10:43 AMSolution
It's either Conditional Access, or redirecting the authentication process by deploying an on-premises AD FS server with the MFA configured there. Which in your scenario will probably cost more.
The other functionality that comes to mind is the Azure AD Join, which will automatically satisfy MFA requirements. But that's not the same as domain-joined, as generally speaking people can join personal devices and thus bypass MFA on them as well.
Feb 20 2019 11:18 AM
Thank you very much for your quick response! After searching around for a good while, I had a feeling that Conditional Access was pretty much our only option (I had not considered the full ADFS option until you mentioned it but I think I'd rather stay away from the complexity that solution brings) so we will probably take a hard look at adding those Azure AD Premium licenses to gain the Conditional Access feature.