Study guide

15.2 Microsoft Sentinel Data Connectors, Content Hub & Normalization

Microsoft Azure Security Technologies AZ-500

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Exam Overview & Azure Security Architecture Foundation

1.1 Azure Security Engineer Role & Exam Logistics 1.2 Microsoft Cybersecurity Reference Architecture & Zero Trust Principles

2 Chapter 2: Secure Identity and Access - Authentication, MFA & PIM

2.1 Microsoft Entra ID Security, Users, and Groups 2.2 Authentication Methods, MFA, and Conditional Access Policy Design 2.3 Microsoft Entra Privileged Identity Management (PIM)

3 Chapter 3: Secure Identity and Access - RBAC & Workload Identity

3.1 Azure RBAC, Custom Roles, and Governance 3.2 Workload Identities and Managed Identities 3.3 External Identities and Cross-Tenant Collaboration

4 Chapter 4: Microsoft Entra Application Access & Consent Governance

4.1 Enterprise Applications, OAuth Permission Grants & Consent Governance 4.2 App Registrations, Permission Scopes & Service Principal Credentials

5 Chapter 5: Secure Azure Networking - Boundary & Perimeter Protection

5.1 Virtual Network Security & Micro-segmentation 5.2 Azure Firewall and Firewall Manager 5.3 Web Application Firewall (WAF) & Azure Front Door

6 Chapter 6: Secure Azure Networking - Private Access & Monitoring

6.1 Private Connectivity with Private Endpoints & Private Link 6.2 Azure Bastion & Remote Management Security 6.3 Network Perimeter Protection & Flow Monitoring

7 Chapter 7: Network Architecture, Routing & Hybrid Connectivity

7.1 Azure Virtual Network Manager, Network Groups & User-Defined Routes 7.2 VPN Gateway, ExpressRoute Encryption & Virtual WAN Secured Hub 7.3 Network Integration for App Service, Functions, App Service Environment & SQL Managed Instance

8 Chapter 8: Public and Edge Access Protection

8.1 Azure Application Gateway Security, TLS Policy & Mutual Authentication 8.2 Azure Front Door, CDN Caching & TLS for App Service and API Management

9 Chapter 9: Compute, Container & Registry Security

9.1 Azure Virtual Machine Hardening & Host Security 9.2 Azure Key Vault Deep Dive & Secrets Lifecycle 9.3 Container & Azure Kubernetes Service (AKS) Security 9.4 Azure Container Instances, Container Apps & Registry Access Control

10 Chapter 10: Storage Security, Access Methods & Data Protection

10.1 Storage Account Security & Access Controls 10.2 Selecting and Configuring Access to Azure Files 10.3 Selecting and Configuring Access to Azure Blob Storage 10.4 Storage Data Protection: Soft Delete, Versioning, Point-in-Time Restore & Backup

11 Chapter 11: Data Platform & Database Security

11.1 Azure SQL Database Security & Always Encrypted 11.2 Database Auditing & Vulnerability Assessment 11.3 Data Discovery, Classification, & Microsoft Purview Integration

12 Chapter 12: Cloud Governance, Key Lifecycle & Asset Protection

12.1 Azure Policy for Security Governance: Definitions, Initiatives, Effects & Remediation 12.2 Key Vault Backup, Recovery & Automated Key Rotation 12.3 Implementing Security Controls to Protect Backups 12.4 Security Controls for Asset Management: Locks, Tags, Resource Graph & Azure Arc

13 Chapter 13: Microsoft Defender for Cloud - Posture & Workload Protection

13.1 Microsoft Defender for Cloud & Secure Score 13.2 Defender Cloud Workload Protection (CWP) Plans 13.3 Defender for Cloud Inventory, Compliance Standards & Custom Standards 13.4 Connecting AWS and GCP Environments to Microsoft Defender for Cloud

14 Chapter 14: External Attack Surface & Vulnerability Management

14.1 Microsoft Defender External Attack Surface Management (EASM) 14.2 Agentless Scanning & Microsoft Defender Vulnerability Management for Azure VMs 14.3 Defender for Cloud DevOps Security: GitHub, Azure DevOps & GitLab

15 Chapter 15: Security Monitoring, Microsoft Sentinel & Automation

15.1 Azure Monitor Data Collection Rules & Network Security Event Monitoring 15.2 Microsoft Sentinel Data Connectors, Content Hub & Normalization 15.3 Microsoft Sentinel Workspace & KQL Threat Hunting 15.4 Sentinel Incident Management & SOAR Automation

15.2 Microsoft Sentinel Data Connectors, Content Hub & Normalization

Key Takeaways Explain This Topic AI

Sentinel connectors fall into service-to-service, agent-based with data collection rules, codeless platform, API-based, and threat intelligence categories.

Content hub solutions package connectors with analytics rules, workbooks, hunting queries, and playbooks so a source arrives with detections attached.

