Onboard Windows devices to Defender for Endpoint using Intune
Applies to:
- Microsoft Defender for Endpoint Plan 1
- Microsoft Defender for Endpoint Plan 2
- Microsoft 365 Defender
Want to experience Defender for Endpoint? Sign up for a free trial.
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.
For more information on using Defender for Endpoint CSP see, WindowsAdvancedThreatProtection CSP and WindowsAdvancedThreatProtection DDF file.
Before you begin
Devices must be enrolled with Intune as your Mobile Device Management (MDM) solution.
For more information on enabling MDM with Microsoft Intune, see Device enrollment (Microsoft Intune).
Onboard devices using Microsoft Intune
Check out the PDF or Visio to see the various paths in deploying Defender for Endpoint.
Follow the instructions from Intune.
For more information on using Defender for Endpoint CSP see, WindowsAdvancedThreatProtection CSP and WindowsAdvancedThreatProtection DDF file.
Note
- The Health Status for onboarded devices policy uses read-only properties and can't be remediated.
- Configuration of diagnostic data reporting frequency is only available for devices on Windows 10, version 1703.
- Onboarding to Defender for Endpoint will onboard the device to Data Loss Prevention (DLP), which is also a part of Microsoft 365 compliance.
Run a detection test to verify onboarding
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.
Offboard devices using Mobile Device Management tools
For security reasons, the package used to Offboard devices will expire 30 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.
Note
Onboarding and offboarding policies must not be deployed on the same device at the same time, otherwise this will cause unpredictable collisions.
Get the offboarding package from Microsoft 365 Defender portal:
In the navigation pane, select Settings > Endpoints > Device management > Offboarding.
Select Windows 10 or Windows 11 as the operating system.
In the Deployment method field, select Mobile Device Management / Microsoft Intune.
Click Download package, and save the .zip file.
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.
Use the Microsoft Intune custom configuration policy to deploy the following supported OMA-URI settings.
- OMA-URI: ./Device/Vendor/MSFT/WindowsAdvancedThreatProtection/Offboarding
- Date type: String
- Value: [Copy and paste the value from the content of the WindowsDefenderATP_valid_until_YYYY-MM-DD.offboarding file]
For more information on Microsoft Intune policy settings, see Windows 10 policy settings in Microsoft Intune.
Note
The Health Status for offboarded devices policy uses read-only properties and can't be remediated.
Important
Offboarding causes the device to stop sending sensor data to the portal but data from the device, including reference to any alerts it has had will be retained for up to 6 months.
Related topics
- Onboard Windows devices using Group Policy
- Onboard Windows devices using Microsoft Endpoint Configuration Manager
- Onboard Windows devices using a local script
- Onboard non-persistent virtual desktop infrastructure (VDI) devices
- Run a detection test on a newly onboarded Microsoft Defender for Endpoint device
- Troubleshoot Microsoft Defender for Endpoint onboarding issues
Feedback
Submit and view feedback for