You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
| Set up, pause, or remove the agent, and manage agent identity |**Security Administrator** in Microsoft Entra ID |
58
-
| View and manage agent settings |**Security Copilot (read)** and **Security data basics (read)** under the **Security operations** permissions group in the Defender portal |
59
-
| View and manage feedback |**Security Copilot (read)**, **Security data basics (read)**, and **Email & collaboration metadata (read)** under the **Security operations** permissions group in the Defender portal|
57
+
| View agent results |To view agent results, you need the same permissions as the agent, or higher permissions:<br>**Security Copilot (read)**, **Security data basics (read)**, **Alerts (manage)**, **Email & collaboration metadata (read)**, and **Email & collaboration content (read)** under the **Security operations** permissions group in the Defender portal|
58
+
| View agent settings |**Security Copilot (read)** and **Security data basics (read)** under the **Security operations** permissions group in the Defender portal |
59
+
| View feedback page |**Security Copilot (read)**, **Security data basics (read)**, and **Email & collaboration metadata (read)** under the **Security operations** permissions group in the Defender portal <br>Or **Security Administrator** in Microsoft Entra ID|
60
+
| Manage agent settings (set up, pause, or remove the agent, and manage agent identity) |**Security Administrator** in Microsoft Entra ID |
60
61
|Reject feedback|**Security Administrator** in Microsoft Entra ID|
61
-
| View agent results |**Security Copilot (read)**, **Security data basics (read)**, **Alerts (manage)**, **Email & collaboration metadata (read)**, and **Email & collaboration content (read)** under the **Security operations** permissions group in the Defender portal|
62
62
63
63
For more information about unified RBAC in the Defender portal, see [Microsoft Defender XDR Unified role-based access control (RBAC)](/defender-xdr/manage-rbac).
64
64
@@ -110,7 +110,7 @@ The Phishing Triage Agent currently only operates with existing user accounts. F
110
110
When you connect the agent to an account, we recommend setting a long account expiration date and closely monitoring its authentication status to ensure continuous operation of the agent. If authentication expires, the agent stops functioning until it’s renewed.
111
111
112
112
> [!TIP]
113
-
> Microsoft recommends creating and using a dedicated identity account with the minimum required permissions for the agent. When creating the account, assign a distinct display name like *Phishing Triage Agent* to easily identify it in the Microsoft Defender portal.
113
+
> We recommend creating and using a dedicated identity account with the minimum required permissions for the agent. When creating the account, assign a distinct display name like *Phishing Triage Agent* to easily identify it in the Microsoft Defender portal.
114
114
115
115
The agent's specified user identity isn't compatible with PIM or TAP, as they don't support long-term background operations.
116
116
@@ -153,12 +153,12 @@ You can access the Phishing Triage Agent setup in two ways:
153
153
154
154
:::image type="content" source="/defender/media/agents-in-defender/phishing-triage/phishing-triage-setup-incident.png" alt-text="Screenshot of the incident queue with the Phishing Triage card where Set up agent is highlighted" lightbox="/defender/media/agents-in-defender/phishing-triage/phishing-triage-setup-incident.png":::
155
155
156
-
- Alternatively, go to **System > Settings > Microsoft Defender XDR**. Under **Agents**, select **Overview > Set up** to start the process.
156
+
- Alternatively, select **System > Settings > Microsoft Defender XDR > Phishing Triage Agent > Overview > Set up** to start the process.
157
157
158
158
:::image type="content" source="/defender/media/agents-in-defender/phishing-triage/phishing-triage-setup.png" alt-text="Screenshot of the Overview page for the Phishing Triage set up" lightbox="/defender/media/agents-in-defender/phishing-triage/phishing-triage-setup.png":::
159
159
160
160
> [!NOTE]
161
-
> To view and manage setting in the Defender portal, you need **Security Copilot (read)** and **Security data basics (read)** permissions. If you don't have these permissions, you can't intiate setup from the **Settings** page, but you can still set up the agent from the incident queue if you have the **Security Administrator** role.
161
+
> To view and manage setting in the Defender portal, you need **Security Copilot (read)** and **Security data basics (read)** permissions. If you don't have these permissions, you can't initiate setup from the **Settings** page, but you can still set up the agent from the incident queue if you have the **Security Administrator** role.
162
162
163
163
Follow the steps in the setup wizard, which includes:
164
164
@@ -171,15 +171,15 @@ Follow the steps in the setup wizard, which includes:
171
171
:::image type="content" source="/defender/media/agents-in-defender/phishing-triage/setup-assign-user.PNG" alt-text="Screenshot of the account assignment for Phishing Triage" lightbox="/defender/media/agents-in-defender/phishing-triage/setup-assign-user.PNG":::
172
172
173
173
> [!NOTE]
174
-
> After setup, you can change the agent's identity and role at any time. To do this, navigate to **System > Settings > Microsoft Defender XDR**. Under **Agents**, select **Identity and role**.
174
+
> After setup, you can change the agent's identity and role at any time. To do this, select **Settings > Microsoft Defender XDR > Phishing Triage Agent > Identity and role**.
175
175
176
176
1. Select **Deploy agent** to activate the agent.
177
177
1. Select **View incidents** to navigate back to the incidents queue or **Manage agent** to manage its settings.
178
178
179
179
180
180
The Phishing Triage Agent is now set up and running in the background, ready to triage user-reported phishing incidents coming in. Your incident queue now contains the Phishing Triage Agent card with the agent’s relevant metrics. This data helps demonstrate the agent’s impact and can be used to inform broader strategic conversations, highlight return on investment, or support decisions around scaling automation across your organization.
181
181
182
-
The card currently contains the following data:
182
+
The card shows:
183
183
184
184
-**Incidents addressed:** Incidents containing user-reported phishing alerts that the agent classified as true phishing threats or false alarms.
185
185
-**Incidents resolved:** Incidents that no longer require further handling, like false alarms.
@@ -190,10 +190,7 @@ Metrics are calculated based on the agent’s activity, beginning either from it
190
190
191
191
## Enhance incident response with the Phishing Triage Agent
192
192
193
-
> [!TIP]
194
-
> Only users with permissions equal to or higher than the agent’s can monitor its activity and view its output.
195
-
196
-
The agent is designed to help security teams manage the overwhelming volume of suspicious emails organizations receive daily. Acting as a force multiplier for SOC teams, it offloads time-consuming triage tasks, reduces alert fatigue, and accelerates incident response by autonomously identifying true phishing threats. This enables analysts to cut through the noise and focus their attention on the threats that truly matter.
193
+
The agent is designed to help security teams manage the overwhelming volume of suspicious emails organizations receive daily. Acting as a force multiplier for SOC teams, the agent offloads time-consuming triage tasks, reduces alert fatigue, and accelerates incident response by autonomously identifying true phishing threats. This enables analysts to cut through the noise and focus their attention on the threats that truly matter.
197
194
198
195
### Agent trigger and flow
199
196
@@ -205,7 +202,7 @@ For every alert it processes, the agent provides a detailed explanation of its v
205
202
206
203
### Collaborate with the agent
207
204
208
-
To maintain transparency, the agent routinely updates incident fields during the triage process. When triaging starts, the agent assigns the alert to itself and adds an **Agent** tag to the corresponding incident. Analysts can filter the incident queue to see only those tagged by the agent, which simplifies oversight and prioritization.
205
+
To maintain transparency, the agent routinely updates incident fields during the triage process. When triaging starts, the agent assigns the alert to itself and adds an **Agent** tag to the corresponding incident. Analysts can filter the incident queue to see only incidents tagged by the agent, which simplifies oversight and prioritization.
209
206
210
207
> [!TIP]
211
208
> You can also filter the incident queue using the name of the identity you assigned to the Phishing Triage Agent to see the incidents the agent is actively working on.
@@ -260,13 +257,13 @@ The agent utilizes stored feedback to triage and classify similar alerts in the
260
257
261
258
### Best practices for writing feedback
262
259
263
-
Lessons provide systematic guidelines that help the agent determine whether an alert is a genuine phishing threat or a false alarm. To ensure the agent effectively incorporates your feedback, Microsoft recommends following these best practices when providing input to the Phishing Triage Agent:
260
+
Lessons provide systematic guidelines that help the agent determine whether an alert is a genuine phishing threat or a false alarm. To ensure the agent effectively incorporates your feedback, follow these best practices when providing input to the Phishing Triage Agent:
264
261
265
262
1.**Ensure feedback is relevant and contextual.** Feedback should pertain only to the email currently under review. It must also align with the updated classification you’ve assigned.
266
263
1.**Be descriptive and specific.** Clearly explain the characteristics of the email. Provide relevant details like the email subject, message body, sender, or recipients to help the agent understand the context. Specific feedback with multiple details enhances effectiveness.
267
-
1.**Ensure clarity and decisiveness.** Avoid vague or universal statements. Give feedback that is clear and actionable. Use decisive and clear identification terms.
264
+
1.**Ensure clarity and decisiveness.** Avoid vague or universal statements. Give feedback that's clear and actionable. Use decisive and clear identification terms.
268
265
1.**Be consistent with previous feedback.** Ensure that new feedback aligns with what was previously provided to avoid contradictions that could confuse the agent or reduce the accuracy of its decisions. You can review all previously submitted input on the [Feedback](#view-and-manage-feedback-to-the-agent) management page.
269
-
1.**Review the agent’s interpretation of your feedback.**After submitting it, always verify that the feedback is accurately translated into a lesson. Confirm that it reflects your intent and maintains consistency with your original input. Checking the validity of AI-generated responses ensures these are applicable to the scenario.
266
+
1.**Review the agent’s interpretation of your feedback.**When you submit feedback, always verify that the feedback is accurately translated into a lesson. Confirm that the lesson reflects your intent and maintains consistency with your original input. Checking the validity of AI-generated responses to ensure they are applicable to the scenario.
270
267
271
268
Here are examples of how you can write your feedback to the agent.
272
269
@@ -299,23 +296,17 @@ Once the agent is taught and equipped with organizational knowledge, it begins t
299
296
300
297
## Manage the Phishing Triage Agent
301
298
302
-
> [!NOTE]
303
-
> To view and manage Phishing Triage Agent settings, you need **Security Copilot (read)** and **Security data basics (read)** permissions.
304
-
305
-
You can manage the Phishing Triage Agent’s settings, review its activity, and review user interaction with the agent. To do so, select **Manage agent** in the card above the incident queue. Alternatively, you can navigate to **Settings > Microsoft Defender XDR > Agents**.
299
+
To manage the Phishing Triage Agent’s settings, review its activity, and review user interactions with the agent, select **Manage agent** in the card above the incident queue. Alternatively, select **Settings > Microsoft Defender XDR > Phishing Triage Agent > Feedback**.
306
300
307
301
### View agent’s previous activity
308
302
309
303
To view all previous runs by the agent:
310
304
311
-
1.Navigate to the **Overview** page under **Agents** in the Defender portal.
312
-
1. Select **View agent activity**. Once selected, the Security Copilot portal opens in a new tab. The tab opens to a table listing all the agent’s recent activities and details.
1. Select **View agent activity**.<br>This opens the Security Copilot portal in a new tab. The tab opens to a table listing all the agent’s recent activities and details.
313
307
314
308
### View and manage feedback to the agent
315
309
316
-
> [!NOTE]
317
-
> To manage feedback, you need **Security Copilot (read)**, **Security data basics (read)**, and **Email & collaboration metadata (read)** permissions.
318
-
319
310
The Phishing Triage Agent uses feedback to improve its performance over time. It stores applicable feedback in its memory as lessons. You can view and manage user-submitted feedback for the Phishing Triage Agent by navigating to the Feedback management page.
320
311
321
312
This page provides a comprehensive list of all feedback submitted to the agent. You can review key details for each piece of feedback, including:
@@ -353,35 +344,31 @@ To reject specific feedback, open the Review feedback pane and select **Reject f
353
344
354
345
### Change the agent’s identity and role
355
346
356
-
> [!NOTE]
357
-
> Changing the Phishing Triage Agent’s identity is only available to users with the **Security Administrator** role.
347
+
To manage the agent’s identity and role at any time, select **System > Settings > Microsoft Defender XDR > Phishing Triage Agent > Overview > Identity and role**.
358
348
359
-
The agent’s identity and role can be managed at any time by navigating to the **Identity and role** page under **Agents**. On this page, users can view the agent's current identity, access details about the last update, and select a new identity type for the agent if necessary. The process of changing an identity is similar to the initial setup of the agent’s identity and role.
349
+
On this page, you can view the agent's current identity, access details about the last update, and select a new identity type for the agent if necessary. The process of changing an identity is similar to the initial setup of the agent’s identity and role.
360
350
361
351
:::image type="content" source="/defender/media/agents-in-defender/phishing-triage/phishing-triage-identity-management.png" alt-text="Screenshot of the Identity and role management page" lightbox="/defender/media/agents-in-defender/phishing-triage/phishing-triage-identity-management.png":::
362
352
363
353
### Pause or resume the agent
364
354
365
-
> [!NOTE]
366
-
> Pausing the Phishing Triage Agent is only available to users with the **Security Administrator** role.
367
-
368
355
Pausing the agent temporarily stops all triage activity, including any in-progress triage tasks. The agent doesn’t process new incidents until it’s resumed. Resuming the agent resumes all its activities, allowing it to start triaging and classifying incoming alerts again.
369
356
370
357
To pause or resume the agent:
371
358
372
-
1.Navigate to the **Overview** page under **Agents** in Defender portal.
359
+
1.Select **System > Settings > Microsoft Defender XDR > Phishing Triage Agent > Overview** in Defender portal.
373
360
1. Select **Pause** to temporarily stop the agent. Once paused, the button updates to **Resume**, which you can select when you’re ready to reactivate the agent’s activities.
374
361
375
362
:::image type="content" source="/defender/media/agents-in-defender/phishing-triage/phishing-triage-overview.png" alt-text="Screenshot of the Agents Overview page highlighting the pause agent option" lightbox="/defender/media/agents-in-defender/phishing-triage/phishing-triage-overview.png":::
376
363
377
364
### Remove the agent
378
365
379
-
> [!NOTE]
380
-
> Removing the Phishing Triage Agent is only available to users with the **Security Administrator** role.
381
-
382
366
Removing the agent permanently disables it. Once removed, triage and classification of new incidents stop, and all feedback is deleted. However, the history of previously triaged incidents is retained for your reference.
383
367
384
-
To remove the agent, navigate to the **Overview** page under **Agents**, then select **Remove agent**.
@@ -397,7 +384,7 @@ Phishing remains one of the most common methods by which attackers gain initial
397
384
398
385
### Can the Phishing Triage Agent be trusted?
399
386
400
-
Microsoft AI agents follow strict Responsible AI guidelines and undergo thorough reviews to ensure compliance with all AI standards and safeguards. Security Copilot’s Phishing Triage Agent is fully incorporated into these controls. During setup, the agent is assigned an identity and configured with the minimum required permissions for its operation, ensuring that it doesn’t have unnecessary permissions. All agent activities are logged in detail, with the complete flow available for review by analysts and admins at any time. Feedback provided to the agent to help it adapt to the organization’s environment is logged, reflected in the system, and accessible for review and modification by admins as needed.
387
+
Microsoft AI agents follow strict Responsible AI guidelines and undergo thorough reviews to ensure compliance with all AI standards and safeguards. Security Copilot’s Phishing Triage Agent is fully incorporated into these controls. During setup, you assign the agent an identity and configure it with the minimum permissions required for its operation, ensuring that it doesn’t have unnecessary permissions. All agent activities are logged in detail, with the complete flow available for review by analysts and admins at any time. Feedback provided to the agent to help it adapt to the organization’s environment is logged, reflected in the system, and accessible for review and modification by admins as needed.
401
388
402
389
### How does the agent differ from a standard SOAR solution?
0 commit comments