Optimize Microsoft Defender XDR data ingestion

When Microsoft Defender XDR data is available directly in Advanced Hunting, you can update Microsoft Sentinel content to use the corresponding Advanced Hunting tables and then stop duplicate ingestion of that data into Microsoft Sentinel.

Update your content one table at a time. When the content for all tables is updated and validated, stop ingestion for the supported Microsoft Defender XDR tables in the workspace at the same time.

Important

You can't stop ingestion for a single table. Configure workspace stops ingesting data into Log Analytics for the supported Defender XDR tables in the workspace at the same time, except tables with analytics retention set to 180 days or more, which stay ingested. Don't select it until you've updated and validated all content that depends on any of these tables. Otherwise, detections, workbooks, queries, and automation can stop receiving the data they require.

Prerequisites

Before you begin, make sure that:

  • Your tenant is eligible for ISOC.

  • You have an existing Microsoft Sentinel workspace that ingests Microsoft Defender XDR data that is also available through Advanced Hunting.

  • You have access to the Microsoft Defender portal and Advanced Hunting.

  • You have permissions to review and update the Microsoft Sentinel and Microsoft Defender content that depends on the tables you're optimizing.

  • You have identified the queries, analytics rules, workbooks, Logic App playbooks, reports, and other content that depend on each table you plan to transition.

For information about updating access when moving from workspace-based data to Microsoft Defender XDR data, see Update permissions and roles with Unified RBAC.

Prepare dependent content

Before you stop ingestion, update content that currently queries the Microsoft Sentinel table so that it can use the corresponding Advanced Hunting data.

Use the following sequence:

Area Action
Queries and other KQL content Update queries to use the corresponding Advanced Hunting tables and schema.
Permissions and roles Make sure users and automation identities have access to the required Microsoft Defender workloads.
Analytics rules Recreate applicable Microsoft Sentinel analytics rules as Microsoft Defender custom detections.
Workbooks Update workbook queries to use the Advanced Hunting data source.
Logic App playbooks Replace Log Analytics query actions with queries to the Microsoft Graph Advanced Hunting API where applicable.
Ingestion Stop ingestion for the supported Defender XDR tables only after the content for all tables is updated and validated.

For detailed migration guidance, see:

Validate content before you stop ingestion

For each table, validate all dependent content before you stop ingestion.

Make sure that:

  • Detections: Every analytics rule that queries the table has an equivalent custom detection running against Advanced Hunting data.

  • Workbooks: Every workbook that uses the table has been updated to use the Advanced Hunting data source and renders correctly for its intended users.

  • Automation: Every Logic App playbook that queries the table has been updated to use the Microsoft Graph Advanced Hunting API where required and has passed an end-to-end test.

  • Access: Users, groups, and automation identities that require the data have access to the corresponding Microsoft Defender workload.

  • Queries and reports: Queries, saved hunts, scheduled reports, and other content that previously referenced the Microsoft Sentinel table return the expected results against Advanced Hunting.

  • Deployment: If you use CI/CD or repeatable deployment definitions, make sure they deploy the updated custom detections and Advanced Hunting-based content.

Validate dependencies before you stop ingestion. In particular, validate detections, workbooks, automation, and access for every table.

Stop ingestion for the supported Defender XDR tables

If you use data collection rules (DCRs) on these tables, check them first. To keep a DCR working on a table, set that table's retention to 180 days or more before you select Configure workspace. For more information, see Check data collection rules and transformations before you stop ingestion.

After you complete all Lower Defender data costs recommendations and validate all dependent content:

  1. In the Microsoft Defender portal, go to Setup & configuration > Data management > Data & connectors.

  2. Select the Tables tab.

  3. Select Configure workspace.

This stops ingesting Defender XDR data into Log Analytics for the supported Defender XDR tables in the workspace. This is what lowers your costs.

Validate after you stop ingestion

After you stop ingestion, confirm that ingestion changed as expected and that your security operations content continues to work.

Monitor the updated configuration over several detection and automation runs.

Verify that:

  • Custom detections continue to return the expected results from Advanced Hunting data.

  • Hunting queries and other KQL content return the expected results.

  • Workbook tiles render correctly for their intended users.

  • Logic App playbooks continue to trigger and complete successfully.

  • Users and automation identities retain access to the required data.

If content doesn't behave as expected, review its Advanced Hunting table mapping, schema, permissions, and query configuration.

Update content table by table

You don't need to update the content for every Microsoft Defender XDR table at the same time. For each table:

  1. Identify the content that depends on the table.

  2. Update the dependent content to use Advanced Hunting.

  3. Validate queries, detections, workbooks, automation, and access.

  4. Set the recommendation status to Completed.

  5. Continue with the next table.

After all tables are complete, stop ingestion for the supported Defender XDR tables.