Skip to content

Commit 2a9a123

Browse files
committed
fixing link
1 parent c3b7e25 commit 2a9a123

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/sentinel/sap/cross-workspace.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ ms.date: 03/22/2023
1111

1212
# Work with the Microsoft Sentinel solution for SAP applications in multiple workspaces
1313

14-
When you set up your Microsoft Sentinel workspace, you have [multiple architecture options](../../azure-monitor/logs/workspace-design?toc=/azure/sentinel/TOC.json&bc=/azure/sentinel/breadcrumb/toc.json) and factors to consider. Taking into account geography, regulation, access control, and other factors, you might choose to have multiple Microsoft Sentinel workspaces in your organization.
14+
When you set up your Microsoft Sentinel workspace, you have [multiple architecture options](/azure/azure-monitor/logs/workspace-design?toc=/azure/sentinel/TOC.json&bc=/azure/sentinel/breadcrumb/toc.json) and factors to consider. Taking into account geography, regulation, access control, and other factors, you might choose to have multiple Microsoft Sentinel workspaces in your organization.
1515

1616
This article discusses how to work with the Microsoft Sentinel solution for SAP applications in multiple workspaces for different deployment scenarios.
1717

@@ -58,7 +58,7 @@ Creating separate workspaces for the SAP and SOC data has these benefits:
5858
5959
- The SAP team has its own Microsoft Sentinel workspace that includes all features except detections that include both SOC and SAP data.
6060
- Flexibility. The SAP team can focus on the control of internal threats in its landscape, and the SOC can focus on external threats.
61-
- There's no additional charge for ingestion fees, because data is ingested only once into Microsoft Sentinel. However, each workspace has its own [pricing tier](../../azure-monitor/logs/workspace-design#step-5-collecting-any-non-soc-data?toc=/azure/sentinel/TOC.json&bc=/azure/sentinel/breadcrumb/toc.json).
61+
- There's no additional charge for ingestion fees, because data is ingested only once into Microsoft Sentinel. However, each workspace has its own [pricing tier](/azure/azure-monitor/logs/workspace-design#step-5-collecting-any-non-soc-data?toc=/azure/sentinel/TOC.json&bc=/azure/sentinel/breadcrumb/toc.json).
6262
- The SOC can see and investigate SAP incidents. If the SAP team faces an event that it can't explain by using existing data, the team can assign the incident to the SOC.
6363

6464

0 commit comments

Comments
 (0)