Skip to content

Commit 84c207a

Browse files
committed
Update add-advanced-hunting-community-queries.md
Per TR
1 parent c86fd59 commit 84c207a

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

defender-office-365/step-by-step-guides/add-advanced-hunting-community-queries.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -125,7 +125,7 @@ Go to the next section to actually start creating or modifying queries.
125125

126126
## Step 4: Create Advanced Hunting queries in the working branch in the cloned repository on your local computer
127127

128-
When you open VS Code to create or update queries, alway verify that your desired working branch (not **master**) is the active branch:
128+
When you open VS Code to create or update queries, always verify your desired working branch is the active branch (not **master**):
129129

130130
:::image type="content" source="../media/add-advanced-hunting-community-queries-vs-code-verify-active-branch.png" alt-text="Screenshot of the active (open) branch highlighted in Visual Studio Code, which is now the new branch that you created in the previous step." lightbox="../media/add-advanced-hunting-community-queries-vs-code-verify-active-branch.png":::
131131

@@ -156,28 +156,28 @@ If it isn't, select the active branch name in the bottom left corner, and then s
156156

157157
You can find more information on the requirements and structure of the .yaml file at [Query Style Guide](https://github.com/Azure/Azure-Sentinel/wiki/Query-Style-Guide) on the Azure-Sentinel repository wiki.
158158

159-
Use the [New-Guid](/powershell/module/microsoft.powershell.utility/new-guid) cmdlet in Windows PowerShell to create a unique GUID for the **id** property of the query file (for example, 36f68d74-3e45-44d8-9915-ød35b7567bcf).
159+
Use the [New-Guid](/powershell/module/microsoft.powershell.utility/new-guid) cmdlet in Windows PowerShell to create a unique GUID for the **id** property of the query file (for example, 36f68d74-3e45-44d8-9915-0d35b7567bcf).
160160

161161
The finished `Top user receiving phish.yaml` file looks something like this:
162162

163163
```yml
164-
id: 36f68d74-3e45-44d8-9915-ød35b7567bcf
164+
id: 36f68d74-3e45-44d8-9915-0d35b7567bcf
165165
name: Friendly name describing the query
166166
description: |
167167
This is a short description of what the query does
168168
description-detailed: |
169-
This is a much longer description Of what the intention Of the query is within Defender for Office 365
169+
This is a much longer description of what the intention of the query is within Defender for Office 365
170170
requiredDataConnectors:
171-
- connectorld: Microsoft ThreatProtection
171+
- connectorId: MicrosoftThreatProtection
172172
dataTypes:
173173
- EmailEvents
174174
tactics:
175175
- InitialAccess
176-
relevant Techniques :
176+
relevantTechniques:
177177
- T1566
178178
query: |
179179
EmailEvents
180-
| where Threat Types has "Phish" and EmailDirection == "Inbound"
180+
| where Threat Types has "Phish" and EmaiIdirection == "Inbound"
181181
| summarize count() by RecipientEmailAddress
182182
| sort by count_
183183
| top 15 by count_

0 commit comments

Comments
 (0)