↳ GitHub sourceConnector

SAP LogServ (RISE), S/4HANA Cloud private edition

An inconsistency was detected in the sources: variants or an invalid file. Check the files and commit shown below.

Description

SAP LogServ is an SAP Enterprise Cloud Services (ECS) service aimed at collection, storage, forwarding and access of logs. LogServ centralizes the logs from all systems, applications, and ECS services used by a registered customer. <br> Main Features include:<br>Near Realtime Log Collection: With ability to integrate into Microsoft Sentinel as SIEM solution.<br>LogServ complements the existing SAP application layer threat monitoring and detections in Microsoft Sentinel with the log types owned by SAP ECS as the system provider. This includes logs like: SAP Security Audit Log (AS ABAP), HANA database, AS JAVA, ICM, SAP Web Dispatcher, SAP Cloud Connector, OS, SAP Gateway, 3rd party Database, Network, DNS, Proxy, Firewall<br><br>**ASIM-Enabled Routing:** Standard log formats (Linux/Syslog, Windows OS, DNS, network, web access) are automatically routed to dedicated Microsoft ASIM-normalized tables via DCR data flow branching, enabling reuse of existing detections and partner analytics. SAP Security Audit Log (AS ABAP) is routed to the Microsoft standard **ABAPAuditLog** table. SAP-specific logs remain in the SAPLogServ_CL custom table.
Declared author / publisher
SAP SE

Declared sources

Metadata from the source file. No dependencies inferred from KQL.

Data types

Declared permissions

Read and Write permissions are required.
Workspace
Workspace
Read permissions to shared keys for the workspace are required. [See the documentation to learn more about workspace keys](https://docs.microsoft.com/azure/azure-monitor/platform/agent-windows#obtain-workspace-id-and-key)
Keys
Workspace
Microsoft Entra
Permission to create an app registration in Microsoft Entra ID. Typically requires Entra ID Application Developer role or higher.
Microsoft Azure
Permission to assign Monitoring Metrics Publisher role on data collection rules. Typically requires Azure RBAC Owner or User Access Administrator role.

Connector instructions

Content published in the repository. Refer to the original file for all parameters.

1. Create ARM Resources and Provide the Required Permissions
We will create data collection rule (DCR) and data collection endpoint (DCE) resources. We will also create a Microsoft Entra app registration and assign the required permissions to it.
Deploy push connector resources
2. Maintain the data collection endpoint details and authentication info in SAP LogServ
Share the data collection endpoint URL and authentication info with the SAP LogServ administrator to configure the SAP LogServ to send data to the data collection endpoint. Learn more from [this blog series](https://community.sap.com/t5/enterprise-resource-planning-blog-posts-by-members/ultimate-blog-series-sap-logserv-integration-with-microsoft-sentinel/ba-p/14126401).
Use this value to configure as Tenant ID in the LogIngestionAPI credential.
Entra Application ID
Entra Application Secret
Use this value to configure the LogsIngestionURL parameter when deploying the IFlow.
DCR Immutable ID

Related content

Links established from declared identifiers and solution manifests.

Source provenance

GitHub

Displayed values come from files in Azure/Azure-Sentinel. They describe the published template, not your workspace configuration.

Source identifier
SAPLogServ
Additional source files 1Solutions/SAP LogServ/Data Connectors/SAPLogServ.jsonsource ↗
GSTEP / CATALOG TRACKING

Added to catalog : 16 Sept 2026 · 05:49 UTC
Last change observed : 16 Sept 2026 · 05:49 UTC

GSTEP sync dates, separate from the source content’s publication dates.