Skip to content

Commit d9ad9f1

Browse files
committed
dvir's comments
1 parent ad33b7c commit d9ad9f1

File tree

3 files changed

+6
-7
lines changed

3 files changed

+6
-7
lines changed

articles/sentinel/sap/deploy-command-line.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -133,9 +133,11 @@ This procedure describes how to create a new agent and connect it to your SAP sy
133133
134134
Replace placeholder values as follows:
135135
136+
To find your VM identity object ID in Azure:
137+
136138
|Placeholder |Value |
137139
|---------|---------|
138-
|`<OBJ_ID>` | Your VM identity object ID. <br><br> To find your VM identity object ID in Azure, go to **Enterprise application** > **All applications**, and select your VM or registered application name. Copy the value of the **Object ID** field to use with your copied command. |
140+
|`<OBJ_ID>` | Your VM identity object ID. <br><br> To find your VM identity object ID in Azure: For a managed identity, the object ID is listed on the VM's **Identity** page. For a service principal, go to **Enterprise application** in Azure. Select **All applications** and then select your VM. The object ID is displayed on the **Overview** page. |
139141
|`<SUB_ID>` | Your Microsoft Sentinel workspace subscription ID |
140142
|`<RESOURCE_GROUP_NAME>` | Your Microsoft Sentinel workspace resource group name |
141143
|`<WS_NAME>` | Your Microsoft Sentinel workspace name |
@@ -218,7 +220,7 @@ Azure Key Vault is the recommended method to store your authentication credentia
218220
219221
|Placeholder |Value |
220222
|---------|---------|
221-
|`<OBJ_ID>` | Your VM identity object ID. <br><br> To find your VM identity object ID in Azure, go to **Enterprise application** > **All applications**, and select your VM or application name, depending on whether you're using a managed identity or a registered application. <br><br>Copy the value of the **Object ID** field to use with your copied command. |
223+
|`<OBJ_ID>` | Your VM identity object ID. <br><br> To find your VM identity object ID in Azure: For a managed identity, the object ID is listed on the VM's **Identity** page. For a service principal, go to **Enterprise application** in Azure. Select **All applications** and then select your VM. The object ID is displayed on the **Overview** page. |
222224
|`<SUB_ID>` | Your Microsoft Sentinel workspace subscription ID |
223225
|`<RESOURCE_GROUP_NAME>` | Your Microsoft Sentinel workspace resource group name |
224226
|`<WS_NAME>` | Your Microsoft Sentinel workspace name |

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

Lines changed: 1 addition & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -298,10 +298,7 @@ While deployment is also supported from the command line, we recommend that you
298298
299299
To find your VM identity object ID in Azure:
300300
301-
- For a managed identity, the object ID is listed on the VM's **Identity** page. Alternately:
302-
303-
1. Go to **Managed identities** select your managed identity.
304-
1. For user-assigned identities, the object ID is displayed on the **Overview** page. For system-assigned managed identities, the object ID is displayed on the **Identity** page.
301+
- For a managed identity, the object ID is listed on the VM's **Identity** page.
305302
306303
- For a service principal, go to **Enterprise application** in Azure. Select **All applications** and then select your VM. The object ID is displayed on the **Overview** page.
307304

articles/sentinel/sap/preparing-sap.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -63,7 +63,7 @@ For more information, see the [SAP documentation](https://help.sap.com/docs/ABAP
6363

6464
Some installations of SAP systems might not have audit logging enabled by default. For best results in evaluating the performance and efficacy of the Microsoft Sentinel solution for SAP applications, enable auditing of your SAP system and configure the audit parameters. If you want to ingest SAP HANA DB logs, make sure to also enable auditing for SAP HANA DB.
6565

66-
We recommend that you configure auditing for all messages from the audit log, as this data is useful for Microsoft Sentinel detections and in post-compromise investigations and hunting. <!--add this to word-->
66+
We recommend that you configure auditing for all messages from the audit log, as this data is useful for Microsoft Sentinel detections and in post-compromise investigations and hunting.
6767

6868
For more information, see the [SAP documentation](https://community.sap.com/t5/application-development-blog-posts/analysis-and-recommended-settings-of-the-security-audit-log-sm19-rsau/ba-p/13297094) and [Collect SAP HANA audit logs in Microsoft Sentinel](collect-sap-hana-audit-logs.md).
6969

0 commit comments

Comments
 (0)