azureblog.co.uk
← SC-200 study plan
SC-200 · Manage a security operations environment

Configure automation for Defender XDR and Sentinel

Notifications, alert tuning, Defender for Endpoint advanced features, rules, custom data collection and ASR, automated investigation and response, attack disruption, device groups, and Sentinel automation rules and playbooks.

  • 25 min
  • 11 concepts
  • Try it yourself
  • 5-question check

Learn

A SOC can't handle every alert by hand. This skill area is about setting Defender XDR and Sentinel up so noise is suppressed, routine work happens automatically, and humans get the incidents that matter, quickly.

  1. 1

    Configure email notifications in Microsoft Defender XDR, including incidents, actions, and threat analytics

    In Settings > Microsoft Defender XDR > Email notifications, create rules for incidents (by service source and severity), actions (response and remediation actions taken) and threat analytics (new or updated reports affecting you). Choose recipients and whether to include organisation and device details.

    Remember: Notify on high severity incidents, not everything.

  2. 2

    Configure alert notifications in Microsoft Defender XDR, including tuning, suppression, and correlation

    Alert tuning rules (formerly suppression rules) automatically resolve or hide alerts matching conditions, such as a known admin tool, reducing noise. Defender XDR correlates related alerts into incidents automatically across workloads; you can link or unlink alerts and merge incidents.

    Remember: Known false positives: an alert tuning rule.

  3. 3

    Configure Microsoft Defender for Endpoint advanced features

    Advanced features include automated investigation, live response (and unsigned script execution), EDR in block mode, tamper protection, allow or block file, custom network indicators, web content filtering, Microsoft Intune connection, device discovery, and auto-resolve remediated alerts.

    Remember: EDR in block mode catches what a third-party AV misses.

  4. 4

    Configure rules settings in Microsoft Defender for Endpoint

    Rules include indicators (allow, warn, block or audit by file hash, IP, URL/domain or certificate), alert suppression/tuning, web content filtering categories, and automation folder exclusions that stop automated investigation remediating files in specific paths.

    Remember: Block a malicious hash everywhere: file indicator.

  5. 5

    Configure custom data collection in Microsoft Defender for Endpoint

    Custom data collection rules let you collect additional telemetry (specific events or tables beyond the default set) from Defender for Endpoint devices for hunting and detections, scoped to device groups. Collect only what you need, because extra data has cost and performance impact.

    Remember: Collect extra events only where they add detection value.

  6. 6

    Configure security policies for Microsoft Defender for Endpoint, including attack surface reduction (ASR) rules

    Manage Defender for Endpoint security settings through Intune or security settings management in the Defender portal (for devices not enrolled in Intune): antivirus, firewall, EDR and ASR rules such as blocking credential stealing from LSASS. Run ASR in audit, review events in Advanced Hunting, then block.

    Remember: Security settings management works without Intune enrolment.

  7. 7

    Manage automated investigation and response capabilities in Microsoft Defender XDR

    AIR investigates alerts automatically, gathers evidence and recommends or takes remediation actions (quarantine file, stop process, isolate device, soft-delete email). Pending actions wait in the Action center for approval unless the automation level is full. The Action center history shows what was done and allows undo.

    Remember: Approve pending remediation in the Action center.

  8. 8

    Configure automatic attack disruption in Microsoft Defender XDR

    Automatic attack disruption uses high-confidence correlated signals to stop in-progress attacks such as ransomware, business email compromise and adversary-in-the-middle, by containing devices and disabling or containing users. Prerequisites include Defender for Endpoint in automated mode, Defender for Identity, and excluding service accounts that shouldn't be contained.

    Remember: Disruption contains users and devices automatically.

  9. 9

    Configure and manage device groups, permissions, and automation levels in Microsoft Defender for Endpoint

    Device groups (by name, domain, tag or OS) set the automation level (no automated response, semi (require approval for all or some folders), or full - remediate threats automatically, recommended) and which Entra groups can see them through RBAC. Groups are evaluated in rank order; the first match wins.

    Remember: Full automation is recommended; groups match by rank.

  10. 10

    Create and configure automation rules in Microsoft Sentinel

    Automation rules run when incidents are created or updated, or alerts are created. Conditions filter by analytics rule, severity, entity and more. Actions: change status, severity or owner, add tags, add tasks, run a playbook, and set an expiry. Rules run in order.

    Remember: Automation rules: lightweight triage, then call playbooks.

  11. 11

    Create and configure Microsoft Sentinel playbooks

    Playbooks are Azure Logic Apps workflows triggered by an incident, alert or entity. They enrich (look up IP reputation), notify (Teams, email), and respond (disable a user, isolate a device). Give the Logic App a managed identity with the right permissions, and grant Sentinel the Microsoft Sentinel Automation Contributor role on the playbook's resource group.

    Remember: Sentinel needs Automation Contributor to run playbooks.

Automated response flow

  1. DetectAn analytics or custom detection rule fires.
  2. CorrelateAlerts are grouped into an incident.
  3. TriageAutomation rules set owner, severity and tags.
  4. RespondPlaybooks or AIR take action; disruption contains in-progress attacks.
  5. ReviewAction center and incident history.

Try it

Which automation feature fits?

This interactive part needs JavaScript.

In the portal

  • Email notificationsMicrosoft Defender portal: Settings > Microsoft Defender XDR > Email notifications
  • Advanced featuresMicrosoft Defender portal: Settings > Endpoints > Advanced features
  • Device groupsMicrosoft Defender portal: Settings > Endpoints > Device groups
  • Automation rulesMicrosoft Defender portal: Microsoft Sentinel > Configuration > Automation
  • Action centerMicrosoft Defender portal: Actions & submissions > Action center

Key terms

Click a card to see the definition.

Check your understanding

5 questions. Score 80% or more and these skills are marked as confident in your SC-200 study plan.

  1. Which automation level is recommended for device groups?

  2. What are Sentinel playbooks built on?

  3. What does automatic attack disruption do?

  4. Which role must Sentinel have to run playbooks in a resource group?

  5. Where do you approve remediation actions found by AIR?

Sources

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