Microsoft Sentinel
Hunting and detection

Update Microsoft Sentinel content to use Advanced Hunting tables | Microsoft Learn

In brief

The guidance identifies affected Defender XDR tables, column and data-type differences, and required updates for queries, detections, workbooks, and automation when transitioning Microsoft Sentinel content.

What Defender admins need to know

Administrators must update and validate dependent content before stopping ingestion for supported Defender XDR tables.

Summaries are generated from the documentation change itself.

Documentation change

The comparison below shows only the changed extract. Use the full-page view for complete context.

new file mode 100644

layout: Conceptual title: Update Microsoft Sentinel content to use Advanced Hunting tables | Microsoft Learn canonicalUrl: https://learn.microsoft.com/en-us/azure/sentinel/transition-advanced-hunting-tables breadcrumb_path: breadcrumb/toc.json feedback_help_link_url: https://learn.microsoft.com/answers/tags/423/microsoft-sentinel/ feedback_help_link_type: get-help-at-qna feedback_product_url: https://feedback.azure.com/d365community/forum/79b1327d-d925-ec11-b6e6-000d3a4f06a4 feedback_system: Standard learn_banner_products:


Update Microsoft Sentinel content to use Advanced Hunting tables | Microsoft Learn

When you transition Microsoft Sentinel content from workspace-based Microsoft Defender data to Microsoft Defender XDR Advanced Hunting data, review the queries and dependent content that use the affected tables.

Most Microsoft Defender tables have the same name in Microsoft Sentinel and Advanced Hunting, so table references usually don't change. However, some columns and data types work differently and require updates.

Important

Before you stop ingestion, update and validate all dependent queries, detections, workbooks, and automation for all Defender XDR tables. Configure workspace stops ingestion for the supported Defender XDR tables at the same time. If ingestion stops first, dependent content might reference data that is no longer arriving in the Microsoft Sentinel workspace.

For the full Advanced Hunting schema, see Understand the Advanced Hunting schema.

Summary of required updates by workload

The following sections group the affected tables by Microsoft Defender workload. Use the Update pattern column to identify the changes that apply to your content.

Microsoft Defender for Endpoint

Updates requiredTablesUpdate pattern
More content updatesDeviceInfoPattern 1 and Other column changes
More content updatesDeviceNetworkInfoPattern 2
Some content updatesDeviceEvents, DeviceFileEvents, DeviceProcessEvents, DeviceLogonEvents, DeviceNetworkEventsPattern 1
Minor content updatesDeviceFileCertificateInfo, DeviceImageLoadEvents, DeviceRegistryEventsChanges that apply to all tables
More content updatesDisruptionAndResponseEventsOther column changes

The MachineGroup column isn't consistently available or populated across Microsoft Defender XDR endpoint tables. Don't rely on MachineGroup for filtering or scoping outside DeviceInfo. If your queries, workbooks, analytics rules, or automation use this column, review and validate those implementations in Advanced Hunting before you stop ingestion.

Microsoft Defender for Office 365

Updates requiredTablesUpdate pattern
More content updatesEmailEventsPattern 1 and Other column changes
Minor content updatesEmailAttachmentInfo, EmailUrlInfo, UrlClickEventsChanges that apply to all tables
More content updatesEmailPostDeliveryEventsOther column changes
More content updatesMessageEvents, MessagePostDeliveryEvents, MessageUrlInfoMicrosoft Teams message tables
More content updatesCallActivityEvents, FileMaliciousContentInfoOther column changes
Minor content updatesCampaignInfoChanges that apply to all tables

Microsoft Teams message tables

In addition to the changes that apply to all tables, check these column differences:

TableMicrosoft SentinelAdvanced HuntingWhat to do
MessageEventsMessageSubject, MessageFormatType, MessageFormatSubtypeNot availableRemove these columns. Use Subject for the message subject.
MessageEventsLastEditedTime (string)LastEditedTime (datetime)For text comparisons, use tostring(LastEditedTime).
MessagePostDeliveryEventsDetectionMethods (string)DetectionMethods (dynamic)For text comparisons, use tostring(DetectionMethods).
MessageUrlInfoThreatTypesNot availableJoin with MessageEvents on TeamsMessageId to get the threat verdict.
MessageUrlInfoNot availableUrlLocationYou can use this new column.

