Skip to content

Commit 71d20df

Browse files
authored
Merge branch 'main' into docs-editor/android-whatsnew-1763444189
2 parents edb611b + 3f18557 commit 71d20df

File tree

93 files changed

+1670
-174
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

93 files changed

+1670
-174
lines changed

.openpublishing.redirection.defender-endpoint.json

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -20,11 +20,6 @@
2020
"redirect_url": "/defender-endpoint/evaluate-mdav-using-gp",
2121
"redirect_document_id": false
2222
},
23-
{
24-
"source_path": "defender-endpoint/linux-install-with-activator.md",
25-
"redirect_url": "/defender-endpoint/linux-custom-location-installation",
26-
"redirect_document_id": false
27-
},
2823
{
2924
"source_path": "defender-endpoint/preview.md",
3025
"redirect_url": "/defender-xdr/preview",
@@ -155,6 +150,11 @@
155150
"redirect_url": "/defender-endpoint/onboard-server",
156151
"redirect_document_id": false
157152
},
153+
{
154+
"source_path": "defender-endpoint/linux-install-with-activator.md",
155+
"redirect_url": "/defender-endpoint/linux-install-with-defender-deployment-tool",
156+
"redirect_document_id": false
157+
},
158158
{
159159
"source_path": "defender-endpoint/mde-linux-arm.md",
160160
"redirect_url": "/defender-endpoint/microsoft-defender-endpoint-linux",

defender-endpoint/TOC.yml

Lines changed: 16 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -135,6 +135,8 @@
135135
href: streamlined-device-connectivity-urls-gov.md
136136
- name: Onboard client devices
137137
items:
138+
- name: Onboard Windows devices using the Defender deployment tool
139+
href: defender-deployment-tool-windows.md
138140
- name: Onboard client devices running Windows or macOS
139141
href: onboard-client.md
140142
- name: Defender for Endpoint plug-in for WSL
@@ -174,6 +176,7 @@
174176
href: mde-linux-deployment-on-sap.md
175177
- name: Use custom detection rules to protect SAPXPG
176178
href: mde-sap-custom-detection-rules.md
179+
177180
- name: Defender for Endpoint on macOS
178181
items:
179182
- name: Deploy Defender for Endpoint on macOS
@@ -267,6 +270,8 @@
267270
items:
268271
- name: Enabling deployment to a custom location
269272
href: linux-custom-location-installation.md
273+
- name: Deployment tool based deployment
274+
href: linux-install-with-defender-deployment-tool.md
270275
- name: Installer script based deployment
271276
href: linux-installer-script.md
272277
- name: Ansible based deployment
@@ -625,6 +630,12 @@
625630
href: exclude-devices.md
626631
- name: Identifying transient devices
627632
href: transient-device-tagging.md
633+
- name: Collect custom device data
634+
items:
635+
- name: Overview
636+
href: custom-data-collection.md
637+
- name: Create custom data collection rules
638+
href: create-custom-data-collection-rules.md
628639
- name: Internet facing devices
629640
href: internet-facing-devices.md
630641
- name: Device timeline
@@ -1062,6 +1073,10 @@
10621073
href: respond-machine-alerts.md#contain-devices-from-the-network
10631074
- name: Contain user from the network
10641075
href: respond-machine-alerts.md#contain-user-from-the-network
1076+
- name: Automatically apply GPO hardening (predictive shielding)
1077+
href: respond-machine-alerts.md#gpo-hardening
1078+
- name: Automatically apply Safeboot hardening (predictive shielding)
1079+
href: respond-machine-alerts.md#safeboot-hardening
10651080
- name: Consult a threat expert
10661081
href: respond-machine-alerts.md#consult-a-threat-expert
10671082
- name: Check activity details in Action center
@@ -1098,10 +1113,7 @@
10981113
href: live-response-command-examples.md
10991114

11001115
- name: Use sensitivity labels to prioritize incident response
1101-
href: information-protection-investigation.md
1102-
1103-
- name: Advanced hunting
1104-
href: /defender-xdr/advanced-hunting-overview?toc=/defender-endpoint/toc.json&bc=/defender-endpoint/breadcrumb/toc.json
1116+
href: information-protection-investigation.md
11051117

11061118
- name: Threat analytics
11071119
items:

defender-endpoint/configure-endpoints-gp.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2,8 +2,8 @@
22
title: Onboard Windows Servers to Microsoft Defender for Endpoint via Group Policy
33
description: Use Group Policy to deploy the configuration package on Windows devices so that they're onboarded to the service.
44
ms.service: defender-endpoint
5-
ms.author: bagol
6-
author: batamig
5+
ms.author: painbar
6+
author: paulinbar
77
ms.localizationpriority: medium
88
manager: bagol
99
audience: ITPro
@@ -12,7 +12,7 @@ ms.collection:
1212
- tier1
1313
ms.custom: admindeeplinkDEFENDER
1414
ms.topic: install-set-up-deploy
15-
ms.date: 10/13/2025
15+
ms.date: 11/17/2025
1616
ms.subservice: onboard
1717
search.appverid: met150
1818
appliesto:
@@ -23,6 +23,8 @@ appliesto:
2323

2424
# Onboard Windows devices using Group Policy
2525

26+
[!INCLUDE [Microsoft Defender deployment tool preview](./includes/defender-deployment-tool-preview.md)]
27+
2628
## Prerequisites
2729

2830
- To use Group Policy (GP) updates to deploy the package, you must be on Windows Server 2008 R2 or later.

defender-endpoint/configure-endpoints-mdm.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2,8 +2,8 @@
22
title: Onboard Windows devices to Defender for Endpoint using Intune
33
description: Use Microsoft Intune to deploy the configuration package on devices so that they're onboarded to the Defender for Endpoint service.
44
ms.service: defender-endpoint
5-
ms.author: bagol
6-
author: batamig
5+
ms.author: painbar
6+
author: paulinbar
77
ms.localizationpriority: medium
88
manager: bagol
99
audience: ITPro
@@ -14,14 +14,15 @@ ms.custom: admindeeplinkDEFENDER
1414
ms.topic: install-set-up-deploy
1515
ms.subservice: onboard
1616
search.appverid: met150
17-
ms.date: 10/31/2024
17+
ms.date: 11/17/2025
1818
appliesto:
1919
- Microsoft Defender for Endpoint Plan 1
2020
- Microsoft Defender for Endpoint Plan 2
2121

2222
---
2323
# Onboard Windows devices to Defender for Endpoint using Intune
2424

25+
[!INCLUDE [Microsoft Defender deployment tool preview](./includes/defender-deployment-tool-preview.md)]
2526

2627
You can use mobile device management (MDM) solutions to configure Windows 10 devices. Defender for Endpoint supports MDMs by providing OMA-URIs to create policies to manage devices.
2728

defender-endpoint/configure-endpoints-sccm.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -12,14 +12,13 @@ ms.collection:
1212
- tier1
1313
ms.custom: admindeeplinkDEFENDER
1414
ms.topic: install-set-up-deploy
15-
ms.date: 10/27/2025
15+
ms.date: 11/17/2025
1616
ms.subservice: onboard
1717
search.appverid: met150
1818
---
1919

2020
# Onboard Windows devices using Configuration Manager
2121

22-
2322
You can use Configuration Manager to onboard endpoints to the Microsoft Defender for Endpoint service.
2423

2524
There are several options you can use to onboard devices using Configuration Manager:
@@ -32,6 +31,7 @@ There are several options you can use to onboard devices using Configuration Man
3231
3332
You can create a detection rule on a Configuration Manager application to continuously check if a device has been onboarded. An application is a different type of object than a package and program. If a device is not yet onboarded (due to pending OOBE completion or any other reason), Configuration Manager reattempts to onboard the device until the rule detects the status change. For more information, see [Configure Detection Methods in System Center 2012 R2 Configuration Manager](/previous-versions/system-center/system-center-2012-R2/gg682159\(v=technet.10\)#step-4-configure-detection-methods-to-indicate-the-presence-of-the-deployment-type).
3433

34+
[!INCLUDE [Microsoft Defender deployment tool preview](./includes/defender-deployment-tool-preview.md)]
3535

3636
## Prerequisites
3737

defender-endpoint/configure-endpoints-script.md

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -3,8 +3,8 @@ title: Onboard Windows Servers using a local script
33
description: Use a local script to deploy the configuration package on devices to enable onboarding of the devices to the service.
44
search.appverid: met150
55
ms.service: defender-endpoint
6-
ms.author: bagol
7-
author: batamig
6+
ms.author: painbar
7+
author: paulinbar
88
ms.reviewer: pahuijbr
99
ms.localizationpriority: medium
1010
manager: bagol
@@ -15,22 +15,23 @@ ms.collection:
1515
ms.custom: admindeeplinkDEFENDER
1616
ms.topic: install-set-up-deploy
1717
ms.subservice: onboard
18-
ms.date: 04/16/2025
18+
ms.date: 11/17/2025
1919
appliesto:
2020
- Microsoft Defender for Endpoint Plan 1
2121
- Microsoft Defender for Endpoint Plan 2
2222

2323
---
2424
# Onboard Windows devices using a local script
2525

26-
2726
You can also manually onboard individual devices to Defender for Endpoint. You might want to onboard some devices when you're testing the service before you commit to onboarding all devices in your network.
2827

2928
> [!IMPORTANT]
3029
> The script described in this article is recommended for manually onboarding devices to Defender for Endpoint. It should only be used on a limited number of devices. If you're deploying to a production environment, see [other deployment options](onboard-client.md), such as Intune, Group Policy, or Configuration Manager.
3130
3231
Check out [Identify Defender for Endpoint architecture and deployment method](deployment-strategy.md) to see the various paths in deploying Defender for Endpoint.
3332

33+
[!INCLUDE [Microsoft Defender deployment tool preview](./includes/defender-deployment-tool-preview.md)]
34+
3435
## Onboard devices
3536

3637
1. Open the configuration package .zip file (*WindowsDefenderATPOnboardingPackage.zip*) that you downloaded from the service onboarding wizard. You can also get the package from the [Microsoft Defender portal](https://security.microsoft.com):

defender-endpoint/configure-endpoints-vdi.md

Lines changed: 6 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -3,8 +3,8 @@ title: Onboard non-persistent virtual desktop infrastructure (VDI) devices
33
description: Deploy the configuration package on virtual desktop infrastructure (VDI) device so that they're onboarded to Microsoft Defender for Endpoint service.
44
search.appverid: met150
55
ms.service: defender-endpoint
6-
ms.author: bagol
7-
author: batamig
6+
ms.author: painbar
7+
author: paulinbar
88
ms.reviewer: pahuijbr; yonghree
99
ms.localizationpriority: medium
1010
manager: bagol
@@ -14,18 +14,15 @@ ms.collection:
1414
- tier2
1515
ms.custom: admindeeplinkDEFENDER
1616
ms.topic: install-set-up-deploy
17-
ms.date: 03/11/2025
17+
ms.date: 11/17/2025
1818
ms.subservice: onboard
1919
appliesto:
2020
- Microsoft Defender for Endpoint Plan 1
2121
- Microsoft Defender for Endpoint Plan 2
2222

2323
---
24-
# Onboard non-persistent virtual desktop infrastructure (VDI) devices in Microsoft Defender XDR
25-
26-
27-
2824

25+
# Onboard non-persistent virtual desktop infrastructure (VDI) devices in Microsoft Defender XDR
2926

3027
Virtual desktop infrastructure (VDI) is an IT infrastructure concept that lets end users access enterprise virtual desktops instances from almost any device (such as your personal computer, smartphone, or tablet), eliminating the need for organization to provide users with physical machines. Using VDI devices reduces costs, as IT departments are no longer responsible for managing, repairing, and replacing physical endpoints. Authorized users can access the same company servers, files, apps, and services from any approved device through a secure desktop client or browser.
3128

@@ -34,6 +31,8 @@ Like any other system in an IT environment, VDI devices should have an endpoint
3431
> [!NOTE]
3532
> **Persistent VDI's** - Onboarding a persistent VDI machine into Microsoft Defender for Endpoint is handled the same way you would onboard a physical machine, such as a desktop or laptop. Group policy, Microsoft Configuration Manager, and other methods can be used to onboard a persistent machine. In the Microsoft Defender portal, (https://security.microsoft.com) under onboarding, select your preferred onboarding method, and follow the instructions for that type. For more information, see [Onboarding Windows client](onboard-client.md).
3633
34+
[!INCLUDE [Microsoft Defender deployment tool preview](./includes/defender-deployment-tool-preview.md)]
35+
3736
## Onboarding non-persistent virtual desktop infrastructure (VDI) devices
3837

3938
Defender for Endpoint supports non-persistent VDI session onboarding. There might be associated challenges when onboarding VDI instances. The following are typical challenges for this scenario:
Lines changed: 115 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,115 @@
1+
---
2+
title: Create and manage custom data collection rules in Microsoft Defender for Endpoint
3+
description: Learn how to create and manage custom data collection rules in Microsoft Defender for Endpoint to enhance your threat hunting capabilities.
4+
ms.service: defender-endpoint
5+
f1.keywords:
6+
- NOCSH
7+
ms.author: lwainstein
8+
author: limwainstein
9+
ms.localizationpriority: medium
10+
manager: bagol
11+
audience: ITPro
12+
ms.collection:
13+
- m365-security
14+
- tier1
15+
- usx-security
16+
ms.topic: how-to
17+
search.appverid:
18+
- MOE150
19+
- MET150
20+
ms.date: 11/12/2025
21+
appliesto:
22+
- Microsoft Defender for Endpoint
23+
---
24+
25+
# Create and manage custom data collection rules in Microsoft Defender for Endpoint (Preview)
26+
27+
[!INCLUDE [Prerelease information](../includes/prerelease.md)]
28+
29+
[Custom data collection (Preview)](custom-data-collection.md) enables organizations to expand and customize telemetry collection beyond default configurations to support specialized threat hunting and security monitoring needs.
30+
31+
Custom data collection rules allow you to define specific events and analyze the data to enhance your security visibility and threat hunting operations. Custom data collection rules are based on tailored filters for event properties such as folder paths, process names, and network connections.
32+
33+
This article shows you how to create and manage custom data collection rules in the Microsoft Defender portal.
34+
35+
## Create custom data collection rules
36+
37+
### Prerequisites
38+
39+
To use custom data collection, check that you have the following prerequisites:
40+
41+
- A Microsoft Defender for Endpoint P2 license.
42+
- A connected [Microsoft Sentinel workspace](/azure/sentinel/quickstart-onboard): required for custom data storage and querying. You can currently only connect one Sentinel workspace per Defender for Endpoint tenant for custom data collection.
43+
- Dynamic tags configured in [Asset Rule Management](/defender-xdr/configure-asset-rules) for device targeting. To use a tag for custom data collection, the tag should be run at least once.
44+
45+
### Supported operating systems
46+
47+
- **Windows 10 and 11** with a minimum Defender for Endpoint client version of 10.8805.
48+
- Windows 10 requires enrollment in [Extended Security Updates (ESU) program](/windows/whats-new/extended-security-updates).
49+
50+
### Performance and limits
51+
52+
- Each collection rule can capture up to 25,000 events per device within a 24-hour rolling window. Once the device reaches the limit, telemetry for the specific rule on the specific device stops until the window resets.
53+
- If the device reaches the threshold early in the cycle, it can take up to 24 hours for telemetry to resume. For example, if the device reaches the limit one hour after the window resets, telemetry resumes after 23 hours.
54+
- If the device reaches the threshold near the end of the window, the delay is shorter. For example, if the device reaches the limit two hours before the window resets, telemetry resumes after two hours.
55+
- Rule deployment typically takes 20 minutes to one hour.
56+
- Custom collection operates alongside default Defender for Endpoint configuration without interference.
57+
58+
### Data costs
59+
60+
Custom data collection is included with Microsoft Defender for Endpoint P2 licensing. However, data ingestion into Microsoft Sentinel workspaces incurs charges based on your Sentinel billing arrangement.
61+
62+
### Create rules
63+
64+
1. In the Microsoft Defender portal, navigate to **Settings** > **Endpoints** > **Rules** > **Custom Data Collection**.
65+
66+
:::image type="content" source="media/custom-data-collection/custom-data-collection-main-view.png" alt-text="Screenshot of the main Custom Data Collection page." lightbox="media/custom-data-collection/custom-data-collection-main-view.png":::
67+
68+
1. To switch your Microsoft Sentinel workspace, select the workspace name on the top right, and select the workspace.
69+
1. Select **Create rule**. In the **General Information** section, type a rule name and description, and select **Next**.
70+
71+
:::image type="content" source="media/create-custom-data-collection-rules/create-custom-data-collection-rule-general.png" alt-text="Screenshot of creating a rule: General Information page." lightbox="media/create-custom-data-collection-rules/create-custom-data-collection-rule-general.png":::
72+
73+
1. In the **Create rule** section:
74+
75+
1. Select which table you want to collect data from. For more information, see [Supported event tables](custom-data-collection.md#supported-event-tables).
76+
1. Select the action for which you want to collect data.
77+
1. Add rule conditions to filter the data even further. You can add multiple conditions to refine the data collection. Rule conditions are based on the selected table. For more information, see the respective table link under [Supported event tables](custom-data-collection.md#supported-event-tables).
78+
79+
:::image type="content" source="media/create-custom-data-collection-rules/create-custom-data-collection-rule.png" alt-text="Screenshot of creating a rule: Create rule page." lightbox="media/create-custom-data-collection-rules/create-custom-data-collection-rule.png":::
80+
81+
1. Select **Next**.
82+
83+
1. In the **Define rule scope** section, select whether you want to collect data from all applicable client devices or from specific devices that include dynamic tags. For more information, see [Create dynamic rules for devices in asset rule management](/defender-xdr/configure-asset-rules).
84+
85+
:::image type="content" source="media/create-custom-data-collection-rules/create-custom-data-collection-rule-define-scope.png" alt-text="Screenshot of creating a rule: Define scope page." lightbox="media/create-custom-data-collection-rules/create-custom-data-collection-rule-define-scope.png":::
86+
87+
> [!NOTE]
88+
> Custom data collection only supports dynamic tags.
89+
90+
1. In the **Review and finish** section, review your rule settings, and select **Submit**.
91+
92+
:::image type="content" source="media/create-custom-data-collection-rules/create-custom-data-collection-rule-review.png" alt-text="Screenshot of creating a rule: Review and finish page." lightbox="media/create-custom-data-collection-rules/create-custom-data-collection-rule-review.png":::
93+
94+
It can take up to an hour for the rule to be deployed to the targeted devices.
95+
96+
## Monitor and troubleshoot
97+
98+
If rules aren't working as expected:
99+
100+
- Create a broad rule to collect events in an unexpected use case. For example, create a rule that collects all network events where `port not equals 0`.
101+
- Apply individual filters and tags to isolate issues.
102+
- If a device isn't responding after you enable the feature, reboot the device.
103+
104+
Review these considerations when monitoring and troubleshooting custom data collection rules:
105+
106+
- Endpoint detection and response (EDR) exclusions may override custom collection rules.
107+
- Dynamic tags update approximately every hour. Check the **Custom collection** > **Last run time** column for the status.
108+
109+
## Edit, delete, and enable or disable custom data collection rules
110+
111+
- To edit a rule, navigate to **Settings** > **Endpoints** > **Rules** > **Custom Collection**, select the rule you want to edit, and select **Edit**.
112+
- To disable or enable a rule, select the rule you want to modify, and select or clear the **Enable** check-box under the rule description. When you disable a rule,data collection for that rule stops on all targeted devices.
113+
- To delete a rule, select the rule you want to delete, and select **Delete**. When you delete a rule, the rule is permanently removed from the system.
114+
115+
[!INCLUDE [Microsoft Defender XDR rebranding](../includes/defender-m3d-techcommunity.md)]

0 commit comments

Comments
 (0)