Skip to content

Commit 07980fd

Browse files
committed
added manage and report sections
1 parent 940aee0 commit 07980fd

File tree

1 file changed

+10
-1
lines changed

1 file changed

+10
-1
lines changed

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

Lines changed: 10 additions & 1 deletion
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: 01/29/2023
9+
ms.date: 02/13/2023
1010

1111
ms.author: justinha
1212
author: justinha
@@ -98,6 +98,15 @@ When a user reports a MFA prompt as suspicious, the event shows up in the Sign-i
9898

9999
- To view fraud reports in the Audit logs, select **Azure Active Directory** > **Audit logs**. The fraud report appears under Activity type Fraud reported - user is blocked for MFA or Fraud reported - no action taken based on the tenant-level settings for fraud report.
100100

101+
### Manage suspicious activity events
102+
103+
Once a user has reported a prompt as suspicious, the risk should be investigated and remediated with [Identity Protection](/azure/active-directory/identity-protection/howto-identity-protection-remediate-unblock).
104+
105+
### Report suspicious activity and fraud alert
106+
107+
**Report Suspicious Activity** and the legacy **Fraud Alert** implementation can operate in parallel. You can keep your tenant-wide **Fraud Alert** functionality in place while you start to use **Report Suspicious Activity** with a targeted test group.
108+
109+
If **Fraud Alert** is enabled with Automatic Blocking, and **Report Suspicious Activity** is enabled, the user will be added to the blocklist and set as high-risk and in-scope for any other policies configured. These users will need to be removed from the blocklist and have their risk remediated to enable them to sign in with MFA.
101110

102111
## Notifications
103112

0 commit comments

Comments
 (0)