Skip to content

Commit 0602839

Browse files
Merge branch 'main' into repo_sync_working_branch
2 parents 32dc4a2 + 85204de commit 0602839

File tree

5 files changed

+11
-6
lines changed

5 files changed

+11
-6
lines changed

ATPDocs/investigate-assets.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -63,9 +63,10 @@ When you investigate a specific identity, you'll see the following details on an
6363
|[Remediation actions](/microsoft-365/security/defender/investigate-users#remediation-actions) | Respond to compromised users by disabling their accounts or resetting their password. After taking action on users, you can check on the activity details in the Microsoft Defender XDR **Action center.|
6464

6565
> [!NOTE]
66-
> **Investigation Priority Score** has been deprecated on December 3, 2025. As a result, both the Investigation Priority Score breakdown and the scored activity timeline cards have been removed from the UI.
66+
> **Investigation Priority Score** has been deprecated on December 3, 2024. As a result, both the Investigation Priority Score breakdown and the scored activity timeline cards have been removed from the UI.
67+
68+
6769

68-
6970
For more information, see [Investigate users](/microsoft-365/security/defender/investigate-users) in the Microsoft Defender XDR documentation.
7071

7172
## Investigation steps for suspicious groups

ATPDocs/whats-new.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -24,6 +24,10 @@ For updates about versions and features released six months ago or earlier, see
2424

2525
## March 2025
2626

27+
### New Health Issue
28+
29+
New [health issue](health-alerts.md#network-configuration-mismatch-for-sensors-running-on-vmware) for cases where sensors running on VMware have network configuration mismatch.
30+
2731
### Enhanced Identity Inventory (Preview)
2832

2933
The Identities page under *Assets* has been updated to provide better visibility and management of identities across your environment.

defender-office-365/mdo-support-teams-about.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -160,5 +160,5 @@ For detailed syntax and parameter information, see [Set-TeamsProtectionPolicyRul
160160
- [Microsoft Teams](/microsoftteams/teams-overview)
161161
- [Managing Teams quarantined messages](quarantine-admin-manage-messages-files.md#use-the-microsoft-defender-portal-to-manage-microsoft-teams-quarantined-messages)
162162
- [Get started using Attack simulation training in Defender for Office 365](attack-simulation-training-get-started.md)
163-
- [Get started with Defender for Cloud Apps for Microsoft Teams] (/defender-cloud-apps/what-is-defender-for-cloud-apps)
163+
- [Get started with Defender for Cloud Apps for Microsoft Teams](/defender-cloud-apps/what-is-defender-for-cloud-apps)
164164
- [Get started with Compliance and DLP protection for Microsoft Teams](/microsoftteams/security-compliance-overview)

defender-office-365/submissions-users-report-message-add-in-configure.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -168,9 +168,9 @@ A: We recommend you update clients in the Microsoft admin center or ask users to
168168

169169
### Q: The Report phishing add-in offers a single report option but the built-in Report button has more options. What can I do?
170170

171-
A: This design was finalized after partnership with more than 50 customers and a Private Preview of approximately two and half years. Many customers who had this question are actually much more comfortable with the built-in **Report** button.
171+
A: This design was finalized after partnership with more than 50 customers and a Private Preview of approximately two and half years. Many customers who had this question are actually much more comfortable with the built-in **Report** button. They have transitioned completely to the built-in **Report** button.
172172

173-
They transitioned completely to the built-in **Report** button. Users were instructed to use the default action (split) for reporting messages as phishing, and to use the side menu to report messages as other types (Junk or Not junk).
173+
The built-in **Report** button is a split button. Clicking on the button without using the dropdown list reports the message as phishing. Use the dropdown list to report messages as junk or not junk.
174174

175175
We recommend that you try the built-in **Report** button. If you're still facing issues, you can always reach out to us via Microsoft Support.
176176

defender-xdr/investigate-users.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -60,7 +60,7 @@ The user page shows the Microsoft Entra organization as well as groups, helping
6060
The **Entity details** panel on the left side of the page provides information about the user, such as the Microsoft Entra identity risk level, the insider risk severity level (Preview), the number of devices the user is signed in to, when the user was first and last seen, the user's accounts, groups that the user belongs to, contact information, and more. You see other details depending on the integration features you enabled.
6161

6262
> [!NOTE]
63-
> **Investigation Priority Score** has been deprecated on December 3, 2025. As a result, both the Investigation Priority Score breakdown and the Scored activities cards have been removed from the UI.
63+
> **Investigation Priority Score** has been deprecated on December 3, 2024. As a result, both the Investigation Priority Score breakdown and the Scored activities cards have been removed from the UI.
6464
6565
> [!NOTE]
6666
> (Preview) Microsoft Defender XDR users with access to [Microsoft Purview Insider Risk Management](/purview/insider-risk-management-solution-overview) can now see a user's insider risk severity and gain insights on a user's suspicious activities in the user page. Select the **insider risk severity** under Entity details to see the risk insights about the user.

0 commit comments

Comments
 (0)