Study guide

7.6 Automation Rules and Logic Apps Playbooks

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.6 Automation Rules and Logic Apps Playbooks

Key Takeaways Explain This Topic AI

SOAR in Sentinel is delivered through automation rules and playbooks; playbooks are built on Azure Logic Apps.

A playbook is a Logic App workflow that performs response actions, such as blocking a user, isolating a device, or opening a ticket.

Automation rules centrally manage triage and orchestration and can trigger playbooks on incident or alert events.

UEBA baselines normal user/entity behavior to detect anomalies; threat intelligence enriches detections with known indicators.

Response automation comes after detection and incident context, never before data exists.

Last updated: June 2026

SOAR: Automation Rules and Playbooks

The SOAR half of Microsoft Sentinel is delivered through two related features: automation rules and playbooks . A playbook is a workflow built on Azure Logic Apps that performs response actions automatically — for example, blocking or disabling a user , isolating a device via Defender for Endpoint, posting to a Microsoft Teams or Slack channel , opening a ServiceNow ticket , or emailing an analyst for approval . Because playbooks are Logic Apps, they can connect to hundreds of connectors across Microsoft and third-party systems, which is what makes SOAR responses cross-product.

An automation rule is the orchestration and triage layer . It lets you centrally define how incidents are handled — automatically assigning an owner , setting severity or status , tagging , suppressing noise , or running one or more playbooks — and it triggers on incident or alert events. Automation rules also give you a single place to manage and order automation, instead of attaching logic to each rule individually.

  • SOAR concept Role Built on
  • Playbook Automated response workflow / action Azure Logic Apps
  • Automation rule Centralized triage and orchestration; can run playbooks Sentinel automation engine
  • Trigger What starts automation: incident created/updated, or alert Event-driven

Response automation is not the first step in the Sentinel chain. The order is: connectors ingest data, analytics rules (or hunting) detect, incidents organize the investigation, and then automation rules and playbooks coordinate the response. A scenario that wants "a repeatable action to run whenever a specific incident is created" is squarely an automation rule plus playbook answer.

UEBA, Threat Intelligence, and the SOAR Trap

Two more Sentinel capabilities round out the platform. User and Entity Behavior Analytics (UEBA) baselines normal behavior for users and entities (hosts, IPs, apps) and surfaces anomalies — for example, a user suddenly accessing resources at an unusual hour or from a new location — assigning risk to help analysts prioritize. Threat intelligence (TI) brings in indicators of compromise (malicious IPs, domains, file hashes) from Microsoft and third-party feeds via the TI connector (often TAXII/STIX ), so analytics rules can match ingested data against known-bad indicators .

Both are detection enrichments inside the same Sentinel platform; neither is a separate product.

The most common SOAR trap is choosing a Defender product for a Sentinel automation scenario, or confusing a Sentinel playbook with a study "playbook" or exam-day checklist. In this chapter a playbook is strictly an automated security response workflow on Logic Apps . Defender products protect specific surfaces (endpoints, email, identity, apps); Sentinel orchestrates response across the whole SOC and can drive Defender actions through playbook connectors.

Use this response checklist:

SIEM wording (collect, analyze, detect) -> Sentinel detection side.

SOAR wording (orchestrate, automate, respond) -> automation rules and playbooks.

"Logic Apps workflow that responds to an incident" -> playbook .

"Centrally triage and route incidents, run playbooks" -> automation rule .

"Baseline behavior and flag anomalous users" -> UEBA .

"Match activity against known malicious indicators" -> threat intelligence .

Compliance wording (labels, retention, eDiscovery) -> Microsoft Purview , not Sentinel.

For SC-900 you will not design a Logic App. Know that playbooks (Logic Apps) and automation rules deliver Sentinel's SOAR , that UEBA and threat intelligence enrich detection , and that when a question combines threat detection, incidents, and automated response across many sources, Microsoft Sentinel is the single best product match.

Why SOAR Matters and How the Pieces Fit Together

Security teams are flooded with alerts, and many response steps are repetitive: enrich an incident with extra context, notify the right people, open a ticket, and contain an obvious threat. m. In Sentinel, the division of labor is clear. Automation rules decide what should happen and to which incidents — they are the policy and triage layer that can run immediately when an incident is created or updated. Playbooks are the hands — Logic Apps workflows that carry out the concrete actions an automation rule (or an analyst) invokes.

Because playbooks are Azure Logic Apps , they tap a large library of connectors. A single playbook might call Microsoft Entra to disable a user, call Microsoft Defender for Endpoint to isolate a device, post a summary to Microsoft Teams, and create a ticket in ServiceNow — all in one orchestrated flow. Playbooks can run fully automatically or pause for human approval before taking a sensitive action, which is a common real-world pattern the exam may allude to.

  • Sentinel layer Question it answers Typical example
  • Analytics rule / hunting What is suspicious? Detect an impossible-travel sign-in
  • Incident What do we investigate? Group the related alerts and entities
  • Automation rule What should we do, and when? On creation, assign owner and run a playbook
  • Playbook (Logic Apps) How do we do it? Disable the user, notify Teams, open a ticket

UEBA and threat intelligence sit on the detection side of this picture, sharpening the signals that ultimately drive incidents and automation: UEBA finds anomalies by comparing behavior to a learned baseline, and threat intelligence flags activity that matches known-bad indicators. For SC-900, the durable lesson is the see-detect-respond chain across one platform : Sentinel sees data through connectors, detects with analytics, UEBA, and threat intelligence, organizes investigation through incidents and hunting, visualizes with workbooks, and responds through automation rules and Logic Apps playbooks .

A scenario that spans detection and automated, cross-product response is the clearest possible cue for Microsoft Sentinel.