CEF and syslog from third-party appliances are collected by the Azure Monitor Agent running on a Linux forwarder with a matching data collection rule.

ASIM parsers normalize disparate sources into shared schemas so one analytics rule can cover many products.

The SentinelHealth table reports connector and automation health, which is how silent ingestion failures are detected.

Last updated: August 2026

Connector Types and When Each Applies

Type Mechanism Examples

Service-to-service (native) Microsoft-to-Microsoft, enabled with a toggle and RBAC Azure Activity, Microsoft Entra ID sign-in and audit logs, Microsoft Defender XDR, Microsoft Defender for Cloud, Office 365

Agent-based via DCR Azure Monitor Agent plus a data collection rule Windows Security Events, Windows Forwarded Events, Syslog, Common Event Format (CEF)

Codeless Connector Platform (CCP) Declarative connector definition, no code to maintain Many SaaS and vendor sources

API / Functions / Logstash Custom pull or push into a custom table via the Logs Ingestion API AWS S3, GCP, bespoke applications

Threat intelligence TAXII feeds, the upload API, or a platform integration Commercial and open-source indicator feeds

Choosing correctly is a common exam task. Anything Microsoft-to-Microsoft should be a native connector, never a custom API integration. Anything from a network appliance is CEF or syslog through a forwarder. Anything from a cloud provider has a purpose-built connector — for AWS, the S3-based connector reading CloudTrail, GuardDuty, and VPC flow logs.

Content Hub: Connectors Arrive With Their Detections

The Content hub is Sentinel's marketplace of solutions — packaged content for a product or scenario. Installing a solution can deliver, in one action:

The data connector and its configuration steps.

Analytics rule templates tuned to that source.

Workbooks for visualization.

Hunting queries for proactive investigation.

Playbooks for automated response.

Parsers , including ASIM parsers where relevant.

The practical lesson: install the solution from Content hub rather than only enabling the connector , because a connector without rules is just an ingestion bill. After installing, review the analytics rule templates and create rules from the ones that match your environment — templates are not active until instantiated.

The CEF and Syslog Forwarder Pattern

For firewalls, proxies, and other appliances that emit syslog or CEF:

Deploy a Linux virtual machine to act as a forwarder, reachable from the appliances.

Install the Azure Monitor Agent on it and run the provided installation script, which configures rsyslog or syslog-ng to listen and forward.

Create a data collection rule targeting the forwarder that collects the Microsoft-CommonSecurityLog stream (CEF) or Microsoft-Syslog stream, and sends it to the Sentinel workspace.

Point the appliances at the forwarder, typically on UDP or TCP 514.

Security considerations for the forwarder: it becomes a chokepoint and a target, so harden it like a jump host — no public IP, NSG restricted to the appliance source addresses, Defender for Servers enabled, and monitoring for the forwarder process itself. Size for peak events per second and deploy more than one behind a load balancer where volume demands it.

ASIM: One Rule, Many Products

The Advanced Security Information Model (ASIM) solves the problem that every vendor names the same field differently. ASIM defines normalized schemas — Authentication, Network Session, DNS Activity, Process Event, File Event, Web Session, Registry Event, and others — and ships parsers that map each source's native table into that schema.

Source-specific parsers map one product's table to a schema.

Unifying parsers (named with the _Im_ prefix for parameterized versions, _ASim_ for the non-parameterized form) query across all source-specific parsers at once.

The payoff: an analytics rule written against _Im_NetworkSession covers every firewall you have normalized, including ones you onboard next year, with no rule changes. Without ASIM you would write and maintain one rule per product. When a scenario mentions "one detection covering multiple firewall vendors", ASIM is the answer.

The cost is query-time computation, since parsers are functions evaluated at query time. For very high-volume, latency-sensitive rules, a source-specific rule may still be appropriate.

Connector Health and Table Plans

Silent ingestion failure is the most dangerous failure mode in a SIEM — the dashboard looks calm because nothing is arriving. Monitor for it:

The SentinelHealth table records connector, analytics rule, and automation health events. Enable health monitoring on the workspace and build analytics rules on it.

Build a simple volume-anomaly rule per critical table: alert when today's row count for SecurityEvent or CommonSecurityLog falls far below the trailing average.

Watch agent heartbeat data for forwarders and critical servers.

Table plans shape what you can do with data once ingested:

  • Plan Query behaviour Typical use
  • Analytics Full KQL, used by analytics rules Detection-relevant security logs
  • Basic Limited query, cheaper ingestion High-volume logs used mainly for investigation
  • Auxiliary Lowest cost, limited querying Verbose logs kept for occasional lookback

Interactive retention on Analytics tables extends up to 730 days , with long-term retention available well beyond that for archival lookback. Choose the plan per table deliberately: putting a verbose proxy log on the Analytics plan is one of the fastest ways to exhaust a security budget without improving detection coverage.