Microsoft Sentinel
Troubleshooting

Troubleshoot the Microsoft Sentinel solution for SAP applications agentless data connector | Microsoft Learn

In brief

The article now includes troubleshooting paths by symptom, diagnostic information to collect, an ABAPAuditLog query, and guidance on SAP releases, audit-log performance, delayed ingestion, user-data ingestion cycles, and time-zone offsets.

What Defender admins need to know

Administrators can use the new checks and query to more quickly isolate connector, SAP, and ingestion issues.

Summaries are generated from the documentation change itself.

Documentation change

The comparison below shows only the changed extract. Use the full-page view for complete context.

Troubleshoot the Microsoft Sentinel solution for SAP applications agentless data connector | Microsoft Learn

This article includesTrace problems from Microsoft Sentinel through SAP Cloud Integration and SAP Cloud Connector to the SAP system. Start with the affected SAP system ID (SID), the UTC time range, and the SAP Cloud Integration message processing log.

Choose a troubleshooting steps to helppath

SymptomFirst check
You can't deploy Azure resources or connect an SAP systemCheck deployment permissions or follow the connection procedure.
The connector is connected, but SAP calls fail or return no logsFind the failed SID and exact error in the SAP Cloud Integration message processing log, then see SAP release and audit log corrections.
Onboarding or log reads are slow or time outRun the Prerequisite checker and identify which downstream call is slow; see timeouts and filesystem-backed audit logs.
Logs are missing for a time range or arrive lateCompare the failed UTC collection window with the source records; check time zone settings and retries.
User or role data is incompleteCheck the configured full-ingestion cycle and user master data guidance.

When you ensure accurate and timely data ingestion and monitoring forcontact your SAP environment with Microsoft Sentinel.BASIS or SAP Cloud Integration administrator, include the SID, UTC time range, message processing log error and timestamp, SAP_BASIS release and support package, and (for audit-log issues) the configured recording target. Don't include credentials or client secrets.

When working with theTo confirm agentless data connector, most troubleshooting is done directly inaudit-log ingestion, check the SAP Cloud Integration Suite, where the message log displays errors indicating the nature of the issue encountered.

Start by examining the message processing logs. log for a successful Data Collector run, then query the ABAPAuditLog table:

ABAPAuditLog
| where TimeGenerated > ago(1h)
| summarize Records = count() by SourceSystem, bin(TimeGenerated, 5m)
| order by TimeGenerated desc

For more information, seedelayed records, change the SAP documentation. The error messages there can help you diagnose issues with missing permissions, connectivity errors, and other misconfigurations.

If you donquery't see a related errors time filter to your issue, turn on trace logging for more in-depth troubleshooting. For more information, see the SAP documentation.affected collection interval. Check that interval rather than only checking the newest records.

Check for prerequisites

Undeploy the scheduled Prerequisite checker iflow once SAP system check was completed successfully. Repeat this sequence for every new SAP system that shall be onboarded.

Missing functionalitySAP release and audit log corrections

SAP_BASIS 7.50 is the minimum supported release. SAP's OData API for Security Audit Log integration with SIEM is available only for S/4HANA Cloud Public Edition, and SAP hasn't indicated that it will be downported to Private Edition. Therefore, RFC-enabled extraction remains mandatory for systems outside Public Edition, despite SAP Notes that advise against RFC-based integration. The remote audit log API is available in legacy SAP systems

Some legacy SAP systems may be missingthis release, but the required functionality formight depend on the installed support package and corrections. If SAP Cloud Integration logs show an RFC_READ_TABLE function module. Make sure thaterror, ask your SAP admin has reviewedBASIS administrator to check SAP Note 2246160 for release-specific enhancements.

For slow or incomplete reads of file-based audit logs, see SAP Note 3407647, which describes file-selection performance and related runtime errors. If the audit log is configured for both filesystem and database recording, SAP Note 3726943 documents an API option to select filesystem data only. SAP notes 3390051Notes have release-specific validity and 382318, and has patchedprerequisites. Ask SAP to confirm whether the correction chain applies to your system accordingly.before changing its configuration.

For more information, see Configure SAP Cloud Connector settings.

