Microsoft Entra role: Security Reader; Azure role: Microsoft Sentinel Responder

Assigning incidents requires Sentinel incident-management permissions, which are provided by Microsoft Sentinel Responder at the workspace scope. Because the consultant is a guest user, Security Reader in Microsoft Entra gives the security-reader context commonly needed for security operations visibility without granting administrative tenant privileges. Sentinel Reader alone would allow viewing but not assignment. Contributor-level Azure roles would be broader than necessary. In Microsoft Sentinel and Defender scenarios, collection, detection, investigation, and automation are separate functions. The selected answer maps to the function requested by the question rather than a neighboring capability. This is why analytics, hunting, workbooks, connectors, automation rules, and playbooks must not be treated as interchangeable. The result is a direct exam-style implementation choice: it changes the required security behavior without relying on unrelated monitoring, manual cleanup, or excessive privilege. Official Microsoft source/topic: SC-500 Study Guide > Assign roles in Microsoft Sentinel; Microsoft Learn > Microsoft Sentinel built-in roles.

==============================================================