Skip to content

Commit d5f487c

Browse files
committed
Update how-to-migrate-mfa-server-to-azure-mfa-user-authentication.md
1 parent 8e4519f commit d5f487c

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/active-directory/authentication/how-to-migrate-mfa-server-to-azure-mfa-user-authentication.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -64,7 +64,7 @@ If you are already using Conditional Access to determine when users are prompted
6464
As users are migrated to cloud authentication, they will start using Azure AD MFA as defined by your existing Conditional Access policies.
6565
They won’t be redirected to AD FS and MFA Server anymore.
6666

67-
If your federated domain(s) have the [federatedIdpMfaBehavior](/graph/api/resources/federatedIdpMfaBehavior?view=graph-rest-beta) set to `enforceMfaByFederatedIdp` or **SupportsMfa** flag set to `$True`, you are likely enforcing MFA on AD FS using claims rules.
67+
If your federated domain(s) have the [federatedIdpMfaBehavior](/graph/api/resources/federatedIdpMfaBehavior?view=graph-rest-beta) set to `enforceMfaByFederatedIdp` or **SupportsMfa** flag set to `$True` (the **federatedIdpMfaBehavior** overrides **SupportsMfa** when both are set), you are likely enforcing MFA on AD FS using claims rules.
6868
In this case, you will need to analyze your claims rules on the Azure AD relying party trust and create Conditional Access policies that support the same security goals.
6969

7070
If you need to configure Conditional Access policies, you need to do so before enabling staged rollout.

0 commit comments

Comments
 (0)