Protect devices · Topic 3 of 6
Defender for Endpoint Integration and Onboarding
MD-102 Defender for Endpoint: connect it to Intune, onboard devices with EDR policies, use device risk in compliance, and investigate threats and incidents.
- 5 min
- Connect both sides: Defender portal Advanced features (Intune connection) and the Intune connector under Tenant administration.
- Use an EDR policy with the onboarding package from the connector to onboard Windows devices.
- Machine risk score levels are Clear, Low, Medium and High, and noncompliant devices are blocked by Conditional Access.
What it is
Microsoft Defender for Endpoint is the endpoint detection and response service. Intune and Defender for Endpoint work together: Intune onboards devices and deploys security policies, and Defender reports each device's risk level, which Intune compliance and Conditional Access can act on. Analysts then investigate threats and triage incidents in the Defender portal.
How it works
Connecting Intune and Defender
Enable the connection once per tenant.
- In the Microsoft Defender portal, go to Settings, Endpoints, General, Advanced features, and turn on Microsoft Intune connection.
- In the Intune admin center, go to Tenant administration, Connectors and tokens, Microsoft Defender for Endpoint and connect. The status becomes Enabled (up to 15 minutes).
- Set the connector options, such as enabling compliance policy evaluation for the platforms you use (Windows, Android, iOS).
You need the Endpoint Security Manager role (or a custom role) in Intune, and the Security Administrator role in Entra ID or Defender. The integration needs a Defender for Endpoint subscription and Intune.
Onboarding devices
Onboard Windows devices with an Endpoint detection and response (EDR) policy under Endpoint security, Endpoint detection and response. Choose the onboarding package source: Auto from connector (recommended) takes the latest package from Defender, with no download. A preconfigured EDR Onboarding Status policy deploys with recommended settings once the connector is active. Alternatives are a local script, Group Policy or Configuration Manager, and for non enrolled devices security settings management can onboard devices without Intune enrollment.
An EDR policy also sets sample sharing, telemetry reporting frequency and, on some versions, device tags. Devices appear in the Defender device inventory after onboarding, and the EDR Onboarding Status tab shows whether each device has onboarded.
Mobile devices use the Microsoft Defender app (iOS, Android), deployed as an app and configured with an app configuration policy and, for MAM, an app protection policy.
Using device risk in compliance
A compliance policy has a Microsoft Defender for Endpoint section with Require the device to be at or under the machine risk score.
| Level | Meaning |
|---|---|
| Clear | No threats at all. The strictest |
| Low | Low level threats allowed. Intune's recommended balance |
| Medium | Medium or lower allowed |
| High | Allows all threat levels. Reports risk without making devices noncompliant |
Devices that exceed the level become noncompliant, and a Conditional Access policy that requires a compliant device then blocks them. Intune no longer creates classic Conditional Access policies for the connector, so delete any old ones. Windows devices must be Entra registered, enrolled in Intune and onboarded to Defender for this to work.
Investigating threats and triaging incidents
Analysts use the Microsoft Defender portal (security.microsoft.com).
- Incidents group related alerts into one story, and show the affected devices, users and a timeline.
- Device inventory and device page show alerts, the timeline, software inventory and vulnerabilities.
- Actions on a device include isolate device, run antivirus scan, collect investigation package and restrict app execution. Live response opens a remote shell.
- Automated investigation and remediation examines alerts and can fix them, subject to the device group's automation level.
- Triage means setting the status (New, In progress, Resolved), the classification (true or false positive) and assigning an owner.
- Threat and vulnerability management lists weaknesses. The Vulnerability Remediation Agent (covered later) can prioritise them, and Intune can remediate through security tasks.
Intune surfaces the same data in Endpoint security, Defender for Endpoint with the connection status and compliance evaluation toggles, and in Devices, Monitor.
A worked scenario
A company wants only low risk devices to reach SharePoint. The admin enables the connector in both portals, deploys an EDR policy that uses the connector's onboarding package, and adds Require the device to be at or under the machine risk score: Low to the Windows compliance policy. A Conditional Access policy requires a compliant device. When a laptop shows a medium alert, Intune marks it noncompliant, access is blocked, and a Defender analyst isolates it and resolves the incident.
What to remember for the exam
- Connect both sides: Defender portal Advanced features (Intune connection) and the Intune connector under Tenant administration.
- Use an EDR policy with the onboarding package from the connector to onboard Windows devices.
- Machine risk score levels are Clear, Low, Medium and High, and noncompliant devices are blocked by Conditional Access.
- Defender incidents group alerts. Triage sets status, classification and owner. Isolate device limits network access.
- Mobile devices use the Defender app with app configuration and app protection policies.
Intune does the onboarding and compliance. Defender does the detection and investigation.
How the exam asks about this
- "Onboard Intune managed Windows devices to Defender for Endpoint with no manual package." An EDR policy with the connector's package.
- "Block devices that have any medium or high threat." A compliance policy with machine risk score Low, plus Conditional Access.
- "Stop a compromised device talking to the network but keep it online for investigation." Isolate device in Defender.
- "The connector is not working." Check the Advanced features toggle and the roles.
Common mistakes
Enabling only one side of the connection. Both are required.
Setting the risk level to High and expecting blocking. High allows everything.
Forgetting Conditional Access. Compliance alone does not block.
Using Defender for Endpoint baselines on VDI. They are not recommended there.
Check yourself
Where do you connect Intune to Defender for Endpoint?
Tenant administration, Connectors and tokens, Microsoft Defender for Endpoint, and the Intune connection in Defender's Advanced features.
Which policy onboards Windows devices?
An endpoint detection and response (EDR) policy.
What does isolating a device do?
It limits the device's network connectivity while keeping it reachable for investigation.
Topic 3 of 6 in Protect devices
Test yourself on Protect devices
The full Microsoft MD-102 question bank has 658 questions, with timed practice exams and an explanation for every answer.
This study guide is independent and is not affiliated with, endorsed by, or sponsored by Microsoft. Vendor names, certification names and exam codes are trademarks of their respective owners and are used for identification only.