OnLink
When a laptop starts throwing security warnings, the ticket rarely names the laptop and the agent shouldn’t need the Defender portal to find it. OnLink syncs Microsoft Defender for Endpoint devices, incidents and alerts into JSM Assets, so every security ticket points at the exact device with its risk score, exposure level, open alerts and the incident they belong to.
Security alerts usually live outside the service desk. A requester writes “my laptop keeps showing warnings”, and the agent opens the Defender portal, searches by user and guesses between three devices. With devices and alerts in Assets, that context is on the ticket from the start.
An Assets field on the request form lists your real Defender devices by name, OS and device group.
Risk score, exposure level, health status, last IP and open alerts show on the incident without a portal trip.
Automation on a new high-severity Defender Incident creates one JSM incident, links every alert and affected device, and routes it to the security queue.
Link the Defender object to the Intune, Jamf or Entra ID device you already import, so security posture sits next to ownership and hardware.
The requester types part of a device name into an Assets field and picks the exact laptop. The agent sees its risk score, exposure level, health status and the two open Defender alerts, synced minutes ago by OnLink.

Three API calls become three Assets object types. Defender Device comes from GET /api/machines and is keyed on the Defender machine ID. Defender Incident comes from Microsoft Graph’s GET /security/incidents, keyed on the incident ID, with status, severity, classification and a link back to the Defender portal. Defender Alert comes from GET /api/alerts, keyed on the alert ID, with references to the device it hit and the incident it belongs to. Import devices, then incidents, then alerts so every reference resolves. If you already import Intune or Entra ID devices, link the Defender object to them by Entra device ID rather than creating a second record.
Setup comes down to three parts. The setup guide has every field, filter and mapping line.
On the app registration OnLink already uses, add the WindowsDefenderATP application permissions Machine.Read.All and Alert.Read.All, plus the Microsoft Graph permission SecurityIncident.Read.All, and grant admin consent. Same tenant ID, client ID and secret. Devices and alerts use the token scope https://api.securitycenter.microsoft.com/.default; incidents use your existing Graph connection.
OnLink calls /api/machines and /api/alerts, paging with $top and $skip (up to 10,000 records a call), and /security/incidents on Microsoft Graph, 50 records a page. Server-side $filter conditions mean only onboarded, active devices, open incidents or open High and Medium alerts land in Assets.
Key devices on the machine ID, incidents on the incident ID and alerts on the alert ID, map the fields you want, and reference the device and incident from each alert by machineId and incidentId. Schedule devices daily (Defender refreshes its full device report about once a day), incidents and alerts hourly.
Sample mapping for devices:
key:id=Machine ID
map:computerDnsName=Name
map:osPlatform=OS Platform
map:healthStatus=Health Status
map:onboardingStatus=Onboarding Status
map:riskScore=Risk Score
map:exposureLevel=Exposure Level
map:lastIpAddress=Last IP Address
map:rbacGroupName=Device Group
map:aadDeviceId=Entra Device ID
map:machineTags=Tags|arraySeparator=,
map:lastSeen=Last Seen
config:api=/api/machines
Start a free trial of OnLink on the Atlassian Marketplace.
No. Add the two WindowsDefenderATP application permissions and the Microsoft Graph permission SecurityIncident.Read.All to the registration OnLink already uses and grant admin consent. Tenant ID, client ID and secret stay the same.
Microsoft still issues Defender tokens for the legacy securitycenter audience. A token for any other scope, including Microsoft Graph, returns 403 Forbidden even though the calls go to api.security.microsoft.com.
Defender builds incidents in Defender XDR by grouping related alerts, and Microsoft exposes them through the Graph security API rather than the Defender for Endpoint API. OnLink reads them over the Graph connection you already use for Intune or Entra ID, and links each alert to its incident by incident ID.
Yes. List machines and List alerts are available on Defender for Business and Defender for Endpoint Plans 1 and 2.
Yes. The same connection serves /api/vulnerabilities, /api/software and /api/recommendations. Create another object type and import for each.
Your call. Without a filter they stay in Assets with a resolved status, plus a resolvedTime on alerts and a resolving comment on incidents, which is useful for audit. With status ne 'Resolved' on alerts and status eq 'active' or status eq 'inProgress' on incidents, only open items are imported.
Defender for Endpoint in Assets
Start a free trial of OnLink on the Atlassian Marketplace.
Your service desk shouldn’t need the Defender portal to know which laptop is affected, how exposed it is, or what alerts are open on it.
OnLink is Cloud Fortified and brings 100+ sources into JSM Assets: HR systems, identity providers, MDMs, cloud platforms, and now Microsoft Defender for Endpoint.
What you get with OnLink for Defender for Endpoint:
RELATED