Skip to content

Commit 50d1ae5

Browse files
Merge pull request #243408 from Justinha/acct-lock
revised heading and added note for account lockout
2 parents 8f5e6d4 + 71b1d82 commit 50d1ae5

File tree

1 file changed

+8
-5
lines changed

1 file changed

+8
-5
lines changed

articles/active-directory/authentication/howto-mfa-mfasettings.md

Lines changed: 8 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ services: multi-factor-authentication
66
ms.service: active-directory
77
ms.subservice: authentication
88
ms.topic: how-to
9-
ms.date: 06/26/2023
9+
ms.date: 06/29/2023
1010

1111
ms.author: justinha
1212
author: justinha
@@ -19,12 +19,12 @@ ms.custom: contperf-fy20q4
1919
# Configure Azure AD Multi-Factor Authentication settings
2020

2121
To customize the end-user experience for Azure AD Multi-Factor Authentication, you can configure options for settings like account lockout thresholds or fraud alerts and notifications. Some settings are available directly in the Azure portal for Azure Active Directory (Azure AD), and some are in a separate Azure AD Multi-Factor Authentication portal.
22-
22+
2323
The following Azure AD Multi-Factor Authentication settings are available in the Azure portal:
2424

2525
| Feature | Description |
2626
| ------- | ----------- |
27-
| [Account lockout](#account-lockout) | Temporarily lock accounts from using Azure AD Multi-Factor Authentication if there are too many denied authentication attempts in a row. This feature applies only to users who enter a PIN to authenticate. (MFA Server only) |
27+
| [Account lockout (MFA Server only)](#account-lockout-mfa-server-only) | Temporarily lock accounts from using Azure AD Multi-Factor Authentication if there are too many denied authentication attempts in a row. This feature applies only to users who use MFA Server to enter a PIN to authenticate. |
2828
| [Block/unblock users](#block-and-unblock-users) | Block specific users from being able to receive Azure AD Multi-Factor Authentication requests. Any authentication attempts for blocked users are automatically denied. Users remain blocked for 90 days from the time that they're blocked or until they're manually unblocked. |
2929
| [Report suspicious activity](#report-suspicious-activity) | Configure settings that allow users to report fraudulent verification requests. |
3030
| [Notifications](#notifications) | Enable notifications of events from MFA Server. |
@@ -34,9 +34,12 @@ The following Azure AD Multi-Factor Authentication settings are available in the
3434

3535
![Azure portal - Azure AD Multi-Factor Authentication settings](./media/howto-mfa-mfasettings/multi-factor-authentication-settings-portal.png)
3636

37-
## Account lockout
37+
## Account lockout (MFA Server only)
38+
39+
>[!NOTE]
40+
>Account lockout only affects users who sign in by using MFA Server on-premises.
3841
39-
To prevent repeated MFA attempts as part of an attack, the account lockout settings let you specify how many failed attempts to allow before the account becomes locked out for a period of time. The account lockout settings are applied only when a PIN code is entered for the MFA prompt.
42+
To prevent repeated MFA attempts as part of an attack, the account lockout settings let you specify how many failed attempts to allow before the account becomes locked out for a period of time. The account lockout settings are applied only when a PIN code is entered for the MFA prompt by using MFA Server on-premises.
4043

4144
The following settings are available:
4245

0 commit comments

Comments
 (0)