acrolinx

batamig · batamig · commit 254c7c26e5f5 · 2024-12-16T12:13:35.000+02:00
diff --git a/articles/sentinel/monitor-sap-system-health.md b/articles/sentinel/monitor-sap-system-health.md
@@ -36,7 +36,7 @@ For a video demonstration of the procedures in this article, watch the following
 
 ## Prerequisites
 
-- Before you can perform the procedures in this article, you need to have a SAP data connector connected to your SAP system. SAP logs aren't displayed in the Microsoft Sentinel **Logs** page until your SAP system is connected and data starts streaming into Microsoft Sentinel.
+- Before you can perform the procedures in this article, you need to have an SAP data connector connected to your SAP system. SAP logs aren't displayed in the Microsoft Sentinel **Logs** page until your SAP system is connected and data starts streaming into Microsoft Sentinel.
 
 For more information, see [Connect your SAP system to Microsoft Sentinel](sap/deploy-data-connector-agent-container.md).
 
diff --git a/articles/sentinel/sap/deploy-data-connector-agent-container.md b/articles/sentinel/sap/deploy-data-connector-agent-container.md
@@ -32,7 +32,7 @@ Content in this article is relevant for your **security**, **infrastructure**, a
 
 :::zone pivot="connection-agentless"
 
-:::image type="content" source="media/deployment-steps/deploy-data-connector-agentless.png" alt-text="Diagram of the SAP solution deployment flow, highlighting the Connect your SAP system step." border="false" :::
+:::image type="content" source="media/deployment-steps/deploy-data-connector-agentless.png" alt-text="Diagram of the SAP solution deployment flow, highlighting the Connect your SAP system step."  :::
 
 Content in this article is relevant for your **security** team, using information provided by your **SAP BASIS** teams.
 
@@ -204,7 +204,7 @@ This procedure describes how to create a new agent and connect it to your SAP sy
 
 Deploying the data connector agent from the portal is supported from both the Azure portal, and the Defender portal if you onboarded your workspace to the unified security operations platform.
 
-While deployment is also supported from the command line, we recommend that you use the portal for typical deployments. Data connector agents deployed using the command line can be managed only via the command line, and not via the portal. For more information, see [Deploy a SAP data connector agent from the command line](deploy-command-line.md).
+While deployment is also supported from the command line, we recommend that you use the portal for typical deployments. Data connector agents deployed using the command line can be managed only via the command line, and not via the portal. For more information, see [Deploy an SAP data connector agent from the command line](deploy-command-line.md).
 
 > [!IMPORTANT]
 > Deploying the container and creating connections to SAP systems from the portal is currently in PREVIEW. The [Azure Preview Supplemental Terms](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) include additional legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.
diff --git a/articles/sentinel/sap/deploy-sap-security-content.md b/articles/sentinel/sap/deploy-sap-security-content.md
@@ -18,7 +18,7 @@ zone_pivot_groups: sentinel-sap-connection
 
 # Install a Microsoft Sentinel solution for SAP applications
 
-The Microsoft Sentinel solutions for SAP applications include a SAP data connector, which collects logs from your SAP systems and sends them to your Microsoft Sentinel workspace, and out-of-the-box security content, which helps you gain insight into your organization's SAP environment and detect and respond to security threats. Installing your solution is a required step before you can configure your data connector agent container.
+The Microsoft Sentinel solutions for SAP applications include an SAP data connector, which collects logs from your SAP systems and sends them to your Microsoft Sentinel workspace, and out-of-the-box security content, which helps you gain insight into your organization's SAP environment and detect and respond to security threats. Installing your solution is a required step before you can configure your data connector agent container.
 
 Microsoft Sentinel supports both a containerized data collector agent and an agentless solution. Select the deployment option at the top of the page that matches your environment.
 
diff --git a/articles/sentinel/sap/deployment-overview.md b/articles/sentinel/sap/deployment-overview.md
@@ -52,7 +52,7 @@ You can also authenticate using SAP's Secure Network Communication (SNC) and X.5
 
 The Microsoft Sentinel agentless data connector for SAP uses the SAP Cloud Connector and SAP Integration Suite to connect to your SAP system and pull logs from it, as shown in the following image:
 
