Skip to content

Commit 726281c

Browse files
authored
Merge branch 'main' into docs-editor/alert-policies-1746725824
2 parents b5f9ae7 + 19ba711 commit 726281c

34 files changed

+324
-242
lines changed

ATPDocs/deploy/remote-calls-sam.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -7,6 +7,10 @@ ms.topic: how-to
77

88
# Configure SAM-R to enable lateral movement path detection in Microsoft Defender for Identity
99

10+
> [!IMPORTANT]
11+
> Remote collection of local administrators' group members on endpoints (using SAM-R queries) feature in Microsoft Defender for Identity will be disabled by mid-May 2025.
12+
>
13+
1014
Microsoft Defender for Identity mapping for [potential lateral movement paths](/defender-for-identity/understand-lateral-movement-paths) relies on queries that identify local admins on specific machines. These queries are performed with the SAM-R protocol, using the Defender for Identity [Directory Service account](directory-service-accounts.md) you configured.
1115

1216
> [!NOTE]

ATPDocs/whats-new.md

Lines changed: 9 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -22,6 +22,15 @@ For more information, see also:
2222

2323
For updates about versions and features released six months ago or earlier, see the [What's new archive for Microsoft Defender for Identity](whats-new-archive.md).
2424

25+
## May 2025
26+
27+
### Local administrators collection (using SAM-R queries) feature will be disabled
28+
Remote collection of local administrators' group members on endpoints (using SAM-R queries) feature in Microsoft Defender for Identity will be disabled by mid-May 2025. The details collected are used to build the potential lateral movement paths map. Alternative methods are currently being explored.
29+
30+
### New Health Issue
31+
32+
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.
33+
2534
## April 2025
2635

2736
### Privileged Identity Tag Now Visible in Defender for Identity Inventory
@@ -47,7 +56,6 @@ For more information, see: [Integrations Defender for Identity and PAM services.
4756

4857
### New Service Account Discovery page
4958

50-
5159
Microsoft Defender for Identity now includes a Service Account Discovery capability, offering you centralized visibility into service accounts across your Active Directory environment.
5260

5361
This update provides:
@@ -60,11 +68,6 @@ This update provides:
6068

6169
For more information, see: [Investigate and protect Service Accounts | Microsoft Defender for Identity](service-account-discovery.md).
6270

63-
64-
### New Health Issue
65-
66-
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.
67-
6871
### Enhanced Identity Inventory
6972

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

CloudAppSecurityDocs/anomaly-detection-policy.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -64,14 +64,14 @@ Use this detection to control file uploads and downloads in real time with sessi
6464

6565
By enabling file sandboxing, files that according to their metadata and based on proprietary heuristics to be potentially risky, will also be sandbox scanned in a safe environment. The Sandbox scan may detect files that were not detected based on threat intelligence sources.
6666

67-
Defender for Cloud Apps supports malware detection for the following apps:
67+
Defender for Cloud Apps supports "File Sandboxing" malware detection for the following apps:
6868

6969
* Box
7070
* Dropbox
7171
* Google Workspace
7272

7373
> [!NOTE]
74-
>* Proactively sandboxing will be done in third party applications (*Box*, *Dropbox* etc.). In *OneDrive* and *SharePoint* files are being scanned and sandboxed as part of the service itself.
74+
>* Proactively sandboxing will be done in third party applications (*Box*, *Dropbox* etc.). **In *OneDrive* and *SharePoint* files are being scanned and sandboxed as part of the service itself**.
7575
> * In *Box*, *Dropbox*, and *Google Workspace*, Defender for Cloud Apps doesn't automatically block the file, but blocking may be performed according to the app's capabilities and the app's configuration set by the customer.
7676
> * If you're unsure about whether a detected file is truly malware or a false positive, go to the Microsoft Security Intelligence page at [https://www.microsoft.com/wdsi/filesubmission](https://www.microsoft.com/wdsi/filesubmission) and submit the file for further analysis.
7777

defender-endpoint/TOC.yml

Lines changed: 29 additions & 27 deletions
Original file line numberDiff line numberDiff line change
@@ -5,33 +5,33 @@
55
- name: Zero Trust with Defender for Endpoint
66
href: zero-trust-with-microsoft-defender-endpoint.md
77
- name: Overview
8-
items:
9-
- name: Defender for Endpoint on Windows
10-
href: microsoft-defender-endpoint.md
11-
- name: Defender for Endpoint on macOS
12-
href: microsoft-defender-endpoint-mac.md
13-
- name: Defender for Endpoint on Linux
14-
href: microsoft-defender-endpoint-linux.md
15-
- name: Defender for Endpoint on Android
16-
href: microsoft-defender-endpoint-android.md
17-
- name: Defender for Endpoint on iOS
18-
href: microsoft-defender-endpoint-ios.md
19-
- name: Defender for Endpoint for US Government customers
20-
href: gov.md
21-
- name: Defender for Endpoint Plan 1
22-
items:
23-
- name: Overview of Defender for Endpoint Plan 1
24-
href: defender-endpoint-plan-1.md
25-
- name: Setup and configuration
26-
href: mde-p1-setup-configuration.md
27-
- name: Get started
28-
href: mde-plan1-getting-started.md
29-
- name: Minimum requirements
30-
href: minimum-requirements.md
31-
- name: Supported Defender for Endpoint capabilities by platform
32-
href: supported-capabilities-by-platform.md
33-
- name: Antivirus solution compatibility with Defender for Endpoint
34-
href: defender-compatibility.md
8+
items:
9+
- name: What is Microsoft Defender for Endpoint?
10+
items:
11+
- name: Defender for Endpoint on Windows
12+
href: microsoft-defender-endpoint.md
13+
- name: Defender for Endpoint on macOS
14+
href: microsoft-defender-endpoint-mac.md
15+
- name: Defender for Endpoint on Linux
16+
href: microsoft-defender-endpoint-linux.md
17+
- name: Defender for Endpoint on Android
18+
href: microsoft-defender-endpoint-android.md
19+
- name: Defender for Endpoint on iOS
20+
href: microsoft-defender-endpoint-ios.md
21+
- name: Defender for Endpoint for US Government customers
22+
href: gov.md
23+
- name: Supported Defender for Endpoint capabilities by platform
24+
href: supported-capabilities-by-platform.md
25+
- name: Antivirus solution compatibility with Defender for Endpoint
26+
href: defender-compatibility.md
27+
- name: Defender for Endpoint Plan 1
28+
items:
29+
- name: Overview of Defender for Endpoint Plan 1
30+
href: defender-endpoint-plan-1.md
31+
- name: Setup and configuration
32+
href: mde-p1-setup-configuration.md
33+
- name: Get started
34+
href: mde-plan1-getting-started.md
3535
- name: What's new in Defender for Endpoint
3636
href: whats-new-in-microsoft-defender-endpoint.md
3737
items:
@@ -176,6 +176,8 @@
176176
items:
177177
- name: Deploy Defender for Endpoint on macOS
178178
items:
179+
- name: Microsoft Defender for Endpoint Prerequisites on macOS
180+
href: microsoft-defender-endpoint-mac-prerequisites.md
179181
- name: Deployment with Microsoft Intune
180182
href: mac-install-with-intune.md
181183
- name: JAMF Pro-based deployment

defender-endpoint/attack-surface-reduction.md

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -5,8 +5,8 @@ ms.service: defender-endpoint
55
ms.subservice: asr
66
ms.localizationpriority: medium
77
audience: ITPro
8-
author: denisebmsft
9-
ms.author: deniseb
8+
author: emmwalshh
9+
ms.author: ewalsh
1010
ms.reviewer: sugamar
1111
manager: deniseb
1212
ms.custom: admindeeplinkDEFENDER
@@ -16,7 +16,7 @@ ms.collection:
1616
- tier2
1717
- mde-asr
1818
search.appverid: met150
19-
ms.date: 03/28/2025
19+
ms.date: 05/09/2025
2020
---
2121

2222
# Attack surface reduction rules overview
@@ -98,7 +98,7 @@ Also, make sure [Microsoft Defender Antivirus and anti-malware updates](/windows
9898
- Minimum platform release requirement: `4.18.2008.9`
9999
- Minimum engine release requirement: `1.1.17400.5`
100100

101-
For more information and to get your updates, see [Update for Microsoft Defender anti-malware platform](https://support.microsoft.com/help/4052623/update-for-microsoft-defender-antimalware-platform).
101+
For more information and to get your updates, see [Update for Microsoft Defender anti-malware platform](/defender-endpoint/microsoft-defender-antivirus-updates).
102102

103103
### Cases where warn mode isn't supported
104104

@@ -134,6 +134,8 @@ You can set attack surface reduction rules for devices that are running any of t
134134

135135
- Windows 10 Pro, [version 1709](/windows/whats-new/whats-new-windows-10-version-1709) or later
136136
- Windows 10 Enterprise, [version 1709](/windows/whats-new/whats-new-windows-10-version-1709) or later
137+
- Windows 11 Pro, version 21H2 or later
138+
- Windows 11 Enterprise, version 21H2 or later
137139
- Windows Server, [version 1803 (Semi-Annual Channel)](/windows-server/get-started/whats-new-in-windows-server-1803) or later
138140
- Windows Server 2025
139141
- [Windows Server 2022](/windows-server/get-started/whats-new-in-windows-server-2022)

defender-endpoint/behavioral-blocking-containment.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ ms.collection:
1515
- m365-security
1616
- tier2
1717
search.appverid: met150
18-
ms.date: 03/29/2025
18+
ms.date: 04/25/2025
1919
---
2020

2121
# Behavioral blocking and containment

defender-endpoint/client-behavioral-blocking.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ ms.collection:
1717
- m365-security
1818
- tier2
1919
search.appverid: met150
20-
ms.date: 07/22/2024
20+
ms.date: 04/25/2025
2121
---
2222

2323
# Client behavioral blocking

defender-endpoint/configure-cloud-block-timeout-period-microsoft-defender-antivirus.md

Lines changed: 14 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
2-
title: Configure the Microsoft Defender Antivirus cloud block timeout period
3-
description: You can configure how long Microsoft Defender Antivirus will block a file from running while waiting for a cloud determination.
2+
title: Configure the Microsoft Defender Antivirus cloud block time-out period
3+
description: You can configure how long Microsoft Defender Antivirus blocks a file from running while waiting for a cloud determination.
44
ms.service: defender-endpoint
55
ms.localizationpriority: medium
66
author: emmwalshh
@@ -18,7 +18,7 @@ ms.collection:
1818
search.appverid: met150
1919
---
2020

21-
# Configure the cloud block timeout period
21+
# Configure the cloud block time out period
2222

2323
**Applies to:**
2424
- [Microsoft Defender XDR](/defender-xdr)
@@ -33,15 +33,15 @@ search.appverid: met150
3333

3434
When Microsoft Defender Antivirus finds a suspicious file, it can prevent the file from running while it queries the [Microsoft Defender Antivirus cloud service](cloud-protection-microsoft-defender-antivirus.md).
3535

36-
The default period that the file is [blocked](configure-block-at-first-sight-microsoft-defender-antivirus.md) is 10 seconds. If you're a security administrator, you can specify more time to wait before the file is allowed to run. Extending the cloud block timeout period can help ensure there is enough time to receive a proper determination from the Microsoft Defender Antivirus cloud service.
36+
The default period that the file is [blocked](configure-block-at-first-sight-microsoft-defender-antivirus.md) is 10 seconds. If you're a security administrator, you can specify more time to wait before the file is allowed to run. Extending the cloud block time out period can help ensure there's enough time to receive a proper determination from the Microsoft Defender Antivirus cloud service.
3737

38-
## Prerequisites to use the extended cloud block timeout
38+
## Prerequisites to use the extended cloud block time out
3939

40-
[Block at first sight](configure-block-at-first-sight-microsoft-defender-antivirus.md) and its prerequisites must be enabled before you can specify an extended timeout period.
40+
[Block at first sight](configure-block-at-first-sight-microsoft-defender-antivirus.md) and its prerequisites must be enabled before you can specify an extended time out period.
4141

42-
## Specify the extended timeout period using Microsoft Defender for Endpoint Security settings management
42+
## Specify the extended time out period using Microsoft Defender for Endpoint Security settings management
4343

44-
To specify the cloud block timeout period with Microsoft Defender for Endpoint Security settings management:
44+
To specify the cloud block time out period with Microsoft Defender for Endpoint Security settings management:
4545

4646
1. Go to the Microsoft Defender for Endpoint portal ([https://security.microsoft.com](https://security.microsoft.com)) and sign in.
4747
2. Select **Endpoints** > **Configuration management** > **Endpoint security policies**.
@@ -50,29 +50,29 @@ To specify the cloud block timeout period with Microsoft Defender for Endpoint S
5050
5. Under **Select Template** choose: "Microsoft Defender Antivirus".
5151
6. Select **Create policy**.
5252
7. Enter a name and description and select **Next**.
53-
8. From the **Defender** dropdown go to **Cloud Extended Timeout** and toggle it on.
53+
8. From the Defender dropdown, go to **Cloud Extended Timeout** and toggle it on.
5454
9. Specify the extended time, in seconds, from 1 second to 50 seconds. Whatever you specify is added to the default 10 seconds.
5555
10. Select **Next** and **Save** to finish configuring your policy.
5656

57-
## Specify the extended timeout period using Microsoft Intune
57+
## Specify the extended time out period using Microsoft Intune
5858

59-
You can specify the cloud block timeout period with an [endpoint security policy in Microsoft Intune](/mem/intune/protect/endpoint-security-policy).
59+
You can specify the cloud block time out period with an [endpoint security policy in Microsoft Intune](/mem/intune/protect/endpoint-security-policy).
6060

6161
1. Go to the Intune admin center ([https://intune.microsoft.com/](https://intune.microsoft.com/)) and sign in.
6262

6363
2. Select **Endpoint security**, and then under **Manage**, choose **Antivirus**.
6464

6565
3. Select (or create) an antivirus policy.
6666

67-
4. In the **Configuration settings** section, scroll down to **Cloud Extended Timeout** and specify the timeout, in seconds, from 0 to 50 seconds. Whatever you specify is added to the default 10 seconds.
67+
4. In the **Configuration settings** section, scroll down to **Cloud Extended Timeout** and specify the time out, in seconds, from 0 to 50 seconds. Whatever you specify is added to the default 10 seconds.
6868

6969
5. (This step is optional) Make any other changes to your antivirus policy. (Need help? See [Settings for Microsoft Defender Antivirus policy in Microsoft Intune](/mem/intune/protect/antivirus-microsoft-defender-settings-windows).)
7070

7171
6. Choose **Next**, and finish configuring your policy.
7272

73-
## Specify the extended timeout period using Group Policy
73+
## Specify the extended time out period using Group Policy
7474

75-
You can use Group Policy to specify an extended timeout for cloud checks.
75+
You can use Group Policy to specify an extended time out for cloud checks.
7676

7777
1. On your Group Policy management computer, open the [Group Policy Management Console](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc731212(v=ws.11))
7878

defender-endpoint/configure-device-connectivity.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,8 @@
11
---
22
title: Onboarding devices using streamlined connectivity for Microsoft Defender for Endpoint
33
description: Learn how to use a streamlined domain or static IP ranges during onboarding when connecting devices to Microsoft Defender for Endpoint.
4-
author: denisebmsft
5-
ms.author: deniseb
4+
author: emmwalshh
5+
ms.author: ewalsh
66
manager: deniseb
77
ms.topic: how-to
88
ms.service: defender-endpoint

defender-endpoint/configure-proxy-internet.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -3,8 +3,8 @@ title: Configure your devices to connect to the Defender for Endpoint service us
33
description: Learn how to configure your devices to enable communication with the cloud service using a proxy.
44
search.appverid: met150
55
ms.service: defender-endpoint
6-
ms.author: deniseb
7-
author: denisebmsft
6+
ms.author: ewalsh
7+
author: emmwalshh
88
ms.localizationpriority: medium
99
manager: deniseb
1010
audience: ITPro
@@ -39,7 +39,7 @@ Depending on the operating system, the proxy to be used for Microsoft Defender f
3939

4040
- For Windows devices, see [Configure device proxy and Internet connectivity settings](configure-proxy-internet.md) (in this article).
4141
- For Linux devices, see [Configure Microsoft Defender for Endpoint on Linux for static proxy discovery](linux-static-proxy-configuration.md).
42-
- For macOS devices, see [Microsoft Defender for Endpoint on Mac](microsoft-defender-endpoint-mac.md#network-connections).
42+
- For macOS devices, see [Microsoft Defender for Endpoint on macOS](microsoft-defender-endpoint-mac-prerequisites.md#network-connectivity).
4343

4444
The Defender for Endpoint sensor requires Microsoft Windows HTTP (`WinHTTP`) to report sensor data and communicate with the Defender for Endpoint service. The embedded Defender for Endpoint sensor runs in system context using the `LocalSystem` account.
4545

0 commit comments

Comments
 (0)