Skip to content

Commit f7bb251

Browse files
committed
raise acrolinx score
1 parent c3fa3bc commit f7bb251

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

articles/sentinel/includes/sap-agentless-prerequisites.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ ms.topic: include
99
**To run the tool**:
1010

1111
1. Open the integration package, navigate to the artifacts tab, and select the **Prerequisite checker** iflow > **Configure**.
12-
1. Set the target RFC destination to the SAP system you want to check.
12+
1. Set the target destination name for the remote function call (RFC) to the SAP system you want to check. For example, `A4H-100-Sentinel-RFC`.
1313
1. Deploy the iflow as you would otherwise for your SAP systems.
1414
1. Trigger the iflow from any REST client. For example, use the following sample PowerShell script, modifying the sample placeholder values for your environment:
1515

@@ -40,4 +40,4 @@ ms.topic: include
4040
4141
Make sure that the prerequisites checker runs successfully (status code 200) with no warnings on the response output before connecting to Microsoft Sentinel.
4242
43-
In case of any findings, consult the response details for guidance on remediation steps. Legacy systems typically require additional SAP notes. Furthermore, see the [troubleshooting section](../sap/sap-deploy-troubleshoot.md) for common issues and resolutions.
43+
If any findings, consult the response details for guidance on remediation steps. Legacy SAP systems often require extra SAP notes. Furthermore, see the [troubleshooting section](../sap/sap-deploy-troubleshoot.md) for common issues and resolutions.

0 commit comments

Comments
 (0)