Okta Prompts for MFA Despite Password-Only Policy Due to Microsoft Entra ID
Last Updated:
Overview
Okta prompts a user to enroll in or perform Multi-Factor Authentication (MFA) when accessing an application, even though an Okta sign-on policy is configured for password-only access. This occurs because Microsoft Entra ID enforces an MFA requirement via a Conditional Access policy, which overrides the Okta policy. Resolve this by excluding the affected account from the Microsoft Entra ID Conditional Access policy.
Applies To
- Okta Identity Engine (OIE)
- Okta Classic Engine
- Microsoft Office 365
- Microsoft Entra ID
Cause
Microsoft Entra ID enforces an MFA requirement through a Conditional Access policy or Security Defaults. During the authentication process, Microsoft sends a WS-Federation parameter to Okta:
wauth: http://schemas.microsoft.com/claims/multipleauthn
Example using SAML-tracer:
This parameter explicitly commands Okta to require MFA, overriding any lenient Okta sign-on policies. If the user account lacks enrolled authenticators, Okta evaluates the enrollment policy and prompts the user to set up an authenticator.
Solution
How is the Microsoft Entra ID Conditional Access policy adjusted?
Exclude the affected user account from the Microsoft Entra ID Conditional Access policy to prevent multiple authentication parameters from being sent to Okta.
- Check the Microsoft Entra ID Conditional Access policies or Security Defaults targeting the specific user account or the enterprise application.
- Either exclude the user account from the policy or disable the MFA requirement on Microsoft's side.
- Verify that the user logs in successfully without an MFA prompt.
