Automation Rules for Incident Assignment and Severity in Microsoft Sentinel
A security operations team uses Microsoft Sentinel. They have a scheduled analytics rule that generates an incident when a user signs in from an unusual location. They want to automatically assign the incident to the 'Security Engineering' team and set its severity to 'High' when it is created. Which feature should they use?
Quick Answer
The answer is automation rules. This is correct because automation rules in Microsoft Sentinel provide a centralized, no-code method to automatically handle incidents upon creation, including assigning them to the 'Security Engineering' team and setting their severity to 'High' without needing a playbook or manual intervention. On the Microsoft Azure Security Engineer Associate AZ-500 exam, this question tests your understanding of how automation rules differ from playbooks—a common trap is confusing the two, since playbooks also automate responses but require Logic Apps and are better for complex, multi-step workflows. For incident assignment and severity changes triggered directly by a scheduled analytics rule, automation rules are the lightweight, native solution. Memory tip: think of automation rules as the "instant, built-in trigger" for simple actions like assignment and severity, while playbooks are the "custom, heavy-lifting" tool for advanced orchestration.
⚠ Common exam trap
Watch out — candidates often confuse playbooks with automation rules, thinking that playbooks are required for any automated action, when in fact automation rules are the native, simpler mechanism for assignment and severity changes without needing Logic Apps.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Automation rules
Automation rules in Microsoft Sentinel allow you to centrally manage the automated handling of incidents, including assigning them to a specific team and setting their severity. When a scheduled analytics rule generates an incident, an automation rule can trigger on incident creation to perform these actions without requiring a playbook or manual intervention.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Automation rules
Why this is correct
Automation rules can automatically assign incidents to a team owner and change the severity at the time of incident creation.
- ✗
Playbooks
Why it's wrong here
Playbooks are designed for automated response and remediation actions, typically triggered by incidents or alerts *after* their creation. While they can modify incident properties like severity or assignment, they do not configure these attributes *at the moment an incident is generated* by an analytics rule. This scenario demands initial property assignment. Playbooks would be the correct choice for automating subsequent steps, such as enriching an incident with external data or performing remediation actions like blocking a user in Microsoft Entra ID.
- ✗
Incident settings in analytics rule
Why it's wrong here
The analytics rule's incident settings can only set a default severity, not dynamic assignment or team ownership.
- ✗
Workbooks
Why it's wrong here
Workbooks are dashboards for data visualization; they cannot modify incidents.
Go deeper
Related to this question
About these practice questions
One of 194 original AZ-500 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
Same concept, more angles
2 more ways this is tested on AZ-500
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. A security operations team uses Microsoft Sentinel. They want to automatically assign incidents to different tiers of analysts based on severity when incidents are created. Which feature should they configure?
medium- A.Fusion - Advanced Multistage Attack Detection
- B.Analytics rules with scheduled queries
- ✓ C.Automation rules
- D.Playbooks
Why C: Automation rules in Microsoft Sentinel allow you to automatically assign incidents to specific analysts or teams based on criteria such as severity. When an incident is created, the automation rule triggers and can set the owner (assignee) to a predefined user or group, enabling tiered assignment without manual intervention.
Variation 2. A security operations team uses Microsoft Sentinel. They want to create an automation that automatically changes the severity of an incident from 'Medium' to 'High' when a specific indicator of compromise (IOC) is observed in the incident's entities. The playbook should run immediately when the incident is created. Which type of automation rule trigger should they configure?
medium- ✓ A.When incident is created
- B.When incident is updated
- C.When alert is generated
- D.Scheduled
Why A: The requirement specifies that the automation should run immediately when the incident is created. In Microsoft Sentinel, an automation rule with the trigger 'When incident is created' executes a playbook as soon as the incident is generated, before any updates occur. This allows the playbook to evaluate the incident's entities (e.g., IP addresses, hashes) and change the severity from 'Medium' to 'High' if a specific IOC is present, meeting the real-time response need.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This AZ-500 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the AZ-500 exam.