Question 110
A Microsoft Azure administrator receives this requirement: A SOC investigates role assignments but sees no Azure subscription management activity in Sentinel despite collecting VM system logs. What is the most appropriate corrective step?
Explanation
Correct Answer
The cause is: Guest operating system telemetry does not automatically include the Azure subscription Activity Log that tracks control-plane actions. The appropriate change is: Configure the supported Azure Activity connector and required subscription diagnostic or policy associations to the selected workspace. Verify it with this outcome: An authorized test role assignment creates a searchable subscription activity record in Sentinel.
Incorrect Answers
This action concerns sentinel data retention investigation needs, where Security investigation capability depends on applicable Log Analytics retention configuration and compliant data governance. The reported incident instead involves Guest operating system telemetry does not automatically include the Azure subscription Activity Log that tracks control-plane actions.
This action concerns sentinel incident investigation timeline, where Incident titles alone cannot establish benign behavior; entities, event timestamps and correlated evidence require investigation. The corrective response here is “Configure the supported Azure Activity connector and required subscription diagnostic or policy associations to the selected workspace”; this alternative does not provide that response.
This action concerns sentinel workspace onboarding, where A Log Analytics workspace stores supported telemetry but must be enabled and configured for Microsoft Sentinel capabilities. The stem reports a SOC investigates role assignments but sees no Azure subscription management activity in Sentinel despite collecting VM system logs; this control addresses a different failure condition.