Data connectors use different collection methods to ingest data into Microsoft Sentinel. This page provides an overview of all collection methods and the connectors that use each method.
📚 Learn more: Microsoft Sentinel data connectors overview
Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · Logic Apps · 📊
| Collection Method | Total | Active | Deprecated 🚫 | Unpublished ⚠️ | |:------------------|------:|-------:|-------------:|---------------:| | CCF | 251 | 218 | 5 | 28 | | AMA | 168 | 37 | 122 | 9 | | Azure Function | 130 | 77 | 33 | 20 | | CCF Push | 58 | 55 | 0 | 3 | | REST Pull API | 51 | 35 | 1 | 15 | | Native | 17 | 15 | 1 | 1 | | Azure Diagnostics | 17 | 17 | 0 | 0 | | Azure Function (TI Upload API) | 15 | 12 | 1 | 2 | | Unknown | 12 | 12 | 0 | 0 | | Unknown (Custom Log) | 2 | 2 | 0 | 0 | | Defender | 1 | 1 | 0 | 0 | | Azure Function (TI Upload API)|Unknown | 1 | 1 | 0 | 0 | | MMA | 1 | 1 | 0 | 0 | | Total | 724 | 483 | 163 | 78 |
🚫 Deprecated: This connector has been deprecated and may be removed in future versions.
⚠️ Unpublished: This item is from a solution that is not yet published on Azure Marketplace or not installed in Content Hub.
Each table's collection_method is resolved in this order:
ASIM short-circuit — tables whose name starts with ASim (case-insensitive) are classified as Various, since ASIM is a normalization layer that aggregates events from many heterogeneous sources.
Intrinsic value from tables_reference.csv (e.g. AMA for tables with VM resource types). The shared agent-collected tables — Syslog, CommonSecurityLog, SecurityEvent, and Event — are intrinsically classified as AMA since AMA is the supported modern collection path, even though some legacy connectors that feed them still use MMA.
Defender XDR override — tables flagged source_defender_xdr=Yes are classified as Defender.
Azure Resources override — tables in the Azure Resources category are classified as Azure Diagnostics.
Inherited from feeding connectors when all of them use the same atomized method (1:1). Connector collection_method values are split on | before comparison.
Published-connector trump — when feeding connectors disagree but only some are published in the marketplace, the unpublished connectors are dropped from inference. If that yields a single method, it is used.
Precedence collapse when feeding connectors still disagree and the disagreement is a known generation overlap. Newer / canonical technology wins:
| Co-feeding methods | Inferred method |
|:-------------------|:----------------|
| AMA + MMA | AMA |
| CCF + CCF (Legacy) | CCF |
| Azure Function + CCF | CCF |
If steps 2–4 produced an intrinsic value that disagrees with what step 5–7 would infer, the intrinsic value wins and the disagreement is logged in the analyzer's exceptions report with reason=table_method_conflict. If feeding connectors still disagree after the published-trump filter and precedence collapse, no method is back-propagated and the table is logged with reason=table_method_ambiguity (only when no intrinsic value was set).
tables.csv records the resolution path on every row via the collection_method_source, collection_method_candidates, and feeding_connector_ids columns.
API-based connectors (CCF Push, Azure Function, REST Push API, and Custom Log) use one of two APIs to send data to the Log Analytics workspace. CCF and CCF (Legacy) are excluded as their ingestion is platform-managed.
| Collection Method | Log Ingestion API | HTTP Data Collector API | Undetermined | Total |
|---|---|---|---|---|
| Azure Function | 47 | 70 | 3 | 120 |
| CCF Push | 58 | - | - | 58 |
| REST Pull API | 1 | 50 | - | 51 |
| Azure Function (TI Upload API) | - | - | - | 0 |
| CCF | 11 | - | - | 11 |
| Azure Function (TI Upload API)|Unknown | - | - | - | 0 |
| Total | 117 | 120 | 3 | 265 |
Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · Logic Apps · 📊