more feedback

Author: batamig

articles/sentinel/sap/sap-audit-controls-workbook.md

@@ -11,7 +11,7 @@ appliesto:
 ms.collection: usx-security
 ---
 
-# Check compliance for your SAP security controls with the SAP - Security Audit Controls workbook(Preview)
+# Check compliance for your SAP security controls with the SAP - Security Audit Controls workbook
 
 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:
 
@@ -26,9 +26,6 @@ For example:
 
 Content in this article is intended for your **security** team.
 
-> [!IMPORTANT]
-> The Microsoft Sentinel SAP Audit Controls workbook 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.
-
 ## Prerequisites
 
 Before you can start using the **SAP - Security Audit log and Initial Access** workbook, you must have:

articles/sentinel/sap/stop-collection.md

@@ -27,6 +27,7 @@ Before you stop the data collection from your SAP applications, ensure you have
 - The Log Analytics workspace that's enabled for Microsoft Sentinel. For more information, see [Roles and permissions in Microsoft Sentinel](../roles.md).
 - The SAP data connector agent machine or container.
 
+<!--
 We recommend that you back up your current configuration and logs before making any changes. <!--is this correct?-->
 
 
@@ -38,12 +39,6 @@ To stop ingesting SAP logs into the Microsoft Sentinel workspace, and to stop th
 docker stop sapcon-[SID/agent-name]
 ```
 
-To stop ingesting a specific SID for a multi-SID container, make sure that you also delete the SID from the connector page UI in Microsoft Sentinel: This option is available only if you [deployed the agent via the portal](deploy-data-connector-agent-container.md#deploy-the-data-connector-agent-from-the-portal-preview).
-
-1. In Microsoft Sentinel, select **Configuration > Data connectors** and search for **Microsoft Sentinel for SAP**.
-1. Select the data connector row and then select **Open connector page** in the side pane.
-1. In the **Configuration** area on the **Microsoft Sentinel for SAP** data connector page, locate the SID agent you want to remove and select **Delete**. <!--need validation for this-->
-
 The Docker container stops and doesn't send any more SAP logs to the Microsoft Sentinel workspace. This stops both the ingestion and billing for the SAP system related to the connector.
 
 If you need to reenable the Docker container, sign into the data connector agent machine and run:
@@ -52,6 +47,15 @@ If you need to reenable the Docker container, sign into the data connector agent
 docker start sapcon-[SID]
 ```
 
+To stop ingesting a specific SID for a multi-SID container, make sure that you also delete the SID from the connector page UI in Microsoft Sentinel. This option is relevant only if you [deployed the agent via the portal](deploy-data-connector-agent-container.md#deploy-the-data-connector-agent-from-the-portal-preview).
+
+1. In Microsoft Sentinel, select **Configuration > Data connectors** and search for **Microsoft Sentinel for SAP**.
+1. Select the data connector row and then select **Open connector page** in the side pane.
+1. In the **Configuration** area on the **Microsoft Sentinel for SAP** data connector page, locate the SID agent you want to remove and select **Delete**. <!--need validation for this-->
+
+
+
+
 ## Remove the user role and any optional CR installed on your ABAP system
 
 If you're turning off the SAP data connector agent and stopping log ingestion from your SAP system, you might want to also remove the user role and optional CRs installed on your ABAP system.