Skip to content

Commit 11ff9ad

Browse files
authored
changed files by pdets auto publish service, publishid[f48aa130-c78f-44af-8ca2-34bd9faefd99] and do [publish].
1 parent c7544b4 commit 11ff9ad

File tree

1 file changed

+1
-0
lines changed

1 file changed

+1
-0
lines changed

learn-pr/wwl-azure/secure-sap-microsoft-cloud/includes/4-microsoft-sentinel-security-rise.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -10,6 +10,7 @@ The solution allows you to gain visibility to user activities on SAP RISE/ECS an
1010
- Visualize the data with [built-in workbooks](/azure/sentinel/sap/sap-audit-log-workbook).
1111

1212
:::image type="content" source="../media/sap-rise-sentinel.png" alt-text="Diagram that shows how to connect Microsoft Sentinel with SAP RISE/ECS." lightbox="../media/sap-rise-sentinel.png":::
13+
1314
This diagram shows an example of Microsoft Sentinel connected through an intermediary VM or container to SAP managed SAP system. The intermediary VM or container runs in customer's own subscription with configured SAP data connector agent. Connection to SAP Business Technology Platform (BTP) uses SAP's public APIs for the Audit Log Management Service.
1415

1516
For SAP RISE/ECS, the Microsoft Sentinel solution must be deployed in customer's Azure subscription. All parts of the Microsoft Sentinel solution are managed by customer and not by SAP. Private network connectivity from customer's vnet is needed to reach the SAP landscapes managed by SAP RISE/ECS. Typically, this connection is over the established vnet peering or through alternatives described in this document.

0 commit comments

Comments
 (0)