You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/sentinel/sap/preparing-sap.md
+14-6Lines changed: 14 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -189,17 +189,25 @@ For more information, see [Database Collector in Background Processing](https://
189
189
190
190
For more information, see the [SAP documentation](https://help.sap.com/docs/integration-suite/sap-integration-suite/initial-setup).
191
191
192
-
## Perform initial connector configuration
192
+
## Configure the connector in Microsoft Sentinel and in your SAP system
193
193
194
-
This procedure starts in Microsoft Sentinel and requires that the solution be installed before you start.
194
+
This procedure has steps both in Microsoft Sentinel and your SAP system, and requires coordination with the SAP administrator.
195
195
196
-
1. In Microsoft Sentinel, go to the **Configuration > Data connectors** page and locate the **Microsoft Sentinel for SAP - agent-less (Preview)** data connector.
196
+
1. In Microsoft Sentinel, go to the **Configuration > Data connectors** page and locate the **Microsoft Sentinel for SAP - agentless (Preview)** data connector.
197
197
198
-
1. In the **Configuration** area, expand and follow the instructions in the **Initial connector configuration - Run the steps below once:** area. These steps will require a mixture of your Security and SAP BASIS teams.
198
+
1. In the **Configuration** section, expand and follow the instructions in the **Initial connector configuration - Run the steps below once:** section. These steps will require both your SecuritySOC engineer and the SAP admin.
199
+
1. Trigger automatic deployment of Azure resources (SOC Engineer).
200
+
If, after you deploy the Azure resources, the values in the steps 2 and 3 aren't automatically populated, close and re-expand step 1 to refresh the values in steps 2 and 3.
201
+
1. Deploy an OAuth2 client credentials artifact in the SAP Integration (SAP Admin).
202
+
1. Deploy the SAP agentless data connector package to the SAP Integration Suite (SAP Admin).
203
+
1. Download the [integration package](https://aka.ms/SAPAgentlessPackage) and upload it to your SAP Integration Suite. For more information, see the [SAP documentation](https://help.sap.com/docs/integration-suite/sap-integration-suite/importing-integration-packages).
204
+
1. Open the package and go to the **Artifacts** tab. Then select the **Data Collector** configuration. For more information, see the [SAP documentation](https://help.sap.com/docs/integration-suite/sap-integration-suite/importing-integration-packages).
205
+
1. Configure the integration flow with the **LogIngestionURL** and the **DCRImmutableID**.
206
+
1. Deploy the i-flow using SAP Cloud Integration as the runtime service.
199
207
200
-
If, after you deploy the Azure resources step 1, the values in the steps 2 and 3 aren't automatically populated, close and re-expand step 1 to refresh the values in steps 2 and 3.
201
208
202
-
1. Included in the package is **Prerequisite checker** iflow. We recommend running this iflow before continuing to the next step to ensure that your SAP system meets the system prerequisites.
209
+
## Run the prerequisite checker
210
+
1. The **Prerequisite checker** iflow is included in the package. We recommend running this iflow before continuing to the next step to ensure that your SAP system meets the system prerequisites.
Copy file name to clipboardExpand all lines: articles/sentinel/sap/sap-deploy-troubleshoot.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,7 +29,7 @@ If you don't see a related error to your issue, turn on trace logging for more i
29
29
30
30
## Check for prerequisites
31
31
32
-
The agentless data connector package, deployed while [performing the initial connector configuration](preparing-sap.md#perform-initial-connector-configuration), includes a tool to help SAP admins diagnose and fix issues related to the SAP environment configuration.
32
+
The agentless data connector package, deployed while [performing the initial connector configuration](preparing-sap.md#configure-the-connector-in-microsoft-sentinel-and-in-your-sap-system), includes a tool to help SAP admins diagnose and fix issues related to the SAP environment configuration.
Copy file name to clipboardExpand all lines: articles/sentinel/whats-new.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -106,7 +106,7 @@ The Microsoft Sentinel agentless data connector for SAP and related security con
106
106
-**Enhanced instructions** in the portal for deploying and configuring the data connector. [External documentation](sap/preparing-sap.md#next-step) is updated to rely on the instructions in the portal.
107
107
-**[More data ingested](sap/sap-solution-log-reference.md)**, such as Change Docs logs and User Master data.
108
108
-**Optional parameters** to [Customize data connector behavior (optional)](sap/deploy-data-connector-agent-container.md#customize-data-connector-behavior-optional).
109
-
-[**A new tool to verify system prerequisites and compatibility**](sap/preparing-sap.md#perform-initial-connector-configuration), recommended both before deploying and when [troubleshooting](sap/sap-deploy-troubleshoot.md#check-for-prerequisites).
109
+
-[**A new tool to verify system prerequisites and compatibility**](sap/preparing-sap.md#configure-the-connector-in-microsoft-sentinel-and-in-your-sap-system), recommended both before deploying and when [troubleshooting](sap/sap-deploy-troubleshoot.md#check-for-prerequisites).
0 commit comments