↳ 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 that collects, stores, and forwards logs from all SAP systems, applications, and ECS services used by a registered customer. This connector streams those logs to Microsoft Sentinel in near real time, complementing SAP application-layer detections with infrastructure logs such as HANA database, SAP Web Dispatcher, OS, DNS, and Azure network flows. Standard log formats are automatically routed by the data collection rule to the matching Microsoft Sentinel tables — **Syslog**, **WindowsEvent** / **SecurityEvent**, and the ASIM-normalized tables **ASimDnsActivityLogs**, **ASimWebSessionLogs** and **ASimNetworkSessionLogs** — while SAP-specific logs remain in the **SAPLogServ_CL** custom table. Because these logs land in normalized, source-agnostic tables, they are already covered by the out-of-the-box analytic rules and hunting queries that Microsoft ships for the corresponding ASIM schemas and standard tables. To avoid duplicate alerts, those detections are intentionally **not** repackaged in this solution; only the HANA DB analytic rules — which require LogServ-specific parsing of the Syslog payload — are shipped here. Learn how normalized data reuses this built-in content in [Advanced Security Information Model (ASIM) normalization content](https://learn.microsoft.com/en-us/azure/sentinel/normalization-content).
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.
Microsoft Sentinel for SAP agentless data connector and content package (60+ analytic rules, workbooks, parsers, and more)
Deploy from Microsoft Sentinel content hub. See details [here](https://aka.ms/sentinel-sap-agentless-docs)

Connector instructions

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

1. Deploy Microsoft Sentinel agentless data connector and content for SAP
LogServ adds infrastructure logs to Microsoft Sentinel. Deploying the Microsoft Sentinel agentless data connector and content for SAP will provide you with **60+ out-of-box detections and visualizations** for your whole SAP environment. Get started from [here](https://aka.ms/sentinel-sap-agentless-docs). Learn more from [this article](https://aka.ms/sentinel-sap-logserv).
2. 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
3. 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 2Solutions/SAP LogServ/Data Connectors/SAPLogServ_PUSH_CCP/SAPLogServ_connectorDefinition.jsonsource ↗Solutions/SAP LogServ/Data/Solution_SAPLogServ.jsonsolution-membership ↗
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.