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
+5-1Lines changed: 5 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -198,7 +198,9 @@ This procedure has steps both in Microsoft Sentinel and your SAP system, and req
198
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
199
1. Trigger automatic deployment of Azure resources (SOC Engineer).
200
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).
201
+
1. Deploy an OAuth2 client credentials artifact in the SAP Integration (SAP Admin).
202
+
1. Deploy a Secure Parameter artifact in SAP Integration (SAP Admin) named **workspaceKey** containing the Log Analytics workspace key visible in the data connector UI.
203
+
202
204
1. Deploy the SAP agentless data connector package to the SAP Integration Suite (SAP Admin).
203
205
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
206
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).
@@ -235,6 +237,8 @@ This procedure has steps both in Microsoft Sentinel and your SAP system, and req
235
237
236
238
-**SIAG_ROLE_GET_AUTH**, to retrieve security role authorizations
237
239
240
+
-**/OSP/SYSTEM_TIMEZONE**, to retrieve SAP system timezone details
241
+
238
242
1. Add a new destination in SAP BTP that points the virtual host you'd created earlier. Use the following details to populate the new destination:
239
243
240
244
-**Name:** Enter the name you want to use for the Microsoft Sentinel connection
0 commit comments