azureblog.co.uk
← SC-500 study plan
SC-500 · Manage and monitor security posture

Implement activity and event collection in Microsoft Sentinel

Creating and connecting workspaces, Sentinel roles, content hub, Azure data connectors, Syslog and CEF, Windows events and WEF, custom tables, automation, retention, and querying Purview Audit in Defender XDR.

  • 22 min
  • 10 concepts
  • Try it yourself
  • 4-question check

Learn

For a cloud security engineer, Sentinel is the place all Azure security signals end up. This lesson covers standing it up and feeding it; the SC-200 Sentinel lessons go deeper on detections and hunting.

  1. 1

    Create and connect workspaces in Microsoft Sentinel

    Create a Log Analytics workspace (usually one per tenant or region), enable Microsoft Sentinel on it, and connect it to the Microsoft Defender portal (the unified SecOps platform; one primary workspace plus secondaries). Multiple tenants can be managed with Azure Lighthouse and multitenant management in Defender.

    Remember: Sentinel runs in the Defender portal now.

  2. 2

    Assign roles in Microsoft Sentinel

    Assign Microsoft Sentinel Reader, Responder or Contributor at the workspace or resource group scope, plus Logic App Contributor for playbook authors and Microsoft Sentinel Automation Contributor for Sentinel itself on playbook resource groups. In the Defender portal, unified RBAC can also grant Sentinel access.

    Remember: Least privilege: Responder for analysts.

  3. 3

    Implement and use content hub solutions

    The content hub installs solutions bundling data connectors, parsers, analytics rules, hunting queries, workbooks and playbooks for a product (for example Microsoft Entra ID, Azure Activity, Palo Alto). Install, then enable the rules you need from templates and keep solutions updated.

    Remember: Install the solution, then enable its rule templates.

  4. 4

    Configure and use Microsoft data connectors for Azure resources

    Connect Azure Activity (via Azure Policy-driven diagnostic settings), Microsoft Defender for Cloud (alerts, tenant-based connector), Microsoft Entra ID (sign-in and audit logs via diagnostic settings), Azure Key Vault, Azure Firewall, Azure Storage and other resource logs (diagnostic settings, often by policy).

    Remember: Azure resource logs = diagnostic settings, at scale with Policy.

  5. 5

    Implement and configure syslog and Common Event Format (CEF) event collections

    Deploy a Linux log forwarder with the Azure Monitor Agent (Azure VM or Arc-enabled), create DCRs for Syslog via AMA (facilities and severities to the Syslog table) and CEF via AMA (to CommonSecurityLog), and point appliances at the forwarder on port 514.

    Remember: Forwarder with AMA, DCR per data type.

  6. 6

    Implement and configure collection of Windows Security events by using data collection rules, including Windows Event Forwarding (WEF)

    Use Windows Security Events via AMA with a DCR (All, Common, Minimal or Custom XPath) for Azure VMs and Arc servers, into SecurityEvent. For machines without AMA, forward events with WEF to a collector running AMA and use the Windows Forwarded Events connector (WindowsEvent table).

    Remember: XPath in the DCR filters noisy events.

  7. 7

    Create custom log tables in the workspace to store ingested data

    Create custom _CL tables with a schema, a DCR and data collection endpoint for the Logs Ingestion API, or collect text/JSON logs with AMA. Use ingestion-time transformations to parse and filter.

    Remember: _CL tables + DCR + Logs Ingestion API.

  8. 8

    Implement automation rules and playbooks in Microsoft Sentinel

    Automation rules triage incidents (assign, tag, change severity) and trigger playbooks (Logic Apps with managed identity) to enrich or respond, for example disabling a user in Entra ID or blocking an IP on Azure Firewall.

    Remember: Rules triage; playbooks act.

  9. 9

    Implement data retention in Microsoft Sentinel data stores

    Set per-table retention in the analytics tier (interactive, 90 days included for Sentinel) and long-term retention in the data lake tier (up to 12 years, low cost). Send high-volume, low-value logs to the data lake only, and use KQL jobs or summary rules to bring subsets back.

    Remember: Analytics for detection, lake for long-term.

  10. 10

    Query Microsoft Purview Audit in Defender XDR

    Microsoft 365 audit data is available in Defender XDR Advanced Hunting through tables such as CloudAppEvents (Microsoft 365 activities via Defender for Cloud Apps) so you can correlate Purview Audit events (file access, mailbox actions, admin changes) with endpoint and identity data using KQL.

    Remember: Microsoft 365 activity in hunting: CloudAppEvents.

Standing up Sentinel

  1. WorkspaceCreate and enable Sentinel.
  2. Defender portalConnect the workspace.
  3. RolesReader, Responder, Contributor.
  4. Content hubInstall solutions and connectors.
  5. Rules and automationEnable detections, automation rules, playbooks.
  6. RetentionTier per table.

Try it

Which connector or setting?

This interactive part needs JavaScript.

In the portal

  • Connect a workspaceMicrosoft Defender portal: Settings > Microsoft Sentinel > Workspaces
  • Content hubMicrosoft Defender portal: Microsoft Sentinel > Content management > Content hub
  • Data connectorsMicrosoft Defender portal: Microsoft Sentinel > Configuration > Data connectors
  • TablesMicrosoft Defender portal: Microsoft Sentinel > Configuration > Tables

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-500 study plan.

  1. Where are Sentinel solutions with connectors and rules installed?

  2. Which role should Sentinel have on a playbook's resource group?

  3. Which table do CEF logs land in?

  4. Which tier keeps data cheaply for up to 12 years?

Sources

Facts in this lesson are from Microsoft Learn. This site isn't affiliated with Microsoft.