Ingest data into Microsoft Sentinel
Choosing connectors, Windows Security events via AMA and WEF, Syslog and CEF via AMA, Azure activity logs, threat indicators and custom log tables.
- 20 min
- 7 concepts
- Try it yourself
- 4-question check
Learn
Sentinel is only as good as its data. Most connectors now use the Azure Monitor Agent (AMA) with data collection rules (DCRs), which decide exactly what's collected and can filter it before you pay for it.
- 1
Select data connectors based on data source requirements, including Windows logs and security events
Install connectors from content hub solutions. Microsoft sources use service-to-service connectors (Entra ID, Defender XDR, Microsoft 365, Azure Activity). Windows uses Windows Security Events via AMA (Security log) or Windows Forwarded Events. Linux and appliances use Syslog via AMA or CEF via AMA. SaaS sources use codeless connector framework connectors or Logic Apps/Functions.
Remember: Install the content hub solution to get the connector.
- 2
Configure collection of Windows Security events by using Windows Security Events via AMA, including data collection rules
Create a DCR for the connector choosing All events, Common, Minimal or Custom (XPath queries) and target machines (Azure VMs directly, others via Azure Arc). Events land in the
SecurityEventtable. Use XPath or transformations to drop noisy event IDs.Remember: Non-Azure servers need Azure Arc for AMA.
- 3
Plan and configure collection of Windows Security events by using Windows Event Forwarding (WEF)
With WEF, domain machines forward events by Group Policy subscription to a Windows Event Collector server. Install AMA on the collector and use the Windows Forwarded Events connector, which reads the ForwardedEvents channel into the
WindowsEventtable. Useful when you can't install AMA on every machine.Remember: WEF → collector with AMA → WindowsEvent table.
- 4
Plan and configure Syslog via AMA and Common Event Format (CEF) via AMA connectors
Appliances send Syslog or CEF to a Linux log forwarder running AMA (an Azure VM or Arc-enabled server). The DCR selects facilities and severities. Syslog goes to the
Syslogtable; CEF goes toCommonSecurityLog. Avoid duplicate collection of the same facility in both.Remember: CEF → CommonSecurityLog; Syslog → Syslog.
- 5
Configure collection of Azure activity logs by using Azure Policy and resource diagnostic settings
The Azure Activity connector uses an Azure Policy assignment to create subscription diagnostic settings that send activity logs to the workspace (
AzureActivitytable). Resource logs (Key Vault, Storage, NSG flow logs) use diagnostic settings, often deployed at scale with built-in DeployIfNotExists policies.Remember: Activity log at scale: the Azure Policy assignment from the connector.
- 6
Ingest threat indicators into Microsoft Sentinel
Bring in indicators with the Microsoft Defender Threat Intelligence connector, TAXII feeds, the Threat Intelligence Upload API, or manually. Indicators land in
ThreatIntelIndicators(andThreatIntelObjects) and are matched by threat intelligence analytics rules.Remember: TAXII feeds bring in standard STIX indicators.
- 7
Create custom log tables in the workspace to store ingested data
Create custom tables (names end in
_CL) through the portal or API, defining columns, with a DCR and data collection endpoint for the Logs Ingestion API, or collect text and JSON log files from machines with AMA. Use transformations to parse data on the way in.Remember: Custom tables end in _CL.
Source → connector → table
| Source | Connector | Table |
|---|---|---|
| Windows Security log | Windows Security Events via AMA | SecurityEvent |
| WEF collector | Windows Forwarded Events | WindowsEvent |
| Linux / Syslog appliances | Syslog via AMA | Syslog |
| Firewalls sending CEF | CEF via AMA | CommonSecurityLog |
| Azure subscriptions | Azure Activity | AzureActivity |
| Your own app | Logs Ingestion API | Custom_CL |
Try it
Which connector or method?
This interactive part needs JavaScript.
In the portal
- Data connectorsMicrosoft Defender portal: Microsoft Sentinel > Configuration > Data connectors
- Data collection rulesAzure portal: Monitor > Settings > Data Collection Rules
- Threat intelligenceMicrosoft Defender portal: Threat intelligence > Intel management
Key terms
Click a card to see the definition.
Check your understanding
4 questions. Score 80% or more and these skills are marked as confident in your SC-200 study plan.
Which table holds CEF data?
CEF is parsed into CommonSecurityLog.
On-premises servers need AMA. What's required first?
AMA on non-Azure machines needs Arc.
Which table do WEF-collected events land in?
Windows Forwarded Events uses WindowsEvent.
How do custom table names end?
Custom log tables use _CL.
Sources
- Microsoft Learn: Find your Microsoft Sentinel data connector
- Microsoft Learn: Windows security events via AMA
- Microsoft Learn: Ingest Syslog and CEF messages with AMA
- Microsoft Learn: Threat intelligence in Microsoft Sentinel
- Microsoft Learn: Logs Ingestion API
Facts in this lesson are from Microsoft Learn. This site isn't affiliated with Microsoft.