Merge branch 'sap-cr-changes' of https://github.com/limwainstein/azure-docs-pr into sap-cr-changes

Author: limwainstein

articles/sentinel/sap/prerequisites-for-deploying-sap-continuous-threat-monitoring.md

@@ -57,7 +57,7 @@ To successfully deploy the Microsoft Sentinel Solution for SAP, you must meet th
 
 | Prerequisite | Description |
 | ---- | ----------- |
-| **Supported SAP versions** | The SAP data connector agent works best with [SAP_BASIS versions 750 SP13](https://support.sap.com/en/my-support/software-downloads/support-package-stacks/product-versions.html#:~:text=SAP%20NetWeaver%20%20%20%20SAP%20Product%20Version,%20%20SAPKB710%3Cxx%3E%20%207%20more%20rows) or later. <br><br>Certain steps in this tutorial provide alternative instructions if you're working on the older [SAP_BASIS version 740](https://support.sap.com/en/my-support/software-downloads/support-package-stacks/product-versions.html#:~:text=SAP%20NetWeaver%20%20%20%20SAP%20Product%20Version,%20%20SAPKB710%3Cxx%3E%20%207%20more%20rows). |
+| **Supported SAP versions** | The SAP data connector agent support SAP NetWeaver systems and was tested on [SAP_BASIS versions 731](https://support.sap.com/en/my-support/software-downloads/support-package-stacks/product-versions.html#:~:text=SAP%20NetWeaver%20%20%20%20SAP%20Product%20Version,%20%20SAPKB710%3Cxx%3E%20%207%20more%20rows) and above. <br><br>Certain steps in this tutorial provide alternative instructions if you're working on the older [SAP_BASIS version 740](https://support.sap.com/en/my-support/software-downloads/support-package-stacks/product-versions.html#:~:text=SAP%20NetWeaver%20%20%20%20SAP%20Product%20Version,%20%20SAPKB710%3Cxx%3E%20%207%20more%20rows). |
 | **Required software** | SAP NetWeaver RFC SDK 7.50 ([Download here](https://aka.ms/sentinel4sapsdk))<br>Make sure that you also have an SAP user account in order to access the SAP software download page. |
 | **SAP system details** | Make a note of the following SAP system details for use in this tutorial:<br>- SAP system IP address and FQDN hostname<br>- SAP system number, such as `00`<br>- SAP System ID, from the SAP NetWeaver system (for example, `NPL`) <br>- SAP client ID, such as `001` |
 | **SAP NetWeaver instance access** | The SAP data connector agent uses one of the following mechanisms to authenticate to the SAP system: <br>- SAP ABAP user/password<br>- A user with an X.509 certificate (This option requires additional configuration steps) |
@@ -89,7 +89,7 @@ Experienced SAP administrators may choose to create the role manually and assign
 
 You can deploy additional CRs from the [Microsoft Sentinel GitHub repository](https://github.com/Azure/Azure-Sentinel/tree/master/Solutions/SAP/CR) to enable the SAP data connector to retrieve certain information from your SAP system.
 - **SAP BASIS 7.5 SP12 and above**: Client IP Address information from security audit log
-- **ANY SAP BASIS version**: DB Table logs
+- **ANY SAP BASIS version**: DB Table logs, Spool Output log
 
 | SAP BASIS versions | Recommended CR |Notes |
 | --- | --- | --- |

articles/sentinel/sap/sap-solution-log-reference.md

@@ -420,7 +420,7 @@ For best results, use the Microsoft Sentinel functions listed below to visualize
 
 - **Log purpose**: Records the progress of an application execution so that you can reconstruct it later as needed.
 
-    Available by using RFC with a custom service based on standard services of XBP interface. This log is generated per client.
+    Available by using RFC based on standard SAP table and standard services of XBP interface. This log is generated per client.
 
 #### ABAPAppLog_CL log schema
 
@@ -471,7 +471,7 @@ For best results, use the Microsoft Sentinel functions listed below to visualize
 
     - Other entities in the SAP system, such as user data, roles, addresses.
 
-    Available by using RFC with a custom service based on standard services. This log is generated per client.
+    Available by using RFC based on standard SAP tables. This log is generated per client.
 
 #### ABAPChangeDocsLog_CL log schema
 
@@ -515,7 +515,7 @@ For best results, use the Microsoft Sentinel functions listed below to visualize
 
 - **Log purpose**: Includes the Change & Transport System (CTS) logs, including the directory objects and customizations where changes were made.
 
-    Available by using RFC with a custom service based on standard tables and standard services. This log is generated with data across all clients.
+    Available by using RFC based on standard tables and standard SAP services. This log is generated with data across all clients.
 
 > [!NOTE]
 > In addition to application logging, change documents, and table recording, all changes that you make to your production system using the Change & Transport System are documented in the CTS and TMS logs.
@@ -630,7 +630,7 @@ To have this log sent to Microsoft Sentinel, you must [add it manually to the **
 
 - **Log purpose**: Combines all background processing job logs (SM37).
 
-    Available by using RFC with a custom service based on standard services of XBP interfaces. This log is generated with data across all clients.
+    Available by using RFC based on standard SAP table and standard services of XBP interfaces. This log is generated with data across all clients.
 
 #### ABAPJobLog_CL log schema
 
@@ -724,7 +724,7 @@ To have this log sent to Microsoft Sentinel, you must [add it manually to the **
 
 - **Log purpose**: Serves as the main log for SAP Printing with the history of spool requests. (SP01).
 
-    Available by using RFC with a custom service based on standard tables. This log is generated with data across all clients.
+    Available by using RFC based on standard SAP table. This log is generated with data across all clients.
 
 #### ABAPSpoolLog_CL log schema
 
@@ -867,7 +867,7 @@ To have this log sent to Microsoft Sentinel, you must [add it manually to the **
 
     For example, unmapped business processes may be simple release or approval procedures, or more complex business processes such as creating base material and then coordinating the associated departments.
 
-    Available by using RFC with a custom service based on standard tables and standard services. This log is generated per client.
+    Available by using RFC based on standard SAP tables. This log is generated per client.
 
 #### ABAPWorkflowLog_CL log schema