Consider the following scenario:
- You have an Azure Active Directory (Azure AD) tenant in which users are federated through Active Directory Federated Services (AD FS).
- In this tenant, Azure MFA Server or a third-party MFA provider is deployed in AD FS.
In this scenario, users may be forced to sign in by providing their user name and password two times before they are prompted for multi-factor authentication (MFA) and can complete the logon.
If the MsolDomainFederationSettings -SupportsMFA value is set to $true and the -PromptLoginBehavior value is set to TranslateToFreshPasswordAuth, Azure AD sends the MFA request to the IDP for step-up authentication. Azure AD also asks for a fresh user login. This is accomplished by sending the following parameters to AD FS:
When this situation occurs, user are prompted a second time for their user name and password regardless of whether they just logged in. Users are prompted for MFA only after they enter their credentials a second time.
To resolve this issue, you must configure Azure AD to let AD FS natively handle this request by changing the -PromptLoginBehavior setting to NativeSupport. To do this, follow these steps:
Important Your AD FS deployment must be running on Windows Server 2016 or Windows Server 2012 R2, and must have the July 2016 update 3172614 installed.
Download the latest Azure AD PowerShell V1 release.
- Run the following Connect command to sign in to your Azure AD administrator account:
Note Run this command every time that you start a new session.
Configure Azure AD to run federated user authentication by using the prompt=login behavior. This prevents the user from having to begin a completely new authentication. For example, run a command such as the following that includes your tenant-specific information:
Set-MsolDomainFederationSettings –DomainName your_domain_name -PreferredAuthenticationProtocol <current auth setting such as WsFed> -SupportsMfa $True -PromptLoginBehavior NativeSupport