This table reflects the schema that Advanced Hunting returns. Columns not listed work the same in both. If a column differs from the schema reference page, run <TableName> | getschema in Advanced Hunting to confirm.

For the full schemas, see MessageEvents, MessagePostDeliveryEvents, and MessageUrlInfo.

Microsoft Defender for Identity

Updates requiredTablesUpdate pattern
More content updatesIdentityLogonEvents, IdentityDirectoryEvents, IdentityQueryEventsPattern 3
Minor content updatesIdentityEventsChanges that apply to all tables

Microsoft Defender for Cloud Apps and Defender alerts

Updates requiredTablesUpdate pattern
More content updatesAlertEvidencePattern 1, Pattern 4, and Other column changes
Minor content updatesCloudAppEvents, AlertInfoChanges that apply to all tables
Minor content updatesOAuthAppInfoChanges that apply to all tables

Microsoft Defender for Cloud

Updates requiredTablesUpdate pattern
More content updatesCloudAuditEvents, CloudDnsEvents, CloudProcessEventsOther column changes

Note

Defender is still building up 90 days of history for Defender for Cloud tables. Until it does, Advanced Hunting might have less than 90 days of past data for these tables. If you need older data, keep it in Microsoft Sentinel until Advanced Hunting has the history you need.

Changes that apply to all tables

Review the following changes for every query, detection, workbook, and playbook that you update:

  • You don't have to replace TimeGenerated. When your Microsoft Sentinel workspace is connected to the Microsoft Defender portal, TimeGenerated in Advanced Hunting returns the same value as the table's event time column. In Microsoft Sentinel, TimeGenerated can differ slightly from the event time, so results that depend on exact time windows might not match exactly. For new queries, and for custom detections that run in near real time (Continuous (NRT) frequency), use Timestamp. CallActivityEvents doesn't have a Timestamp column. For that table, use ActivityTimestamp.
  • Remove dependencies on Sentinel-only metadata columns such as TenantId, SourceSystem, _IsBillable, and _BilledSize.
  • For device tables, review dependencies on MachineGroup. Don't rely on MachineGroup for filtering or scoping outside DeviceInfo.
  • Update playbooks that query Log Analytics to use the Advanced Hunting API. For more information, see Update Logic App playbook automation.
  • Validate Microsoft Defender permissions and scoping for analysts, workbook viewers, and automation identities. For more information, see Update permissions and roles with Unified RBAC.
  • Advanced Hunting tables don't include custom columns that end in _CF. These columns are added by a data collection rule (DCR) in your workspace. If your content uses a _CF column, update it before you move it to Advanced Hunting.

Common update patterns

Only a few schema patterns change between Microsoft Sentinel and Advanced Hunting. Update your content based on the patterns that apply to each table.

Pattern 1: Dynamic fields become strings

This pattern applies to:

  • DeviceEvents
  • DeviceFileEvents
  • DeviceProcessEvents
  • DeviceLogonEvents
  • DeviceNetworkEvents
  • DeviceInfo
  • EmailEvents
  • AlertEvidence

AdditionalFields, and LoggedOnUsers in DeviceInfo, are dynamic in Microsoft Sentinel but strings in Advanced Hunting.

Before member access or mv-expand, parse the value by using todynamic() and tostring().

For example:

DeviceInfo
| where Timestamp > ago(24h)
| extend Users = todynamic(tostring(LoggedOnUsers))
| mv-expand Users
| project Timestamp, DeviceName, AccountName = tostring(Users.UserName)

Pattern 2: Dynamic array fields become strings

This pattern applies to the following DeviceNetworkInfo fields:

  • IPAddresses
  • DnsAddresses
  • ConnectedNetworks
  • DefaultGateways

Parse these fields before using mv-expand or accessing individual elements.

For example:

DeviceNetworkInfo
| where Timestamp > ago(24h)
| extend IPs = todynamic(tostring(IPAddresses))
| mv-expand IPs
| project Timestamp, DeviceName, IPAddress = tostring(IPs.IPAddress)

Pattern 3: Port fields become integers

This pattern applies to:

  • IdentityLogonEvents
  • IdentityDirectoryEvents
  • IdentityQueryEvents

The Port and DestinationPort fields are strings in Microsoft Sentinel and integers in Advanced Hunting.

For example, a Microsoft Sentinel query might use:

| where Port == "3389" or DestinationPort == "445"

In Advanced Hunting, normalize the fields by using toint():