-:::image type="content" source="media/deployment-overview/agentless-connector.png" alt-text="Diagram that shows the Microsoft Sentinel agentless data connector in a SAP environment." border="false":::
+:::image type="content" source="media/deployment-overview/agentless-connector.png" alt-text="Diagram that shows the Microsoft Sentinel agentless data connector in an SAP environment." border="false":::
 
 By using the SAP Cloud Connector, the **Agentless solution** profits from already existing setups and established integration processes. This means you don't have to tackle network challenges again, as the people running your SAP Cloud Connector have already gone through that process.
 
@@ -106,7 +106,7 @@ We recommend that you involve all relevant teams when planning your deployment t
 **Extra options include:**
 
 - [Collect SAP HANA audit logs](collect-sap-hana-audit-logs.md)
-- [Deploy a SAP data connector agent manually](sap-solution-deploy-alternate.md)
+- [Deploy an SAP data connector agent manually](sap-solution-deploy-alternate.md)
 
 ## Stop SAP data collection
 
diff --git a/articles/sentinel/sap/preparing-sap.md b/articles/sentinel/sap/preparing-sap.md
@@ -151,7 +151,7 @@ For more information, see [Database Collector in Background Processing](https://
 
 1. Create an instance of SAP Integration Suite.
 
-1. Assign the SAP BTP **Integration_Provisioner** role to your your SAP BTP subaccount user account.
+1. Assign the SAP BTP **Integration_Provisioner** role to your SAP BTP subaccount user account.
 
 1. In the SAP Integration Suite, add the cloud integration capability.
 
diff --git a/articles/sentinel/sap/prerequisites-for-deploying-sap-continuous-threat-monitoring.md b/articles/sentinel/sap/prerequisites-for-deploying-sap-continuous-threat-monitoring.md
@@ -91,7 +91,7 @@ Typically, Azure prerequisites are managed by your **security** teams.
 | Prerequisite | Description |Required/optional |
 | ---- | ----------- |----------- |
 | **Access to the limited preview** | The **Agentless solution** requires you to register, and is only available to approved customers and partners during the limited preview period. For more information, see [Limited Preview Sign Up: Microsoft Sentinel Solution for SAP - Agent-less Data Connector](https://aka.ms/SentinelSAPAgentlessSignUp). |Required |
-| **Permissions to create Azure resources** | You must have: <br><br>- The necessary permissions to deploy solutions from the Microsoft Sentinel content hub. For more information, see [Prerequisites for deploying Microsoft Sentinel solutions](../sentinel-solutions-deploy.md#prerequisites) and [Microsoft Entra built-in roles](/entra/identity/role-based-access-control/permissions-reference#application-administrator). <br>Owner on the Sentinle resource group , required for:<br><br>- Creation of data collection rule and data collection endpoint.<br><br>- Monitoring Metrics Publisher role assignment on data collection rule. |Required |
+| **Permissions to create Azure resources** | You must have: <br><br>- The necessary permissions to deploy solutions from the Microsoft Sentinel content hub. For more information, see [Prerequisites for deploying Microsoft Sentinel solutions](../sentinel-solutions-deploy.md#prerequisites) and [Microsoft Entra built-in roles](/entra/identity/role-based-access-control/permissions-reference#application-administrator). <br>Owner on the Microsoft Sentinel resource group , required for:<br><br>- Creation of data collection rule and data collection endpoint.<br><br>- Monitoring Metrics Publisher role assignment on data collection rule. |Required |
 | **Permissions in** **Microsoft Entra**|You must have permissions in Microsoft Entra ID required to create app registrations. This permission can be obtained through membership of built-in Microsoft Entra ID role:<br><br>- Application Developer.|Required |
 
 ## SAP prerequisites for the agentless data connector
@@ -100,7 +100,7 @@ We recommend that your **SAP BASIS** team verify and ensure SAP system prerequis
 
 | Prerequisite | Description |
 | ---- | ----------- |
-| **SAP system** | Your SAP system must have: <br><br>A SAP BTP Subaccount with following services enabled:  <br>    - SAP Integration Suite <br>- SAP Process Integration Runtime <br>- Cloud Foundry Runtime<br>    For more information, see the [SAP documentation](https://help.sap.com/docs/sap-hana-spatial-services/onboarding/creating-subaccount-on-sap-business-technology-platform-sap-btp ). [Trial accounts](https://developers.sap.com/tutorials/hcp-create-trial-account.html) are supported.<br><br>The [SAP Cloud Connector](https://help.sap.com/docs/connectivity/sap-btp-connectivity-cf/installation?locale=en-US) deployed <br><br>SAP NetWeaver version 7.5 or higher|
+| **SAP system** | Your SAP system must have: <br><br>An SAP BTP Subaccount with following services enabled:  <br>    - SAP Integration Suite <br>- SAP Process Integration Runtime <br>- Cloud Foundry Runtime<br>    For more information, see the [SAP documentation](https://help.sap.com/docs/sap-hana-spatial-services/onboarding/creating-subaccount-on-sap-business-technology-platform-sap-btp ). [Trial accounts](https://developers.sap.com/tutorials/hcp-create-trial-account.html) are supported.<br><br>The [SAP Cloud Connector](https://help.sap.com/docs/connectivity/sap-btp-connectivity-cf/installation?locale=en-US) deployed <br><br>SAP NetWeaver version 7.5 or higher|
 | **SAP roles and permissions** | You must have the following roles in your SAP systems: <br><br>**In SAP NetWeaver 7.5+**: SAP Netweaver Administrator <br><br>**In SAP BTP, all of the following roles**:<br>- Subaccount administrator <br>- Integration Provisioner <br>- PI_Administrator <br>- PI_Integration_Developer <br>- PI_Business_Expert| 
 
 :::zone-end
diff --git a/articles/sentinel/sap/sap-audit-controls-workbook.md b/articles/sentinel/sap/sap-audit-controls-workbook.md
@@ -18,7 +18,7 @@ ms.collection: usx-security
 
 This article describes how you can use the *SAP - Security Audit Controls* workbook to monitor and track security control framework compliance across your SAP systems, including the following functionality:
 
-- See recommendations on which analytics rules to enable, and enable them in-place with proper preset configuration.
+- See recommendations on which analytics rules to enable, and enable them in place with proper preset configuration.
 - Associate your analytics rules to the SOX or NIST control framework, or apply your own custom control framework.
 - Review incidents and alerts summarized by control, according to the selected control framework.
 - Export relevant incidents for further analysis, for auditing and reporting purposes.
diff --git a/articles/sentinel/sap/sap-audit-log-workbook.md b/articles/sentinel/sap/sap-audit-log-workbook.md
@@ -78,7 +78,7 @@ The following table describes each metric in the **Logon analysis** area:
 
 |Area  |Description  |
 |---------|---------|
-|**Unique user logons per system**     |Shows the number of unique signins for each SAP system, and a graph with the sign-in trends over the selected time for each system. <br><br>For example: the 012 system has 1.4-K unique logon attempts in the last 14 days, and in these 14 days the graph shows a relatively rising sign-in trend.         |
+|**Unique user logons per system**     |Shows the number of unique sign-ins for each SAP system, and a graph with the sign-in trends over the selected time for each system. <br><br>For example: the 012 system has 1.4-K unique logon attempts in the last 14 days, and in these 14 days the graph shows a relatively rising sign-in trend.         |
 |**Logon types trend**     |Shows a trend of the number of sign ins according to type, for example, login via dialog. <br><br>Hover over the graph to show the number of logons for different dates.|
 |**Logon failures Vs. success by unique users - trend**     |Shows a trend of successful and failed sign ins in the selected period. <br><br>Hover over the graph to show the amount of successful and failed sign ins for different dates.|
 
diff --git a/articles/sentinel/sap/sap-solution-deploy-alternate.md b/articles/sentinel/sap/sap-solution-deploy-alternate.md
@@ -18,7 +18,7 @@ ms.collection: usx-security
 
 This article provides procedures for deploying and configuring the Microsoft Sentinel for SAP data connector agent container with expert, custom, or manual configuration options. For typical deployments we recommend that you use the [portal](deploy-data-connector-agent-container.md#deploy-the-data-connector-agent-from-the-portal-preview) instead.
 
-Content in this article is intended for your **SAP BASIS** teams. For more information, see [Deploy a SAP data connector agent from the command line](deploy-command-line.md).
+Content in this article is intended for your **SAP BASIS** teams. For more information, see [Deploy an SAP data connector agent from the command line](deploy-command-line.md).
 
 > [!NOTE]
 > This article is relevant only for the data connector agent, and isn't relevant for the [SAP agentless solution](deployment-overview.md#data-connector) (limited preview).
