Skip to content

Commit b2583ec

Browse files
[Azure AD] Multi-Factor to Multifactor
1 parent 13d4172 commit b2583ec

File tree

3 files changed

+3
-3
lines changed

3 files changed

+3
-3
lines changed

articles/active-directory/conditional-access/concept-conditional-access-policies.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ All policies are enforced in two phases:
3636
- Use the session details gathered in phase 1 to identify any requirements that haven't been met.
3737
- If there's a policy that is configured to block access, with the block grant control, enforcement will stop here and the user will be blocked.
3838
- The user will be prompted to complete more grant control requirements that weren't satisfied during phase 1 in the following order, until policy is satisfied:
39-
1. [Multifactor Authentication​](concept-conditional-access-grant.md#require-multi-factor-authentication)
39+
1. [Multifactor Authentication​](concept-conditional-access-grant.md#require-multifactor-authentication)
4040
2. [Device to be marked as compliant](./concept-conditional-access-grant.md#require-device-to-be-marked-as-compliant)
4141
3. [Hybrid Azure AD joined device](./concept-conditional-access-grant.md#require-hybrid-azure-ad-joined-device)
4242
4. [Approved client app](./concept-conditional-access-grant.md#require-approved-client-app)

articles/active-directory/conditional-access/howto-conditional-access-policy-authentication-strength-external.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ You can use one of the built-in strengths or create a [custom authentication str
2929
In external user scenarios, the MFA authentication methods that a resource tenant can accept vary depending on whether the user is completing MFA in their home tenant or in the resource tenant. For details, see [Conditional Access authentication strength](https://aka.ms/b2b-auth-strengths).
3030

3131
> [!NOTE]
32-
> Currently, you can only apply authentication strength policies to external users who authenticate with Azure AD. For email one-time passcode, SAML/WS-Fed, and Google federation users, use the [MFA grant control](concept-conditional-access-grant.md#require-multi-factor-authentication) to require MFA.
32+
> Currently, you can only apply authentication strength policies to external users who authenticate with Azure AD. For email one-time passcode, SAML/WS-Fed, and Google federation users, use the [MFA grant control](concept-conditional-access-grant.md#require-multifactor-authentication) to require MFA.
3333
3434
## Configure cross-tenant access settings to trust MFA
3535

articles/active-directory/conditional-access/howto-conditional-access-session-lifetime.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -101,7 +101,7 @@ Supported scenarios:
101101

102102
- Require user reauthentication during [Intune device enrollment](/mem/intune/fundamentals/deployment-guide-enrollment), regardless of their current MFA status.
103103
- Require user reauthentication for risky users with the [require password change](concept-conditional-access-grant.md#require-password-change) grant control.
104-
- Require user reauthentication for risky sign-ins with the [require multifactor authentication](concept-conditional-access-grant.md#require-multi-factor-authentication) grant control.
104+
- Require user reauthentication for risky sign-ins with the [require multifactor authentication](concept-conditional-access-grant.md#require-multifactor-authentication) grant control.
105105

106106
When administrators select **Every time**, it will require full reauthentication when the session is evaluated.
107107

0 commit comments

Comments
 (0)