Skip to content

Commit f565a31

Browse files
authored
Update create-manage-use-automation-rules.md
1 parent 0efc704 commit f565a31

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/sentinel/create-manage-use-automation-rules.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -94,7 +94,7 @@ Use the options in the **Conditions** area to define conditions for your automat
9494

9595
Analytic rule name values include only analytics rules, and don't include other types of rules, such as threat intelligence or anomaly rules.
9696

97-
- Rules you create for when an incident is created or updated support a large variety of conditions, depending on your environment. These options start with whether your workspace is onboarded to the Defender portal:
97+
- Rules you create for when an incident is created or updated support a large variety of conditions, depending on your environment. These options start with whether your workspace is onboarded to the unified security operations (SecOps) platform:
9898

9999
#### [Onboarded workspaces](#tab/onboarded)
100100

@@ -145,7 +145,7 @@ Use the options in the **Conditions** area to define conditions for your automat
145145
1. Select an operator from the next drop-down box to the right.
146146
:::image type="content" source="media/create-manage-use-automation-rules/select-operator.png" alt-text="Screenshot of selecting a condition operator for automation rules.":::
147147

148-
The list of operators you can choose from varies according to the selected trigger and property.
148+
The list of operators you can choose from varies according to the selected trigger and property. When working with the unified SecOps platform recommend that you use the **Analytic rule name** condition instead of an incident title.
149149

150150
#### Conditions available with the create trigger
151151

0 commit comments

Comments
 (0)