Skip to content

Commit 27e5b73

Browse files
authored
Update workspaces-defender-portal.md
1 parent 43caf7e commit 27e5b73

File tree

1 file changed

+0
-3
lines changed

1 file changed

+0
-3
lines changed

articles/sentinel/workspaces-defender-portal.md

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -35,9 +35,6 @@ For example, you might be working on a global SOC team in a company that has mul
3535

3636
Where you have multiple Microsoft Sentinel workspaces within a Microsoft Entra ID tenant, consider using the primary workspace for your global security operations center.
3737

38-
##
39-
Important: Prior to onboarding, customers who have IRM services enabled will be required to connect IRM to the XDR-Sentinel connector in their primary workspace. If the customer does not want to see IRM alerts and incidents in the primary workspace, IRM can be opted out of the integration with XDR. If the direct Sentinel-IRM connector is connected to any of Sentinel's secondary workspaces, the customer must disconnect it prior to onboarding.
40-
4138
## Permissions to manage workspaces and view workspace data
4239

4340
Use one of the following roles or role combinations to manage primary and secondary workspaces:

0 commit comments

Comments
 (0)