The Microsoft Defender XDR connector for Microsoft Sentinel allows you to stream all Microsoft Defender XDR incidents, alerts, and advanced hunting events into Microsoft Sentinel. This connector keeps the incidents synchronized between both portals. Microsoft Defender XDR incidents include alerts, entities, and other relevant information from all the Microsoft Defender products and services. For more information, see Microsoft Defender XDR integration with Microsoft Sentinel.

The Defender XDR connector, especially its incident integration feature, is the foundation of the unified security operations platform. If you're onboarding Microsoft Sentinel to the Microsoft Defender portal, you must first enable this connector with incident integration.

[!INCLUDE unified-soc-preview]

Before you begin, you must have the appropriate licensing, access, and configured resources described in this section.

• You must have a valid license for Microsoft Defender XDR, as described in Microsoft Defender XDR prerequisites.
• Your user must have the Security Administrator role on the tenant you want to stream the logs from, or the equivalent permissions.
• You must have read and write permissions on your Microsoft Sentinel workspace.
• To make any changes to the connector settings, your account must be a member of the same Microsoft Entra tenant with which your Microsoft Sentinel workspace is associated.
• Install the solution for Microsoft Defender XDR from the Content Hub in Microsoft Sentinel. For more information, see Discover and manage Microsoft Sentinel out-of-the-box content.
• Grant access to Microsoft Sentinel as appropriate for your organization. For more information, see Roles and permissions in Microsoft Sentinel.

For on-premises Active Directory sync via Microsoft Defender for Identity:

• Your tenant must be onboarded to Microsoft Defender for Identity.
• You must have the Microsoft Defender for Identity sensor installed.

In Microsoft Sentinel, select Data connectors. Select Microsoft Defender XDR from the gallery and Open connector page.

The Configuration section has three parts:

1. Connect incidents and alerts enables the basic integration between Microsoft Defender XDR and Microsoft Sentinel, synchronizing incidents and their alerts between the two platforms.

2. Connect entities enables the integration of on-premises Active Directory user identities into Microsoft Sentinel through Microsoft Defender for Identity.

3. Connect events enables the collection of raw advanced hunting events from Defender components.

For more information, see Microsoft Defender XDR integration with Microsoft Sentinel.

To ingest and synchronize Microsoft Defender XDR incidents with all their alerts to your Microsoft Sentinel incidents queue, complete the following steps.

1. Mark the check box labeled Turn off all Microsoft incident creation rules for these products. Recommended, to avoid duplication of incidents. This check box doesn't appear once the Microsoft Defender XDR connector is connected.

2. Select the Connect incidents & alerts button.

3. Verify that Microsoft Sentinel is collecting Microsoft Defender XDR incident data. In Microsoft Sentinel Logs in the Azure portal, run the following statement in the query window:

      SecurityIncident
      |    where ProviderName == "Microsoft 365 Defender"

When you enable the Microsoft Defender XDR connector, any Microsoft Defender components’ connectors that were previously connected are automatically disconnected in the background. Although they continue to appear connected, no data flows through them.

Use Microsoft Defender for Identity to sync user entities from your on-premises Active Directory to Microsoft Sentinel.

1. Select the Go the UEBA configuration page link.

2. In the Entity behavior configuration page, if you didn't enable UEBA, then at the top of the page, move the toggle to On.

3. Mark the Active Directory (Preview) check box and select Apply.

   :::image type="content" source="media/connect-microsoft-365-defender/ueba-configuration-page.png" alt-text="Screenshot of UEBA configuration page for connecting user entities to Sentinel.":::

If you want to collect advanced hunting events from Microsoft Defender for Endpoint or Microsoft Defender for Office 365, the following types of events can be collected from their corresponding advanced hunting tables.

