Skip to content

Commit 78dac90

Browse files
committed
naomi's comments
1 parent 265d190 commit 78dac90

File tree

1 file changed

+13
-11
lines changed

1 file changed

+13
-11
lines changed

articles/sentinel/sap/deploy-data-connector-agent-container.md

Lines changed: 13 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,7 @@ Before you deploy the data connector agent:
3838
## Watch a demo video
3939

4040
Watch one of the following video demonstrations of the deployment process described in this article.
41-
<!--can we recommend 1 only?-->
41+
4242
A deep dive on the portal options:
4343
<br><br>
4444
> [!VIDEO https://www.youtube.com/embed/bg0vmUvcQ5Q?si=hugWYn1wjlq4seCR]
@@ -240,19 +240,21 @@ While deployment is also supported from the command line, we recommend that you
240240
241241
**Prerequisites**:
242242
243-
To deploy your data connector agent via the portal, you need:
243+
- To deploy your data connector agent via the portal, you need:
244+
245+
- Authentication via a managed identitiy or a registered application
246+
- Credentials stored in an Azure Key Vault
244247
245-
- Authentication via a managed identitiy or a registered application
246-
- Credentials stored in an Azure Key Vault
248+
If you don't have these prerequisites, [deploy the SAP data connector agent from the command line](deploy-command-line.md) instead.
247249
248-
If you don't have these prerequisites, [deploy the SAP data connector agent from the command line](deploy-command-line.md) instead.
250+
- To deploy the data connector agent, you also need sudo or root privileges on the data connector agent machine.
249251
250-
If you want to ingest Netweaver/ABAP logs over a secure connection using Secure Network Communications (SNC), you need:
252+
- If you want to ingest Netweaver/ABAP logs over a secure connection using Secure Network Communications (SNC), you need:
251253
252-
- The path to the `sapgenpse` binary and `libsapcrypto.so` library
253-
- The details of your client certificate
254+
- The path to the `sapgenpse` binary and `libsapcrypto.so` library
255+
- The details of your client certificate
254256
255-
For more information, see [Configure your system to use SNC for secure connections](preparing-sap.md#configure-your-system-to-use-snc-for-secure-connections).
257+
For more information, see [Configure your system to use SNC for secure connections](preparing-sap.md#configure-your-system-to-use-snc-for-secure-connections).
256258
257259
**To deploy the data connector agent**:
258260
@@ -294,7 +296,7 @@ For more information, see [Configure your system to use SNC for secure connectio
294296
295297
:::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.":::
296298
297-
To find your VM identity object ID in Azure, go to **Enterprise application** > **All applications**, and select your VM or application name. Copy the value of the **Object ID** field to use with your copied command.
299+
To find your VM identity object ID in Azure, go to **Enterprise application** > **All applications**, and select your VM or application name. Copy the value of the **Object ID** field to use with your copied command. <!--check this with Dvir-->
298300
299301
These commands assign the **Microsoft Sentinel Business Applications Agent Operator** and **Reader** Azure roles to your VM's managed or application identity, including only the scope of the specified agent's data in the workspace.
300302
@@ -319,7 +321,7 @@ For more information, see [Configure your system to use SNC for secure connectio
319321
> The table displays the agent name and health status for only those agents you deploy via the Azure portal. Agents deployed using the command line aren't displayed here. For more information, see the [**Command line** tab](deploy-data-connector-agent-container.md?tabs=command-line) instead.
320322
>
321323
322-
1. On the VM where you plan to install the agent, open a terminal and run the **Agent deployment command** that you'd copied in the previous step.
324+
1. On the VM where you plan to install the agent, open a terminal and run the **Agent deployment command** that you'd copied in the previous step. This step requires sudo or root privileges on the data connector agent machine.
323325
324326
The script updates the OS components and installs the Azure CLI, Docker software, and other required utilities, such as jq, netcat, and curl.
325327

0 commit comments

Comments
 (0)