Skip to content

Commit 67e39aa

Browse files
committed
Learn Editor: Update work-with-stix-objects-indicators.md
1 parent 7b8c107 commit 67e39aa

File tree

1 file changed

+4
-3
lines changed

1 file changed

+4
-3
lines changed

articles/sentinel/work-with-stix-objects-indicators.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -20,10 +20,11 @@ On April 3, 2025, we publicly previewed two new tables to support STIX (Structur
2020

2121
For more information about threat intelligence in Microsoft Sentinel, see [Threat intelligence in Microsoft Sentinel](understand-threat-intelligence.md).
2222

23-
>[!IMPORTANT]
23+
> [!IMPORTANT]
2424
> Microsoft Sentinel will ingest all threat intelligence into the new `ThreatIntelIndicators` and `ThreatIntelObjects` tables, while continuing to ingest the same data into the legacy `ThreatIntelligenceIndicator` table until July 31, 2025.
25-
>
26-
> **Be sure to update your custom queries, analytics and detection rules, workbooks, and automation to use the new tables by July 31, 2025.** After this date, Microsoft Sentinel will stop ingesting data to the legacy `ThreatIntelligenceIndicator` table. We're updating all out-of-the-box threat intelligence solutions in Content hub to leverage the new tables. For more information about the new table schemas, see [ThreatIntelIndicators](/azure/azure-monitor/reference/tables/threatintelligenceindicator) and [ThreatIntelObjects](/azure/azure-monitor/reference/tables/threatintelobjects).
25+
> **Be sure to update your custom queries, analytics and detection rules, workbooks, and automation to use the new tables by July 31, 2025.** After this date, Microsoft Sentinel will stop ingesting data to the legacy `ThreatIntelligenceIndicator` table. We're updating all out-of-the-box threat intelligence solutions in Content hub to leverage the new tables.
26+
> We’ve made improvements to our parsing logic to ensure that each Indicator of Compromise (IoC) ingested results in at least one row being sent to Log Analytics. This change improves visibility and consistency across your threat intelligence data. Additionally, we’ve introduced more top-level fields in the new `ThreatIntelIndicators` and `ThreatIntelObjects` tables. These fields are designed to make queries easier to write and more efficient to run. As a result of these enhancements, you may notice a change in data volume and associated costs when using the `ThreatIntelIndicators` table compared to the previous `ThreatIntelligenceIndicator` table.
27+
> For details on the updated schema and how it may affect your usage, see [ThreatIntelIndicators](/azure/azure-monitor/reference/tables/threatintelindicators) and [ThreatIntelObjects](/azure/azure-monitor/reference/tables/threatintelobjects).
2728
2829
## Identify threat actors associated with specific threat indicators
2930

0 commit comments

Comments
 (0)