Skip to content

Release notes for the Splunk Add-on for Microsoft Security

About this release

Version 5.0.0 of the Splunk Add-on for Microsoft Security was released on November 5, 2026.

Version 5.0.0 changes the Defender Advanced Hunting alert action to use Microsoft Graph. Before you upgrade, review the required migration steps.

Compatibility

Version 5.0.0 is compatible with the following software, Common Information Model (CIM) versions, platforms, and vendor products:

Component Supported versions or products
Splunk platform 9.4.x, 10.0.x, 10.2.x, 10.4.x, 10.6.x, 10.7.x
Splunk Common Information Model 8.5.x
Operating systems Windows and Linux
Vendor products Microsoft Defender XDR, Microsoft Defender for Endpoint, Azure Event Hubs, Microsoft Defender Threat Intelligence

Note

Version 5.0.0 supports the current Splunk platform field alias behavior. It does not support field alias configurations created for older field alias behavior. See Field alias behavior change in the Splunk Enterprise Release Notes.

New features

Version 5.0.0 includes the following new features:

  • Microsoft Graph support for Defender Advanced Hunting. The Defender Advanced Hunting alert action now sends queries to the Microsoft Graph POST /v1.0/security/runHuntingQuery endpoint. The action supports Commercial and Government Community Cloud (GCC), GCC High, and Department of Defense (DoD) Microsoft Graph deployments.
  • Detection status for alert evidence. The detection_status field contains the available detectionStatus values from legacy Microsoft Defender for Endpoint alert evidence and Microsoft Graph incident-alert entities.
  • Inventory network fields for Defender machines. The ms:defender:machines source type now maps to the Inventory Network dataset. The ip and mac fields follow the CIM single-value contract and support IPv4 and IPv6 source values.
  • Additional file hashes. The multivalue file_hashes field contains available MD5, SHA1, and SHA256 values from Graph and Event Hub file, image-load, and email-attachment events. The existing file_hash field remains available.

Breaking changes

Version 5.0.0 includes the following breaking changes:

  • Defender Advanced Hunting requires a Microsoft Graph permission. The alert action no longer uses the legacy Microsoft Defender XDR /api/advancedhunting/run endpoint. Add the Microsoft Graph application permission ThreatHunting.Read.All and grant administrator consent before you upgrade. The legacy AdvancedHunting.Read.All permission does not authorize this action.
  • Review saved cloud environments. Existing alert actions are mapped to Microsoft Graph environments during runtime migration. Previous saved values do not reliably distinguish GCC High from DoD. After you upgrade, explicitly select DoD for every DoD alert action.
  • CIM field values changed. Several source, destination, signature, network-action, inventory-network, and simulation mappings changed to improve alignment with the CIM data models. Review searches, dashboards, and alerts that use these fields. See CIM mapping changes in version 5.0.0.
  • Graph filesystem sizes use CIM kilobytes. For Graph DeviceFileEvents, file_size now converts the Microsoft FileSize byte count to numeric kilobytes, including zero and fractional values. Use the unchanged FileSize for bytes. Event Hub file/image kilobytes and email attachment bytes retain their existing units.
  • Graph network null addresses are omitted. For Graph DeviceNetworkEvents, missing, empty, JSON-null, and literal null addresses leave src, src_ip, dest, and dest_ip unset instead of identifying an endpoint with the string null.
  • Inventory statuses no longer populate boolean enabled. Event Hub DeviceInfo onboarding and DeviceNetworkInfo adapter operational status no longer populate CIM enabled with strings such as Onboarded or Down. Use the unchanged raw status fields, or the existing sensor-health/adapter status mapping. Genuine source enabled values remain available. See the migration guidance.

Fixed issues

Version 5.0.0 of the Splunk Add-on for Microsoft Security fixes the following issues:

  • Checkpoint-safe Microsoft Graph pagination. Graph incident and alert checkpoints advance only after the add-on successfully processes every page in a query window. If a later page fails, the next run retries the incomplete window instead of skipping unprocessed data.
  • Windows Python 3.13 native imports. The add-on includes the matching Python 3.13 stable-ABI DLL required by its bundled Cryptography and Protobuf extensions. This fixes native import failures when the extensions cannot locate python3.dll in the Splunk installation. The separate known issue when Python 3.9 is forced remains.
  • Runtime libraries after an in-place upgrade. The add-on continues to use the Requests and urllib3 libraries supplied by Splunk when an older add-on installation leaves its own copies behind.
  • Configuration and collection hardening. The add-on validates configuration labels, safely renders stored values, records configuration changes and mutating alert actions in a security audit log, and bounds collection resources.
  • Third-party security updates. Updated bundled Cryptography to 50.0.0 on Windows and Linux, PyJWT to 2.15.1, and certifi to 2026.10.23. Updated OpenTelemetry dependencies for Python 3.13 and applied tracestate validation protection to the Python 3.9 bundle.

Known issues

Version 5.0.0 of the Splunk Add-on for Microsoft Security contains the following known issues:

Event Hub input can fail when Python 3.9 is forced on Windows

On Windows Server 2022 with Splunk Enterprise 10.4.4, forcing Python 3.9 for the Microsoft Defender Event Hub input can cause its Python process to crash during input initialization. The input fails to register with Splunk, preventing Event Hub data collection. This issue can occur before the input connects to Azure and does not require a particular event payload.

The add-on declares python.required = 3.9, 3.13. On Splunk Enterprise 10.4, this normally selects Python 3.13 when available. The default Python 3.13 configuration passed input initialization, REST, and restart checks in the tested environment. The affected range of other Windows and Splunk versions has not been established.

Workaround: On Splunk Enterprise 10.4 with Python 3.13 available, remove any local override that restricts the [microsoft_defender_event_hub] stanza in inputs.conf to python.required = 3.9, so that the add-on’s default version list applies. Alternatively, set python.required = 3.13 for that stanza. Restart Splunk and verify that the Event Hub input is available before resuming collection.

Third-party software attributions

Version 5.0.0 incorporates third-party software attributed in the Splunk Add-on for Microsoft Security version 5.0.0 report.