IdentityLogonEvents
| where Timestamp > ago(24h)
| where toint(Port) == 3389 or toint(DestinationPort) == 445

Pattern 4: SecurityAlert splits into AlertInfo and AlertEvidence

Microsoft Sentinel's SecurityAlert table doesn't have a single equivalent in Advanced Hunting.

Alert data is split between:

  • AlertInfo, which contains one row per alert.
  • AlertEvidence, which contains one row per entity associated with an alert.

The following fields map between the schemas:

SecurityAlertfieldAdvanced HuntingNotes
SystemAlertIdAlertIdJoin key between AlertInfo and AlertEvidence
AlertNameTitle
ProviderNameServiceSource
EntitiesAlertEvidence rowsJoin the tables instead of using mv-expand on Entities

Join AlertInfo and AlertEvidence on AlertId when you need alert information together with related entities.

For example:

AlertInfo
| where Timestamp > ago(1h)
| where Title == "Suspicious PowerShell"
| join kind=inner (
    AlertEvidence
    | where Timestamp > ago(1h)
) on AlertId
| extend Fields = todynamic(tostring(AdditionalFields))
| project Timestamp, AlertId, Title, Severity, ServiceSource, EntityType, DeviceId, AccountName

Other column changes

In addition to the changes that apply to all tables, some tables have renamed, removed, or retyped columns in Advanced Hunting. Column names are case-sensitive.

TableMicrosoft SentinelAdvanced Hunting
CallActivityEventsTimeGeneratedTimeGenerated works and returns the same value as ActivityTimestamp. The table doesn't have a Timestamp column, so don't change TimeGenerated to Timestamp. In new queries, use ActivityTimestamp.
CallActivityEventsOriginatorUserObjectIdOriginatorObjectId
FileMaliciousContentInfoDetectionMethods (string)DetectionMethods (dynamic)
EmailEventsLastEventExecutionTimeNot available. Remove this column from your queries.
EmailPostDeliveryEventsApproverUpnNot available in most tenants. Remove this column from your queries, or use column_ifexists("ApproverUpn", "").
DeviceInfoDeviceObjectIdNot available. Remove this column from your queries.
AlertEvidenceAzureResourceId, AzureResourceType, AzureSubscriptionIdResourceID, ResourceType, SubscriptionId
DisruptionAndResponseEventsDataSourcesDataSource. Queries that already use DataSource don't need to change.
DisruptionAndResponseEventsInitiatingProcessId (int)InitiatingProcessId (long)
DisruptionAndResponseEventsPort (string)Port (int)
DisruptionAndResponseEventsReportId (string)ReportId (long)
DisruptionAndResponseEventsMachineGroupPresent but always empty. Don't use it for filtering or scoping.
CloudAuditEventsCloudResourceIdNot available. Use AzureResourceId, AwsResourceName, or GcpFullResourceName.
CloudDnsEventsImageDigest, HostName, RegionMight not be available. To check, run CloudDnsEvents | getschema in Advanced Hunting.
CloudProcessEventsParentProcessId (string), InitiatingProcessId (string)ParentProcessId (long), InitiatingProcessId (long)
CloudProcessEventsAdditionalFields (string)AdditionalFields (dynamic)

Some CallActivityEvents columns, including OriginatorObjectId, CallType, CallName, and the ActivityRecipient columns, are available in Advanced Hunting only if your organization has preview features turned on. Before you update content that uses these columns, run CallActivityEvents | getschema in Advanced Hunting to check which columns you have.

This table reflects the schema that Advanced Hunting returns. If a column name or type differs from the table's schema reference page, run <TableName> | getschema in Advanced Hunting to confirm.

Validate your updates

Before you stop ingestion in Microsoft Sentinel:

  1. Update queries. Update hunting and saved queries for the applicable parsing logic, port conversions, and alert joins.
  2. Validate detections. Confirm that analytics rules and custom detections return the expected results.
  3. Validate workbooks. Check tiles, filters, and parameters that reference changed columns or data types.
  4. Validate automation. Test playbooks, Logic Apps, and API integrations against the Advanced Hunting response format, and confirm Microsoft Defender permissions and workload scoping for automation identities.
  5. Stop ingestion. When all content is updated and validated, stop ingestion for the supported Defender XDR tables. For steps, see Optimize Microsoft Defender XDR data ingestion. \ No newline at end of file