Skip to content

Commit ef70e18

Browse files
Merge pull request #4889 from MicrosoftDocs/main
[AutoPublish] main to live - 09/01 01:35 PDT | 09/01 14:05 IST
2 parents b380864 + adb51cc commit ef70e18

File tree

3 files changed

+10
-7
lines changed

3 files changed

+10
-7
lines changed

defender-endpoint/investigate-user.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -60,7 +60,10 @@ The **User details** pane on left provides information about the user, such as r
6060
The Overview, Alerts, and Observed in organization are different tabs that display various attributes about the user account.
6161

6262
> [!NOTE]
63-
> For Linux devices, information about logged in users is not displayed.
63+
> For Linux devices, information about logged in users isn't displayed.
64+
65+
> [!NOTE]
66+
> Microsoft Defender for Business doesn't include Microsoft Defender for Identity (MDI) by default. In SMB-based environments, Logon User data won't be available unless MDI sensors are installed. To ensure visibility into logon events, customers must deploy MDI sensors.
6467
6568
### Overview
6669

defender-endpoint/linux-install-with-saltack.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -153,7 +153,7 @@ In this step, you create a SaltState state file in your configuration repository
153153
```console
154154
install_mdatp_package:
155155
pkg.installed:
156-
- name: matp
156+
- name: mdatp
157157
- required: add_ms_repo
158158
```
159159

defender-endpoint/respond-machine-alerts.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -2,11 +2,11 @@
22
title: Take response actions on a device in Microsoft Defender for Endpoint
33
description: Take response actions on a device such as isolating devices, collecting an investigation package, managing tags, running an antivirus scan, and restricting app execution.
44
ms.service: defender-endpoint
5-
ms.author: diannegali
6-
author: diannegali
5+
ms.author: painbar
6+
author: paulinbar
77
ms.localizationpriority: medium
8-
ms.date: 07/01/2025
9-
manager: deniseb
8+
ms.date: 09/01/2025
9+
manager: bagol
1010
audience: ITPro
1111
ms.collection:
1212
- m365-security
@@ -330,7 +330,7 @@ You're be able to stop containing a device at any time.
330330
Defender for Endpoint can also contain IP addresses associated with devices that are undiscovered or are not onboarded to Defender for Endpoint. The capability to contain an IP address prevents attackers from spreading attacks to other non-compromised devices. Containing an IP address results in Defender for Endpoint-onboarded devices blocking incoming and outgoing communication with devices using the contained IP address
331331

332332
> [!NOTE]
333-
> Blocking incoming and outgoing communication with a 'contained' device is supported on onboarded Defender for Endpoint Windows 10, Windows 2012 R2, Windows 2016, and Windows Server 2019+ devices.
333+
> Blocking incoming and outgoing communication with a 'contained' device is supported on onboarded Defender for Endpoint Windows 10, Windows 11, Windows 2012 R2, and Windows 2016 devices.
334334
335335
Containing an IP address associated with undiscovered devices or devices not onboarded to Defender for Endpoint is done automatically through [automatic attack disruption](/defender-xdr/automatic-attack-disruption). The Contain IP policy automatically blocks a malicious IP address when Defender for Endpoint detects the IP address to be associated with an undiscovered device or a device not onboarded.
336336

0 commit comments

Comments
 (0)