Skip to content

Commit 6228925

Browse files
authored
Fix casing of primary in Sentinel in portal article
1 parent 147d737 commit 6228925

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/sentinel/microsoft-sentinel-defender-portal.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -64,7 +64,7 @@ This section covers the Microsoft Sentinel capabilities or integrations that are
6464
| Incidents: Programmatic and manual creation of incidents | Azure portal only | Incidents created in Microsoft Sentinel through the API, by a Logic App playbook, or manually from the Azure portal, aren't synchronized to the Defender portal. These incidents are still supported in the Azure portal and the API. See [Create your own incidents manually in Microsoft Sentinel](create-incident-manually.md). |
6565
| Incidents: Reopening closed incidents | Azure portal only | In the Defender portal, you can't set alert grouping in Microsoft Sentinel analytics rules to reopen closed incidents if new alerts are added. <br>Closed incidents aren't reopened in this case, and new alerts trigger new incidents. |
6666
| Incidents: Tasks | Azure portal only | Tasks are unavailable in the Defender portal. <br><br>For more information, see [Use tasks to manage incidents in Microsoft Sentinel](incident-tasks.md). |
67-
| Multiple workspace management for Microsoft Sentinel | Defender portal: Manage a primary workspace and multiple secondary workspaces for a tenant. <br><br>Azure portal: Centrally manage multiple Microsoft Sentinel workspaces for tenants | The Defender portal allows you to connect to one primary workspace and multiple secondary workspaces for Microsoft Sentinel. A Primary workspace's alerts are correlated with Defender XDR data, which results in incidents that include alerts from Microsoft Sentinel's primary workspace and Defender XDR. All other onboarded workspaces are considered secondary workspaces.<br><br> For more information, see the following articles:<br>- Defender portal: [Multiple Microsoft Sentinel workspaces in the Defender portal](workspaces-defender-portal.md)<br>- Azure portal: [Manage multiple Microsoft Sentinel workspaces with workspace manager](/azure/sentinel/workspace-manager)|
67+
| Multiple workspace management for Microsoft Sentinel | Defender portal: Manage a primary workspace and multiple secondary workspaces for a tenant. <br><br>Azure portal: Centrally manage multiple Microsoft Sentinel workspaces for tenants | The Defender portal allows you to connect to one primary workspace and multiple secondary workspaces for Microsoft Sentinel. A primary workspace's alerts are correlated with Defender XDR data, which results in incidents that include alerts from Microsoft Sentinel's primary workspace and Defender XDR. All other onboarded workspaces are considered secondary workspaces.<br><br> For more information, see the following articles:<br>- Defender portal: [Multiple Microsoft Sentinel workspaces in the Defender portal](workspaces-defender-portal.md)<br>- Azure portal: [Manage multiple Microsoft Sentinel workspaces with workspace manager](/azure/sentinel/workspace-manager)|
6868

6969
## Limited or unavailable capabilities
7070

0 commit comments

Comments
 (0)