1. Mark the check boxes of the tables with the event types you wish to collect:

   Defender for Endpoint

   Table name	Events type
   DeviceInfo	Machine information, including OS information
   DeviceNetworkInfo	Network properties of devices, including physical adapters, IP and MAC addresses, as well as connected networks and domains
   DeviceProcessEvents	Process creation and related events
   DeviceNetworkEvents	Network connection and related events
   DeviceFileEvents	File creation, modification, and other file system events
   DeviceRegistryEvents	Creation and modification of registry entries
   DeviceLogonEvents	Sign-ins and other authentication events on devices
   DeviceImageLoadEvents	DLL loading events
   DeviceEvents	Multiple event types, including events triggered by security controls such as Windows Defender Antivirus and exploit protection
   DeviceFileCertificateInfo	Certificate information of signed files obtained from certificate verification events on endpoints

   Defender for Office 365

   Table name	Events type
   EmailAttachmentInfo	Information about files attached to emails
   EmailEvents	Microsoft 365 email events, including email delivery and blocking events
   EmailPostDeliveryEvents	Security events that occur post-delivery, after Microsoft 365 delivers the emails to the recipient mailbox
   EmailUrlInfo	Information about URLs on emails
   UrlClickEvents	Events involving URLs clicked, selected, or requested on Microsoft Defender for Office 365

   Defender for Identity

   Table name	Events type
   IdentityDirectoryEvents	Various identity-related events, like password changes, password expirations, and user principal name (UPN) changes, captured from an on-premises Active Directory domain controller Also includes system events on the domain controller
   IdentityLogonEvents	Authentication activities made through your on-premises Active Directory, as captured by Microsoft Defender for Identity Authentication activities related to Microsoft online services, as captured by Microsoft Defender for Cloud Apps
   IdentityQueryEvents	Information about queries performed against Active Directory objects such as users, groups, devices, and domains

   Defender for Cloud Apps

   Table name	Events type
   CloudAppEvents	Information about activities in various cloud apps and services covered by Microsoft Defender for Cloud Apps

   Defender alerts

   Table name	Events type
   AlertInfo	Alerts from Microsoft Defender for Endpoint, Microsoft Defender for Office 365, Microsoft Cloud App Security, and Microsoft Defender for Identity, including severity information and threat categorization
   AlertEvidence	Information about various entities - files, IP addresses, URLs, users, devices - associated with alerts from Microsoft Defender XDR components

   ---

2. Select Apply Changes.

To run a query in the advanced hunting tables in Log Analytics, enter the table name in the query window.

The data graph in the connector page indicates that you're ingesting data. Notice that it shows one line each for incidents, alerts, and events, and the events line is an aggregation of event volume across all enabled tables. After you enable the connector, use the following KQL queries to generate more specific graphs.

Use the following KQL query for a graph of the incoming Microsoft Defender XDR incidents:

let Now = now(); 
(range TimeGenerated from ago(14d) to Now-1d step 1d 
| extend Count = 0 
| union isfuzzy=true ( 
    SecurityIncident
    | where ProviderName == "Microsoft 365 Defender"
    | summarize Count = count() by bin_at(TimeGenerated, 1d, Now) 
) 
| summarize Count=max(Count) by bin_at(TimeGenerated, 1d, Now) 
| sort by TimeGenerated 
| project Value = iff(isnull(Count), 0, Count), Time = TimeGenerated, Legend = "Events") 
| render timechart 

Use the following KQL query to generate a graph of event volume for a single table (change the DeviceEvents table to the required table of your choosing):

let Now = now();
(range TimeGenerated from ago(14d) to Now-1d step 1d
| extend Count = 0
| union isfuzzy=true (
    DeviceEvents
    | summarize Count = count() by bin_at(TimeGenerated, 1d, Now)
)
| summarize Count=max(Count) by bin_at(TimeGenerated, 1d, Now)
| sort by TimeGenerated
| project Value = iff(isnull(Count), 0, Count), Time = TimeGenerated, Legend = "Events")
| render timechart

In this document, you learned how to integrate Microsoft Defender XDR incidents, alerts, and advanced hunting event data from Microsoft Defender services, into Microsoft Sentinel, by using the Microsoft Defender XDR connector.

To use Microsoft Sentinel integrated with Defender XDR in the unified security operations platform, see Connect Microsoft Sentinel to Microsoft Defender XDR.