Skip to content

Commit 4b61987

Browse files
authored
Update workspaces-defender-portal.md
1 parent b8089e2 commit 4b61987

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/sentinel/workspaces-defender-portal.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ This article primarily applies to the scenario where you onboard Microsoft Senti
2222

2323
Select your primary workspace when you onboard Microsoft Sentinel to the Defender portal. Any other workspaces that you onboard to the Defender portal are considered as secondary workspaces. The Defender portal supports one primary workspace and up to 99 secondary workspaces per tenant for Microsoft Sentinel.
2424

25-
When you also have Microsoft Defender XDR, alerts from your primary workspace are correlated with Defender XDR data, and incidents include alerts from both your primary workspace and Defender XDR in a unified queue.
25+
When you also have Microsoft Defender XDR, alerts from your primary workspace are correlated with Defender XDR data, and incidents include alerts from both your primary workspace and Defender XDR in a unified queue. When you select a primary workspace, the [Defender XDR data connector](connect-microsoft-365-defender.md) for incidents and alerts is connected to the primary workspace only. Any other workspaces that were previously connected to the Defender XDR connector are disconnected. Any legacy Defender XDR data connectors are disconnected for all workspaces.
2626

2727
In such cases:
2828

0 commit comments

Comments
 (0)