Question 920
The cloud operations team reviews the following risk: Security analysts can query VM logs but cannot investigate anomalous Microsoft Entra sign-ins because identity logs are absent. Which explanation fits the observed symptoms most closely?
Explanation
Correct Answer
The described technical condition is: Microsoft Entra sign-in audit events need the appropriate supported connector or diagnostic routing and access permissions. The appropriate corrective action is: Configure the supported Entra sign-in log integration into Sentinel and verify enabled categories and consent. Confirm with: A controlled test sign-in yields searchable identity event fields in the approved workspace.
Incorrect Answers
A DCR's configured destination governs where eligible telemetry is sent, regardless of the analyst's preferred query workspace. “Correct the authorized Log Analytics destination or workspace query scope while preserving the intended data source filters” would address that alternative cause, not the condition in this question: microsoft Entra sign-in audit events need the appropriate supported connector or diagnostic routing and access permissions.
“Review rule order, matching conditions and any stop-processing behavior, then move the precise severity rule ahead of broad disposition” responds to this separate finding: automation rule ordering and stopping behavior can prevent more specific rules from executing as intended. This question instead needs “Configure the supported Entra sign-in log integration into Sentinel and verify enabled categories and consent”, so the alternative does not meet the stated condition.
Workbooks visualize queried telemetry but do not replace enabled analytic rules or explicit alert workflows. “Create and enable an appropriate Sentinel analytic rule for the suspicious traffic pattern while retaining the dashboard for context” applies to that separate problem. The observed case is security analysts can query VM logs but cannot investigate anomalous Microsoft Entra sign-ins because identity logs are absent; choosing this alternative would address the wrong failure mode.