Skip to content

Commit 375ede2

Browse files
authored
Merge pull request #1769 from gigicroitoru/patch-1
Update configure-endpoints-mdm.md
2 parents b7cf34d + 2e50873 commit 375ede2

File tree

1 file changed

+11
-20
lines changed

1 file changed

+11
-20
lines changed

defender-endpoint/configure-endpoints-mdm.md

Lines changed: 11 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ ms.custom: admindeeplinkDEFENDER
1414
ms.topic: conceptual
1515
ms.subservice: onboard
1616
search.appverid: met150
17-
ms.date: 08/12/2024
17+
ms.date: 10/31/2024
1818
---
1919

2020
# Onboard Windows devices to Defender for Endpoint using Intune
@@ -47,7 +47,6 @@ Follow the instructions from [Intune](/mem/intune/protect/advanced-threat-protec
4747
For more information on using Defender for Endpoint CSP, see, [WindowsAdvancedThreatProtection CSP](https://msdn.microsoft.com/library/windows/hardware/mt723296(v=vs.85).aspx) and [WindowsAdvancedThreatProtection DDF file](https://msdn.microsoft.com/library/windows/hardware/mt723297(v=vs.85).aspx).
4848

4949
> [!NOTE]
50-
>
5150
> - The **Health Status for onboarded devices** policy uses read-only properties and can't be remediated.
5251
> - Configuration of diagnostic data reporting frequency is only available for devices on Windows 10, version 1703.
5352
> - Onboarding to Defender for Endpoint will onboard the device to [Data Loss Prevention (DLP)](/Microsoft-365/compliance/endpoint-dlp-learn-about), which is also a part of Microsoft 365 compliance.
@@ -57,13 +56,12 @@ For more information on using Defender for Endpoint CSP, see, [WindowsAdvancedTh
5756

5857
After onboarding the device, you can choose to run a detection test to verify that a device is properly onboarded to the service. For more information, see [Run a detection test on a newly onboarded Microsoft Defender for Endpoint device](run-detection-test.md).
5958

60-
6159
## Offboard devices using Mobile Device Management tools
6260

63-
For security reasons, the package used to Offboard devices will expire 7 days after the date it was downloaded. Expired offboarding packages sent to a device will be rejected. When downloading an offboarding package you'll be notified of the packages expiry date and it will also be included in the package name.
61+
For security reasons, the package used to Offboard devices expires seven days after the date it was downloaded. Expired offboarding packages sent to a device are rejected. When downloading an offboarding package, you're notified of the package's expiry date, and the date is included in the package name.
6462

6563
> [!NOTE]
66-
> Onboarding and offboarding policies must not be deployed on the same device at the same time, otherwise this will cause unpredictable collisions.
64+
> To avoid unpredictable policy collisions, onboarding and offboarding policies must not be deployed at the same time on a device.
6765
6866
1. Get the offboarding package from the [Microsoft Defender portal](https://security.microsoft.com) as follows:
6967

@@ -73,25 +71,18 @@ For security reasons, the package used to Offboard devices will expire 7 days af
7371

7472
3. In the **Deployment method** field, select **Mobile Device Management / Microsoft Intune**.
7573

76-
4. Click **Download package**, and save the .zip file.
74+
4. Select **Download package**, and save the .zip file.
7775

78-
2. Extract the contents of the .zip file to a shared, read-only location that can be accessed by the network administrators who will deploy the package. You should have a file named `WindowsDefenderATP_valid_until_YYYY-MM-DD.offboarding`.
76+
2. Extract the contents of the `.zip` file to a shared, read-only location that can be accessed by the network administrators who'll deploy the package. You should have a file named `WindowsDefenderATP_valid_until_YYYY-MM-DD.offboarding`.
7977

80-
3. In Microsoft Intune admin center, create a custom configuration policy.
78+
3. In the [Microsoft Intune admin center](https://intune.microsoft.com), you can use a custom configuration policy or an EDR policy.
8179

82-
1. In the navigation pane, select **Devices** \> **By platform** \> **Windows** \> **Manage Devices** \> **Configuration**.
83-
2. Under **Policies** click **Create** \> **New Policy**.
84-
3. In the **Create a profile** slide out, select **Windows 10 and later** as **Platform** and **Templates** as **Profile Type**.
85-
4. Under **Template Name**, click the **Custom** template and click **Create**.
86-
5. Enter a value for **Name** and click **Next**.
87-
6. Under **Configuration settings**, click **Add** and use the following OMA-URI settings.
88-
- Name: Provide a name
89-
- OMA-URI: `./Device/Vendor/MSFT/WindowsAdvancedThreatProtection/Offboarding`
90-
- Date type: String
91-
- Value: *Copy and paste the value from the content of the WindowsDefenderATP_valid_until_YYYY-MM-DD.offboarding file*
92-
7. Make the appropriate group assignments, applicability rules, and on the **Review + create** step, click the **Create** button to finish the policy.
80+
| Method | Procedure |
81+
|---|---|
82+
| Custom configuration policy | 1. In the navigation pane, select **Devices** \> **By platform** \> **Windows** \> **Manage Devices** \> **Configuration**. <br/><br/>2. Under **Policies** select **Create** \> **New Policy**.<br/><br/>3. In the **Create a profile** slide out, select **Windows 10 and later** as **Platform** and **Templates** as **Profile Type**.<br/><br/>4. Under **Template Name**, select the **Custom** template and select **Create**.<br/><br/>5. Enter a value for **Name** and select **Next**. <br/><br/>6. Under **Configuration settings**, select **Add** and use the following OMA-URI settings: <br/>- Name: Provide a name <br/>- OMA-URI: `./Device/Vendor/MSFT/WindowsAdvancedThreatProtection/Offboarding` <br/> - Date type: String<br/>- Value: Copy and paste the value from the content of the `WindowsDefenderATP_valid_until_YYYY-MM-DD` offboarding file. <br/><br/>7. Make the appropriate group assignments, applicability rules, and on the **Review + create** step, select **Create**. |
83+
| EDR policy | 1. In the navigation pane, select **Endpoint security** \> **Manage** \> **Endpoint detection and response**.<br/><br/>2. Under **Endpoint detection and response (EDR) policies**, select **Create policy**.<br/><br/>3. In the **Create a profile** slide out, select **Windows** as **Platform** and **Endpoint detection and response** and select **Create**.<br/><br/>5. Enter a value for **Name** and select **Next**. <br/><br/>6. Under **Configuration settings**, select **Offboard** for the setting **Microsoft Defender for Endpoint client configuration package type**.<br/><br/>7. Copy the value from the content of the `WindowsDefenderATP_valid_until_YYYY-MM-DD` offboarding file and paste it in the **Offboarding (Device)** setting. Then select **Next**.<br/><br/>8. Specify any scope tags if needed, make the appropriate group assignments and on the **Review + create** step, select **Create**. |
9384

94-
For more information on Microsoft Intune policy settings, see [Windows 10 policy settings in Microsoft Intune](/mem/intune/configuration/custom-settings-windows-10).
85+
For more information on Microsoft Intune policy settings, see [Windows 10 policy settings in Microsoft Intune](/mem/intune/configuration/custom-settings-windows-10).
9586

9687
> [!NOTE]
9788
> The **Health Status for offboarded devices** policy uses read-only properties and can't be remediated.

0 commit comments

Comments
 (0)