Onboarding a fleet to Microsoft Defender for Endpoint seems trivial until you run into several operating systems, several management tools and an Intune connector that does not behave as expected. This article compares the onboarding methods, walks through the Microsoft Intune route step by step, flags the pitfalls reported in the field and provides a local check script to confirm that the device is actually onboarded.
Which onboarding method should you choose for your devices?
The choice depends on the operating system and on the tool that already manages your devices: if your Windows machines are enrolled in Intune, the EDR (Endpoint Detection and Response) policy is the natural route. The Defender portal wizard follows the same logic: you first choose the operating system, then the deployment method.
One navigation change is worth noting. The Microsoft Learn documentation now places the onboarding page under System > Settings > Endpoints > Device management > Onboarding. It offers a connectivity type of "Streamlined" or "Standard". For Windows, step 1 selects "Windows" (deployment tool) or a version group for a local script or another method.
The Defender deployment tool is sometimes presented as the preferred method. That claim needs nuance: if you already administer your devices with Intune, the EDR policy avoids introducing a second onboarding chain to monitor.
Onboarding Windows devices with an Intune EDR policy
The preconfigured policy is the shortest path: a few clicks and an immediate deployment to all targeted Windows devices. Before you begin, validate the prerequisites.
- Access to the Microsoft Intune admin center with the Endpoint Security Manager role or equivalent permissions
- Microsoft Defender for Endpoint connector configured under Tenant administration > Connectors and tokens
- Microsoft Intune connection enabled on the Defender portal side (System > Settings > Endpoints, general features)
- Defender for Endpoint connector status set to "Enabled" in Endpoint security
- No other policy (device configuration, custom EDR policy) already managing the same onboarding setting
Once these points are confirmed, create the policy.
In the Intune admin center, open Endpoint security > Endpoint detection and response > EDR onboarding status tab.
Select Deploy preconfigured policy. A flyout titled Create profile opens on the right.
Choose Windows for management by Intune, or Windows Config Manager for tenant attach. Under Profile, select Endpoint detection and response, then Create.
Enter a meaningful name (the description is optional), move to the next step, review the policy and then save. It deploys immediately to the relevant Windows devices and appears under EDR policies, Summary tab.
For finer control (specific device groups, custom scope tags), go through Create policy and build the profile manually. In that case, the Microsoft Learn documentation recommends the "Auto from connector" option once the service connection is in place.
Connector, policy conflicts and error 65000: the known pitfalls
Three situations explain most onboardings that fail: an inactive connector, competing policies and a missing "Auto from connector" option.
The Intune documentation specifies that a device configuration policy can also be used for onboarding, but that it does not manage devices in tenant attach. Stacking several policy types on the same onboarding setting causes conflicts: keep a single policy type per device population.
At the end of 2025, administrators reported on Microsoft Q&A that the "Auto from connector" option no longer appeared in custom EDR policies: only Onboard and Offboard remained, with error 65000 on some devices. The reported workarounds are to delete these custom policies and then use "Deploy preconfigured policy", or to manually paste the content of the MDM onboarding package downloaded from the Defender portal. These are community reports: the official documentation announces no removal.
The following table gathers the most common symptoms with a resolution lead. The first two rows rely on Microsoft documentation; the following ones on the reports cited above and on engineering reasoning to be validated on a pilot device.
The Defender deployment tool: when to step outside Intune
The Defender deployment tool (DefenderDT.exe) handles prerequisites, automates migrations from older solutions and removes the need for complex onboarding scripts or separate downloads. You launch it from the onboarding wizard by selecting "Windows" (deployment tool) in step 1.
It relies on an access key generated in the Defender portal. Packages expire between 1 day and 1 year; Microsoft recommends the shortest possible validity period, which limits exposure if a package leaks. The tool also covers passive mode on servers, non-persistent VDI and a pre-test via the -Precheck parameter.
Two constraints to remember. Packages are specific to a tenant: never reuse them from one tenant to another. And the tool's Linux support is still in preview; the documentation page consulted does not mention macOS.
According to Microsoft Learn, the deployment tool does not integrate with onboarding via Intune, Defender for Cloud or the other methods. For a fleet already managed by Intune, stay with the EDR policy; reserve DefenderDT for devices that Intune does not cover.
If you are also preparing to switch from another antivirus, see our article on risk-free migration between Microsoft Defender and Intune.
Implementation: checking the onboarding state of a Windows machine
The portal confirms onboarding on the cloud side; a local check confirms that the sensor is actually in place on the device. The script below reads the Sense service (the Defender for Endpoint sensor) and the OnboardingState registry value. These two elements come from common engineering experience and do not appear in the Microsoft Learn pages cited here: validate them on a pilot device already visible in the portal before rolling out more widely.
- Required module: none, PowerShell 5.1 or later is enough.
- Minimum permission: local read; to query remote machines, an account allowed to use Invoke-Command (WinRM) on those machines.
- Output: one object per machine (Sense service, OnboardingState value, Onboarded flag), exportable to CSV. The script is read-only.
1[CmdletBinding()]2param(3 # Postes à contrôler ; par défaut, la machine locale4 [string[]]$ComputerName = $env:COMPUTERNAME,5 # Chemin d'export CSV facultatif6 [string]$OutputPath7)8 9# Bloc exécuté sur chaque poste : lecture seule10$check = {11 $statusKey = 'HKLM:\SOFTWARE\Microsoft\Windows Advanced Threat Protection\Status'12 $service = Get-Service -Name 'Sense' -ErrorAction SilentlyContinue13 $state = Get-ItemProperty -Path $statusKey -Name 'OnboardingState' -ErrorAction SilentlyContinue14 15 [pscustomobject]@{16 Poste = $env:COMPUTERNAME17 ServiceSense = if ($service) { [string]$service.Status } else { 'Absent' }18 OnboardingState = if ($state) { $state.OnboardingState } else { 'Non défini' }19 Onboarded = [bool]($state -and $state.OnboardingState -eq 1)20 }21}22 23# Exécution locale ou distante selon le paramètre24if ($ComputerName.Count -eq 1 -and $ComputerName[0] -eq $env:COMPUTERNAME) {25 $results = & $check26}27else {28 $results = Invoke-Command -ComputerName $ComputerName -ScriptBlock $check |29 Select-Object -Property Poste, ServiceSense, OnboardingState, Onboarded30}31 32$results | Format-Table -AutoSize33 34# Export facultatif35if ($OutputPath) {36 $results | Export-Csv -Path $OutputPath -NoTypeInformation -Encoding UTF837 Write-Host ('Résultats exportés vers ' + $OutputPath)38}A correctly onboarded machine shows a running Sense service and Onboarded set to True. A missing service or an undefined value indicates that the policy did not apply: go back to the troubleshooting table. Before a deployment with the deployment tool, DefenderDT.exe with -Precheck plays a comparable upstream checking role.
Verifying in the Defender portal: timing and filters
The delay before a newly onboarded device appears is 15 to 30 minutes according to the Intune and Defender documentation (5 to 20 minutes for Linux). After that delay, a missing device warrants investigation, not a wait of several hours.
To verify:
- Open the device inventory from the assets pane (Devices).
- Add a filter on the onboarding status and choose "Onboarded".
- On the Intune side, follow progress in the EDR onboarding status tab.
For a mass deployment, the onboarding documentation recommends a ring-based approach: 50 devices, then 50 to 100, then the rest of the fleet. It is the safest way to detect a policy conflict before it affects everyone. Our guide on making use of the Microsoft Intune licences you already own helps you check what your licences cover before planning the rings.
Frequently asked questions
Should you use the Defender deployment tool or Intune?
If your Windows devices are already managed by Intune, the EDR policy is consistent with your administration chain. The DefenderDT tool is a separate method that does not integrate with onboarding via Intune; it suits devices that Intune does not cover or scenarios such as passive mode on servers.
How long does it take for an onboarded device to appear?
The Microsoft documentation indicates 15 to 30 minutes for a Windows device, and 5 to 20 minutes for Linux. Beyond that, check the connector, the Intune connection on the Defender side and any policy conflicts.
Is the local onboarding script suitable for production?
No. It is limited to 10 devices and reserved for evaluations. In production, favour an Intune EDR policy, Configuration Manager or the Defender deployment tool.
Can you reuse an onboarding package between two tenants?
No. Deployment tool packages are specific to a tenant and must not be reused from one tenant to another.
Where to start: three checks before deploying
Start with the connector: as long as the Intune connection is not active on both sides, no policy will produce a reliable result. Then deploy to a pilot ring and check the result in the portal and with the local script.
- Confirm the Defender for Endpoint connector (Intune) and the Microsoft Intune connection (Defender)
- Create the preconfigured EDR policy and target it at a first ring of about 50 devices
- After 15 to 30 minutes, check the "Onboarded" filter in the device inventory
- Remove competing policies on the same onboarding setting
- Gradually extend to the following rings
If your organisation manages an Intune tenant linked to a Microsoft Entra ID tenant other than the Defender one, go through manual onboarding with the downloaded package. For enrolling the machines themselves, see our guide Intune and Windows 11: enrolment and configuration from A to Z, and for an overview of the platform, Microsoft Defender: a complete security platform for IT administrators.
Going further
- Deploy Windows devices by using the Microsoft Defender deployment tool: parameters, access key, package expiry and GPO deployment.
- Deploy endpoint detection and response policy with Intune: EDR policies, Auto from connector or manual mode, onboarding status report.
- Configure Microsoft Defender for Endpoint with Intune and onboard devices: prerequisites, roles and steps to connect Intune to Defender.
- Onboard devices to Microsoft Defender for Endpoint: portal journey and ring-based deployment.