Incomplete SAP user master data

Long-running SAP ERP systems can have large volumes of user master data. To maintain stability, the agentless data connector spreads full user master data ingestion, including users and roles, over seven days by default. During this cycle, incomplete data doesn't necessarily indicate a collection failure. Allow the configured cycle to complete before assessing whether the full dataset is present. The ingestion-cycle-days parameter controls this duration and doesn't affect ingestion of changes to user master data. For configuration details, see Customize data connector behavior.

If you see an error that you have incomplete SAP user master data or no data in the ABAPAuthorizationDetails Microsoft Sentinel table, do the following:

  1. Confirm that the SIAG_ROLE_GET_AUTH SAP function module exists in the SAP source system.

Note that log filters on NetWeaver impact what is written to the audit log on the source while a filter on SAP Cloud Integration only chooses not to read the problematic entries.

Missing SAP logs due to SAP time zone settings

Microsoft Sentinel requests audit log time slices in UTC. The agentless data connector uses the SAP /OSP/SYSTEM_TIMEZONE function module to retrieve SAP time zone details and determine the offset for audit log collection. If expected logs are missing, first ask your SAP administrator to identify the Security Audit Log recording target and verify the SAP system and RFC user time zones. For file-based logs, also confirm how the source timestamps are recorded; don't assume that the host operating system time is the timestamp basis.

If your checks indicate an offset mismatch, you can test force-utc to use a zero offset instead of the offset retrieved from SAP. Compare the returned source interval and ingested event timestamps before and after the change; the override doesn't change SAP time zone settings. The offset-in-seconds parameter is a separate look-back buffer: with its default of 60 seconds, a request for 10:01 to 10:02 UTC selects the source interval from 10:00 to 10:01 UTC. Changing force-utc doesn't disable this shift. For configuration details, see Customize data connector behavior.

Intermittent failures in the SAP logging pipeline

Brief network interruptions, SAP system downtime, or temporary resource constraints can cause a collection request to fail. The agentless data connector automatically retries failed collection windows, so a failed request doesn't immediately mean that logs are permanently lost.

If Microsoft Sentinel integration requests time out during connector onboarding or ongoing log reads, review how your SAP Security Audit Log is recorded and retrieved, especially when recording is configured as Filesystem and database.

Selecting auditUse the prerequisite checker to determine whether the delay is in SAP audit-log retrieval before changing settings. Reading filesystem-backed logs fromcan be slow when the directory contains many files, when files don't use the classic naming pattern, or when files are on NFS storage. SAP HANA database often providesNote 3407647 describes these conditions and the best performance. Other databases and filesystem-backed selection might require tuning.ID_FILE_SEL_SIMPLE option for systems that use the classic file pattern.

To remediate:

  1. Confirm withIf filesystem-only retrieval is appropriate for your SAP administrator whether Security Audit Log recording targets includeconfiguration, the force-sal-filesystem connector setting requests filesystem storage.
  2. Implement following SAP notes byselection usingSNOTE or by importing the referenced support package (applies to SAP_BASIS 750+):
    • 3726943 - RSAU_API_GET_LOG_DATA | Dataselection only from Filesystem details
    • 3407647 - RSAU_READ_LOG | Optimization of reading audit log files
  3. After implementing the correction, use filesystem-only selection with required parameters ID_FILESYSTEM_SEL_ONLY and ID_FILE_SEL_SIMPLE. The SAP corrections that provide these parameters are described in Notes 3726943 and 3407647; simplified file selection is intended for faster retrieval. For behavior detailsthe classic file naming pattern. Confirm the corrections and explanation, seeconfiguration with SAP note 3500090.
  4. Re-run connector validation.
for your release before enabling the setting, then compare the runtime and returned records for the same collection window.

Applying these SAP notes often improves retrieval performance significantly. If delays continue, they're typically related to SAP-side factors such as log shipping betweencheck SAP short dumps and the SAP Cloud Integration message processing log. SAP also recommends keeping each application serversserver's audit files in its own directory and network latency.avoiding NFS locations; have your SAP administrator verify the configuration with SAP.

SAP Cloud Connector sizing, throughput, and isolation guidance