Black Friday sale: an extra 40% off every course until Monday, November 30.New Year sale: an extra 30% off every course until Friday, January 1.Memorial Day sale: an extra 25% off every course until Monday, May 31.SysAdmin Day sale: an extra 25% off every course until Sunday, August 1.Back to School sale: an extra 25% off every course until Sunday, August 22.Labor Day sale: an extra 25% off every course until Monday, September 6.Black Friday sale: an extra 40% off every course until Monday, November 29.New Year sale: an extra 30% off every course until Saturday, January 1.Choose your certification →

Copyright (c) 2026 MindMesh Academy. All rights reserved. This content is proprietary and may not be reproduced or distributed without permission.

4.1.5. Microsoft Defender for Endpoint Integration and Onboarding

💡 First Principle: Prevention eventually misses something, so you need a sensor that watches behavior, a service that judges how risky the device has become, and a way to turn that judgment into an access decision within minutes. The integration is a chain of four links — connect, onboard, judge, enforce — and a missing link breaks everything after it without any error message.

Microsoft documents the workflow as four steps: create the service-to-service connection, onboard devices with Intune policy, create a compliance policy that sets a risk level, and create a Conditional Access policy that requires compliance.

Link 1: connect. In the Defender portal, go to System > Settings > Endpoints > General > Advanced features and turn on Intune connection. In Intune, Endpoint security > Microsoft Defender for Endpoint shows Connection status as Enabled or Unavailable; it can take up to 15 minutes to show Enabled. On the same Intune page, the toggles under Compliance policy evaluation (Android, iOS/iPadOS, Windows) let Defender risk data feed compliance for those platforms, and toggles under App protection policy evaluation do the same for app protection on Android and iOS/iPadOS.

Link 2: onboard. Once connected, Windows devices can receive an onboarding package automatically; macOS, Android and iOS/iPadOS need the Defender app deployed and configured. On Windows, onboarding is done with an Endpoint detection and response policy:

  • Quick setup: Endpoint security > Endpoint detection and response > EDR Onboarding Status > Deploy preconfigured policy, which assigns to All Devices.
  • Custom policy: set Microsoft Defender for Endpoint client configuration package type to Auto from connector (recommended) or Onboard, where you paste an onboarding package downloaded from the Defender portal. Use Onboard for environments without the service connection, multiple Defender tenants or strict change control.

Assign EDR onboarding to device groups for immediate deployment; user groups wait for a user to sign in. Onboarded devices appear in the Defender device inventory after 15–30 minutes, and the EDR Onboarding Status tab shows each device's Defender sensor state and Onboarding status. Keep the EDR policy's scope in mind: it onboards and configures telemetry, but it doesn't configure antivirus, firewall or ASR. Device configuration profiles can also onboard devices, but using both methods can conflict. To offboard, deploy an EDR policy with an Offboard package — which expires seven days after download — and know that offboarding disables the sensor without removing the client.

Link 3: judge. In a compliance policy, Microsoft Defender for Endpoint > Require the device to be at or under the machine risk score turns Defender's verdict into a compliance result on Windows, Android and iOS/iPadOS. Clear is the most secure (any threat makes the device noncompliant), Low allows only low-level threats, Medium allows low and medium, and High allows everything, so it effectively only reports. Microsoft recommends Low. For mobile apps, an app protection policy's Max allowed device threat level can block access or wipe app data based on the same signal, whether or not the device is enrolled.

Link 4: enforce. A Conditional Access policy targeting Exchange Online and SharePoint Online with Require device to be marked as compliant closes the loop. Microsoft recommends starting in Report-only for 24 hours, reviewing sign-in logs, then switching it on. Intune stopped creating "classic" Conditional Access policies for Defender in August 2023.

StepWhereWho (least privilege)
Connect servicesDefender portal Advanced features; Intune connector pageEntra Security Administrator in Defender; Endpoint Security Manager in Intune
Onboard devicesIntune Endpoint security > EDREndpoint Security Manager
Risk-based complianceIntune compliance policyEndpoint Security Manager
Enforce accessMicrosoft Entra Conditional AccessA separate Entra role, such as Conditional Access Administrator

Licensing. EDR onboarding needs Intune Plan 1 plus a Defender license: Defender for Endpoint Plan 1, a plan that includes Plan 2 such as Microsoft 365 E5, or Microsoft Defender XDR.

Unenrolled devices. Defender for Endpoint security settings management lets Intune endpoint security policies (antivirus, ASR rules, EDR, firewall) manage Defender on devices that aren't enrolled in Intune — Windows, Windows Server, macOS and Linux. Such devices get a synthetic Entra identity and show Managed by = MDE. Enrolled devices ignore these policies, and Azure Virtual Desktop and non-persistent VDI aren't supported.

Investigating and triaging. Investigation happens in the Defender portal. Alerts are individual detections; incidents group related alerts into one attack story with a timeline, affected assets and evidence, and you triage incidents by severity. Device response actions include Isolate device (network cut except to Defender; selective isolation can keep Outlook and Teams working), Run antivirus scan, automated investigation, live response, investigation package collection and Restrict app execution. Defender for Endpoint Plan 1 includes only the first two manual actions; the rest need Plan 2. Vulnerabilities found by Defender Vulnerability Management can come back to Intune as security tasks (Endpoint security > Security tasks), which you accept, remediate and complete.

⚠️ Exam Trap: "Set the machine risk score to High for maximum protection" is backwards. High is the least secure value: it allows devices at every threat level, so it only reports. Clear blocks any detected threat, and Microsoft recommends Low as the balance.

Reflection Question: Defender shows a laptop at high risk, but its user can still open Outlook on it. Walk the four links of the chain and name at least three places it could be broken.

See how it connects
Alvin Varughese
Written byAlvin Varughese
Founder•26 professional certifications earned