Study guide
7.2 Data Connectors and Security Signals
Azure SC-900 Study Guide Exam
Track your progress as you read
Finished sections get a check mark.
1 Orientation: SC-900 Audience, Format, Scoring, Retakes, and Study Map
1.1 Credential Purpose and Audience 1.2 Exam Duration, Seat Duration, and Experience 1.3 Scoring, Scaled Score, and Pass-Rate Myths 1.4 Retake Policy and Certification Lifecycle 1.5 Scheduling, Price, and Delivery Options 1.6 Skills Measured and Study Map
2 Security, Compliance, and Identity Concepts: Zero Trust, Shared Responsibility, and GRC
2.1 Shared Responsibility Model 2.2 Defense in Depth and the CIA Triad 2.3 Zero Trust Model 2.4 Encryption, Hashing, and Data States 2.5 Governance, Risk, and Compliance 2.6 Identity Perimeter, Authentication, Authorization, and Federation
3 Microsoft Entra ID: Identities, Hybrid Identity, and Authentication
3.1 Microsoft Entra ID Foundations 3.2 Identity Types and Directory Objects 3.3 Hybrid Identity and Entra Connect Concepts 3.4 Authentication Methods and Sign-in Assurance 3.5 Multifactor Authentication 3.6 Password Protection, Self-Service Password Reset, and External Identities
4 Microsoft Entra Access Management, Governance, PIM, and Identity Protection
4.1 Conditional Access Purpose 4.2 Signals and Controls 4.3 Microsoft Entra Roles and Role-Based Access Control 4.4 Identity Governance, Entitlement Management, and Lifecycle Governance 4.5 Access Reviews and Privileged Identity Management 4.6 Microsoft Entra ID Protection and Risk
5 Azure Infrastructure Security: DDoS, Firewall, WAF, NSGs, Bastion, and Key Vault
5.1 Choose the Right Infrastructure Security Control 5.2 Azure DDoS Protection for Availability 5.3 Azure Firewall for Centralized Network Policy 5.4 Web Application Firewall for HTTP Workloads 5.5 Virtual Networks, Subnets, and Network Security Groups 5.6 Bastion and Key Vault for Administration and Secrets
6 Defender for Cloud: CSPM, Cloud Workload Protection, and Secure Score
6.1 Defender for Cloud Purpose and Exam Role 6.2 CSPM, Foundational Posture, and Defender CSPM 6.3 Policies, Standards, and Security Recommendations 6.4 Secure Score and Remediation Priority 6.5 Regulatory Compliance and Multicloud Posture 6.6 Cloud Workload Protection and Defender Plans
7 Microsoft Sentinel: SIEM, SOAR, Analytics, Hunting, Workbooks, and Playbooks
7.1 Sentinel as SIEM and SOAR 7.2 Data Connectors and Security Signals 7.3 Analytics Rules, Incidents, and Detection 7.4 Workbooks for Visual Review 7.5 Hunting, KQL Awareness, and Notebooks 7.6 Automation Rules and Logic Apps Playbooks
8 Microsoft Defender XDR: Office, Endpoint, Cloud Apps, Identity, Vulnerability, and Threat Intelligence
8.1 Defender XDR Suite and Microsoft Defender Portal 8.2 Defender for Office 365 8.3 Defender for Endpoint 8.4 Defender for Cloud Apps 8.5 Defender for Identity 8.6 Vulnerability Management and Threat Intelligence
9 Microsoft Purview, Service Trust, Privacy, Compliance Manager, and Compliance Score
9.1 Service Trust Portal and Assurance Resources 9.2 Privacy Principles and Microsoft Priva 9.3 Microsoft Purview Portal 9.4 Compliance Manager Assessments 9.5 Compliance Score and Improvement Actions 9.6 Scenario Selection for Trust, Privacy, and Compliance Manager
10 Microsoft Purview Data Classification, Labels, DLP, Retention, eDiscovery, and Audit
10.1 Data Classification Foundations 10.2 Content Explorer and Activity Explorer 10.3 Sensitivity Labels and Label Policies 10.4 Data Loss Prevention 10.5 Retention, Records Management, and Label Policies 10.6 eDiscovery, Audit, and Insider Risk Management
11 SC-900 Product Selection Playbooks and Common Microsoft Rebrand Traps
11.1 Read the Scenario Before Picking a Product 11.2 Entra Playbook for Identity, Access, and Governance 11.3 Defender Playbook for Protection, Detection, and Posture 11.4 Sentinel Playbook for SIEM, SOAR, and Hunting 11.5 Purview Playbook for Compliance, Data, and Risk 11.6 Renamed Products and Similar-Name Traps 11.7 Microsoft Learn Practice Assessment Review Loop
12 Final SC-900 Review, Timed Practice, Exam Day, and Next Certification Path
12.1 Domain-Weighted Final Review Plan 12.2 Timed Practice and Pacing 12.3 Exam Sandbox and Question Experience 12.4 Exam-Day Logistics and Boundaries 12.5 Scoring, Retakes, and After-Exam Decisions 12.6 Final Memory Check and Scenario Drills 12.7 Next Certification Path After SC-900
7.2 Data Connectors and Security Signals
Key Takeaways Explain This Topic AI
Data connectors are how Sentinel ingests security signals into its Log Analytics workspace.
Connectors come in types: native service-to-service (e.g., Microsoft 365, Entra ID, Defender XDR), agent-based, and standards-based (Syslog, CEF, REST API).
Many connectors ship as packaged solutions that include analytics rules, workbooks, and hunting queries.
Without connected data, analytics rules, hunting, and workbooks have nothing to evaluate.
Sentinel stores ingested data in a Log Analytics workspace; billing is largely based on ingestion and retention.
Last updated: September 2026
Connectors Are the Front Door
A data connector is the mechanism by which Microsoft Sentinel ingests security signals so they land in the underlying Log Analytics workspace . Connectors are the first step in the Sentinel workflow: analytics rules, incidents, workbooks, hunting queries, and playbooks all operate on the data that connectors bring in. If a scenario says an organization wants to collect security signals to detect and investigate threats , the Sentinel answer begins with connectors.
Microsoft provides hundreds of out-of-the-box connectors , and the exam expects you to recognize the broad categories rather than memorize any one setup. The data lands in tables in the workspace and becomes queryable with Kusto Query Language (KQL) .
Connector type How it works Example sources
Native / service-to-service API-based, no agent; often a few clicks Microsoft Entra ID, Microsoft 365, Microsoft Defender XDR, Azure activity
Agent-based Azure Monitor Agent collects logs from VMs/servers Windows/Linux machines, custom on-prem logs
Standards-based Industry log formats forwarded to Sentinel Syslog , Common Event Format (CEF) , firewalls, network appliances
API / codeless / TI REST APIs, Codeless Connector, threat-intel feeds SaaS apps, TAXII/STIX threat intelligence, AWS, GCP
Many connectors are delivered as content solutions from the Sentinel Content Hub. Installing one of these often deploys not just the ingestion path but also matched analytics rules, workbooks, and hunting queries tuned for that source. For SC-900 the key idea is simply that connectors are packaged on-ramps for getting the right data in.
Because Sentinel bills largely on data ingested and retained , connectors are also where data-cost decisions begin in the real world. The exam will not ask for pricing math, but it may describe an organization wanting to control which sources flow in — that is still a connector concept.
The Dependency Chain and Product Cues
Think of Sentinel as a pipeline that starts with connectors:
Connect — data connectors ingest signals into the Log Analytics workspace.
Detect — analytics rules evaluate that data and raise incidents.
Investigate — incidents and hunting work the data.
Visualize — workbooks chart trends from the data.
Respond — automation rules and playbooks act on incidents.
The practical consequence: no connected data means analytics, hunting, and workbooks have less to work with. A scenario that says "the team enabled an analytics rule but it never fires" frequently means the relevant data source is not connected . That cause-and-effect is a fair fundamentals-level inference.
Use connector wording to anchor product selection, but do not stop there. The prompt may move on to detection or response, yet the entry cue is the need to feed signals into a SIEM :
- Goal in the prompt Product/Concept
- Bring security logs from many sources into one place Sentinel data connectors
- Protect email and collaboration Defender for Office 365
- Protect endpoint devices Defender for Endpoint
- Ingest a third-party firewall's logs for a SIEM Sentinel (CEF/Syslog connector)
The exam may not use the word connector at all. It may describe a company whose security signals live in several systems and that wants a Microsoft solution to centralize them for analysis — that is still the Sentinel connector idea. Keep compliance (Purview) and identity governance (Entra) scenarios out of this lane: connectors carry security telemetry for detection and response, not retention labels or access reviews.
Why Connectors Define Sentinel's Value
The range of connectors is precisely what lets Sentinel act as a single pane of glass and what most clearly separates it from Microsoft Defender XDR. Defender XDR correlates signals only across Microsoft workloads — endpoints, identities, email, and cloud apps — with little configuration because the sources are built in. Sentinel deliberately reaches further: its connector catalog includes AWS, Google Cloud, dozens of firewall and proxy vendors, network appliances, SaaS platforms, identity providers, and custom applications , in addition to all of the Microsoft sources.
When a scenario stresses non-Microsoft or mixed-vendor sources, that breadth is the signal to choose Sentinel rather than a single Defender product.
Ask three questions about the source. Is it a supported cloud service? Look for a native service-to-service connector and its permissions, licensing, and configuration prerequisites. Is it a server or virtual machine producing operating-system logs? An Azure Monitor Agent connector and data collection rule may fit. Is it a network appliance, third-party service, or custom application? Check whether the source exposes Syslog, Common Event Format, or an API; use the documented connector or supported custom-ingestion method. These are selection clues, not guarantees that every product uses the same ingestion path.
- Source nature Typical connector approach
- Microsoft cloud service Native service-to-service connector; prerequisites vary
- Windows/Linux server or VM Agent-based via Azure Monitor Agent
- Firewall, proxy, network appliance Standards-based Syslog or CEF forwarding
- Custom app, SaaS, or threat feed REST API, Codeless Connector, or TAXII/STIX
For SC-900 you will not configure any of these. The durable takeaways are that connectors are the on-ramp that makes Sentinel's broad visibility possible, that they come in native, agent-based, and standards-based varieties, that many arrive as packaged solutions bundling rules, workbooks, and hunting queries, and that every downstream Sentinel feature depends on the data they bring in. Recognizing connectors as the first and enabling step lets you answer both "which product" and "why did detection not fire" questions correctly.