An enterprise runs both Microsoft Sentinel for its multicloud and third-party data and Microsoft Defender XDR for its Microsoft workload alerts, and its analysts switch between two consoles and reconcile two separate incident queues for what is often the same intrusion. Leadership wants a design where the team works a single correlated incident queue and one hunting surface that spans both the SIEM data and the XDR detections, without losing the multicloud and third-party ingestion Sentinel already provides. Which design decision best satisfies this consolidation requirement?
- ABuild a Microsoft Sentinel workbook that pulls incidents from both the Sentinel tables and the Defender XDR tables so analysts can monitor a single dashboard view of all incidents across the two products during each shift.
- BRetire Microsoft Sentinel and rely solely on Microsoft Defender XDR, re-creating the multicloud and third-party log analytics as advanced hunting queries inside the Defender portal so everything lives in one place.
- CDeploy the Microsoft Defender for Cloud connector so the cloud-workload alerts stream into Microsoft Sentinel as incidents, giving the analysts one queue in the Sentinel portal for the workload detections alongside their other sources.
- DOnboard Microsoft Sentinel into the Microsoft Defender portal as the unified security operations platform so Sentinel and Defender XDR share one correlated incident queue and one advanced hunting surface while Sentinel keeps ingesting multicloud and third-party data. Correct
Why A is wrong: A workbook can visualise incidents from both sources on one dashboard, but it is a read-only monitoring tile and does not merge the two incident queues into one investigable, actionable surface, so analysts still triage and respond in two separate consoles.
Why B is wrong: Consolidating into one portal is the goal, but removing Sentinel discards the SIEM's broad multicloud and third-party ingestion that the requirement explicitly insists on keeping, so this design loses essential coverage to achieve the single surface.
Why C is wrong: The Defender for Cloud connector brings cloud-workload alerts into Sentinel, but it addresses only one alert source and leaves the broader Defender XDR endpoint and identity incidents in their own portal, so the dual-console and dual-queue problem remains.
Why D is correct: Onboarding Sentinel into the Defender portal delivers Microsoft's unified security operations platform, presenting a single correlated incident queue and one advanced hunting experience across SIEM and XDR data while Sentinel continues to ingest the multicloud and third-party sources, which satisfies every part of the requirement.