Skip to content

Commit 39a6964

Browse files
committed
Merge branch 'andrelom-docsv2.1' of https://github.com/MSFTandrelom/azure-docs-pr into andrelom-docsv2.1
2 parents c41dc9d + 15836e9 commit 39a6964

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,7 @@ Deployment of the SAP continuous threat monitoring solution is divided into the
3939

4040
For the Continuous Threat Monitoring solution for SAP to operate correctly, data must first be ingested from SAP system into Microsoft Sentinel. To accomplish this, you need to deploy the Continuous Threat Monitoring solution for SAP data connector agent.
4141

42-
The data connector agent runs as a container on a Linux virtual machine (VM). This VM can be hosted either in Azure, in a third-party cloud, or on-premises. The recommended way for you to install and configure this container is by using a *kickstart* script, however you can choose do deploy the container [manually](?tabs=deploy-manually)
42+
The data connector agent runs as a container on a Linux virtual machine (VM). This VM can be hosted either in Azure, in a third-party cloud, or on-premises. The recommended way for you to install and configure this container is by using a *kickstart* script, however you can choose to deploy the container [manually](?tabs=deploy-manually)
4343

4444
The agent connects to your SAP system to pull logs and other data from it, then sends those logs to your Microsoft Sentinel. To do this, the agent has to authenticate to your SAP system - that's why you created a user and a role for the agent in your SAP system in the previous step.
4545

@@ -100,7 +100,7 @@ If not, then your SAP configuration and authentication secrets can and should be
100100
101101
1. Copy the **systemAssignedIdentity** GUID, as it will be used in the coming steps.
102102
103-
1. Run the following commands to **create a key vault** (substitute actual names for the `<placeholders>`). If you'll be using an existing key vault, ignore this step :
103+
1. Run the following commands to **create a key vault** (substitute actual names for the `<placeholders>`). If you'll be using an existing key vault, ignore this step:
104104
105105
```azurecli
106106
az keyvault create \

0 commit comments

Comments
 (0)