Skip to content

Commit 831434a

Browse files
authored
Merge pull request #3277 from denisebmsft/docs-editor/alert-policies-1742941871
Update alert-policies.md
2 parents 58fb618 + 91deb8b commit 831434a

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

defender-xdr/alert-policies.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: "Microsoft 365 alert policies"
2+
title: Alert policies in the Microsoft Defender portal
33
f1.keywords:
44
- NOCSH
55
ms.author: diannegali
@@ -23,7 +23,7 @@ ms.custom:
2323
description: "Create alert policies in the Microsoft Defender portal to monitor potential threats."
2424
---
2525

26-
# Alert policies in Microsoft 365
26+
# Alert policies in the Microsoft Defender portal
2727

2828
You can use alert policies and the alerts dashboard in the Microsoft Defender portal to create alert policies and then view the alerts that are generated when users perform activities that match the conditions of an alert policy. There are several default alert policies that help you monitor activities, such as assigning admin privileges in Exchange Online, malware attacks, phishing campaigns, and unusual levels of file deletions or external sharing.
2929

@@ -96,7 +96,7 @@ You can also define user tags as a condition of an alert policy. This definition
9696
- **When the alert is triggered**. You can configure a setting that defines how often an activity can occur before an alert is triggered. This allows you to set up a policy to generate an alert every time an activity matches the policy conditions, when a certain threshold is exceeded, or when the occurrence of the activity the alert is tracking becomes unusual for your organization.
9797

9898
![Configure how alerts are triggered, based on when the activity occurs, a threshold, or unusual activity for your organization.](media/howalertsaretriggered.png)
99-
99+
100100
If you select the setting based on unusual activity, Microsoft establishes a baseline value that defines the normal frequency for the selected activity. It takes up to seven days to establish this baseline, during which alerts aren't generated. After the baseline is established, an alert is triggered when the frequency of the activity tracked by the alert policy greatly exceeds the baseline value. For auditing-related activities (such as file and folder activities), you can establish a baseline based on a single user or based on all users in your organization; for malware-related activities, you can establish a baseline based on a single malware family, a single recipient, or all messages in your organization.
101101

102102
> [!NOTE]

0 commit comments

Comments
 (0)