IntegrationsTAXII 2.1

Microsoft Sentinel Integration

Publish validated Premium IOC records as STIX 2.1 indicators through a TAXII 2.1 feed for Microsoft Sentinel.

5 min read•Last updated November 2026

Stream high-fidelity Indicators of Compromise (IOCs)—including malicious phishing domains, infostealer C2 servers, and ransomware infrastructure—directly into Microsoft Sentinel. ThreatPurge publishes validated threat intelligence using standard STIX 2.1 formats over TAXII 2.1 servers.

Microsoft Sentinel TAXII 2.1 Overview#

Microsoft Sentinel provides native integration with TAXII 2.1 threat intelligence feeds. ThreatPurge packages curated indicators discovered across dark web forums, stealer log dumps, and brand abuse monitors into an automated TAXII 2.1 feed, enabling real-time correlation against your corporate firewall, Microsoft 365, and Azure activity logs.

High & Critical Scoping
To optimize Sentinel Log Analytics ingestion and eliminate low-confidence noise, the TAXII feed exclusively streams validated High and Critical severity threat indicators.

Connecting ThreatPurge TAXII Feed to Sentinel#

Setting up the TAXII 2.1 data connector in Microsoft Sentinel:

1

Generate TAXII Credentials in ThreatPurge

In Settings > Integration Centre, open the Microsoft Sentinel card to retrieve your TAXII 2.1 Discovery Endpoint URL, Collection ID, Username, and API Secret.

2

Open Microsoft Sentinel in Azure Portal

Navigate to your Sentinel workspace and select Configuration > Data Connectors.

3

Open Threat Intelligence - TAXII Connector

Search for 'Threat Intelligence - TAXII (Preview)' and click 'Open Connector Page'.

4

Configure Connector Parameters

Enter a friendly name (e.g., ThreatPurge Premium Intel), paste the API Root URL, Collection ID, and your credentials.

5

Connect and Monitor Ingestion

Click 'Add'. Sentinel will poll the feed on an hourly basis and populate the ThreatIntelligenceIndicator table.

High and Critical Indicator Filtering#

ThreatPurge structures indicators into standard STIX 2.1 observable formats:

Indicator TypeSTIX 2.1 PatternThreat ContextSentinel Matching Entity
Domain Names[domain-name:value = 'badsite.xyz']Typosquatted domains, phishing portals, brand impersonatorsDnsEvents, AzureActivity, NetworkLogs
IPv4 / IPv6 Addresses[ipv4-addr:value = '198.51.100.4']Infostealer malware command-and-control, brute-force scannersCommonSecurityLog, SigninLogs, FirewallLogs
URLs[url:value = 'http://.../login']Active credential harvesters, phishing landing pagesOfficeActivity, CloudAppEvents, WebProxyLogs
File Hashes[file:hashes.'SHA-256' = '...']Infostealer payloads, malware binaries, ransomware droppersDeviceFileEvents, SecurityAlert

Correlating External IOCs with Azure Logs#

In Microsoft Sentinel, enable built-in Threat Intelligence Analytics rules (such as 'TI map IP entity to CommonSecurityLog' or 'TI map Domain entity to DnsEvents'). When an internal user or server interacts with a ThreatPurge indicator, Sentinel automatically raises an incident for immediate SOC containment.

Was this page helpful?

Your feedback helps us improve ThreatPurge technical documentation.