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/deploy-data-connector-agent-container.md
+7-5Lines changed: 7 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -290,7 +290,7 @@ For more information, see [Configure your system to use SNC for secure connectio
290
290
291
291
To run the commands in this step, you must be a resource group owner on your Microsoft Sentinel workspace. If you aren't a resource group owner on your workspace, this procedure can also be performed after the agent deployment is complete.
292
292
293
-
Under **Just a few more steps before we finish**, copy the *Role assignment commands* from step 1 and run them on your agent VM, replacing the `Object_ID` placeholder with your VM identity object ID. For example:
293
+
Under **Just a few more steps before we finish**, copy the *Role assignment commands* from step 1 and run them on your agent VM, replacing the `[Object_ID]` placeholder with your VM identity object ID. For example:
294
294
295
295
:::image type="content" source="media/deploy-data-connector-agent-container/finish-agent-deployment-role.png" alt-text="Screenshot of the Copy icon for the command from step 1.":::
296
296
@@ -330,7 +330,7 @@ For more information, see [Configure your system to use SNC for secure connectio
330
330
1. In the Microsoft Sentinel solution for SAP application's data connector page, in the **Configuration** area, select **Add new system (Preview)**, and then enter the following details: <!--From Naomi - It is not clear how to connect to an SAP system using ASCS. When selecting ABAP server, the solution will not connect to the SAP system, and there is no indication in the documentation what using the Message Server is, since this does not align to the SAP terminology. Update the documentation to align the terminology with SAP terms, and make it clearer what this configuration is used for - use scenarios and examples here.-->
331
331
332
332
- Under **Select an agent**, select the agent you created earlier.
333
-
- Under **System identifier**, select the server type and provide the server details.
333
+
- Under **System identifier**, select the server type and provide the server details, including the ABAP Application server IP address/FQDN, the system ID and number, and the client ID.
334
334
335
335
When you're done, select **Next: Authentication**.
336
336
@@ -343,9 +343,11 @@ For more information, see [Configure your system to use SNC for secure connectio
343
343
- For basic authentication, enter the user and password.
344
344
- If you selected an SNC connection [when you set up the agent](#deploy-the-data-connector-agent-from-the-portal-preview), select **SNC** and enter the certificate details.
345
345
346
-
1. Select **Next: Logs**.
346
+
When you're done, select **Next: Logs**.
347
347
348
-
1. On the **Logs** tab, select the logs you want to ingest from SAP, and then select **Next: Review and create**.
348
+
1. On the **Logs** tab, select the logs you want to ingest from SAP, and then select **Next: Review and create**. For example:
349
+
350
+
:::image type="content" source="media/deploy-data-connector-agent-container/logs-page.png" alt-text="Screenshot of the Logs tab in the Add new system side pane.":::
349
351
350
352
1. Review the settings you defined. Select **Previous** to modify any settings, or select **Deploy** to deploy the system.
351
353
@@ -361,7 +363,7 @@ After you deploy the SAP data connector agent, check your agent's health and con
361
363
362
364
## Next step
363
365
364
-
Once the connector is deployed, proceed to configure the Microsoft Sentinel solution for SAP applications content:
366
+
Once the connector is deployed, proceed to configure the Microsoft Sentinel solution for SAP applications content. Specifically, configuring details in the watchlists is an essential step in enabling detections and threat protection.
365
367
366
368
> [!div class="nextstepaction"]
367
369
> [Enable SAP detections and threat protection](deployment-solution-configuration.md)
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
@@ -236,7 +236,7 @@ If you attempt to retrieve an audit log without the [required configurations](pr
236
236
237
237
- Using a compatibility mode called *XAL* on older versions
238
238
- Using a version not recently patched
239
-
- Without the required change request installed <!--this doesn't quite make sense-->
239
+
- Without any changes made for connecting to the Microsoft Sentinel data connector agent. For more information, see [Configure your SAP system for the Microsoft Sentinel solution](preparing-sap.md).
240
240
241
241
While your system should automatically switch to compatibility mode if needed, you may need to switch it manually. To switch to compatibility mode manually:
0 commit comments