fixing tabs

Author: batamig

articles/sentinel/TOC.yml

@@ -156,7 +156,7 @@
           - name: Connect your SAP system
             displayName: disable, stop ingestion, stop 
             href: sap/deploy-data-connector-agent-container.md
-          - name: Troubleshoot SAP data connector agent
+          - name: Troubleshoot SAP data connector
             href: sap/sap-deploy-troubleshoot.md    
           - name: Extra deployment steps
             items:

articles/sentinel/sap/deploy-sap-security-content.md

@@ -22,8 +22,19 @@ The Microsoft Sentinel solutions for SAP applications include an SAP data connec
 
 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.
 
+:::zone pivot="connection-agent"
+
 :::image type="content" source="media/deployment-steps/install-solution.png" alt-text="Diagram of the SAP solution deployment flow, highlighting the Install solution content step." border="false":::
 
+:::zone-end
+
+:::zone pivot="connection-agentless"
+
+:::image type="content" source="media/deployment-steps/install-solution-agentless.png" alt-text="Diagram of the SAP solution deployment flow, highlighting the Install solution content step." border="false":::
+
+:::zone-end
+
+
 Content in this article is relevant for your **security** team.
 
 :::zone pivot="connection-agentless"

articles/sentinel/sap/deployment-overview.md

@@ -59,6 +59,7 @@ By using the SAP Cloud Connector, the **Agentless solution** profits from alread
 The **Agentless solution** is compatible with SAP S/4HANA Cloud, Private Edition RISE with SAP, SAP S/4HANA on-premises, and SAP ERP Central Component (ECC), ensuring continued functionality of existing security content, including detections, workbooks, and playbooks.
 
 The agentless data connector ingests critical security logs such as the security audit log, change docs logs and user master data including user roles and authorizations.
+
 ---
 
 ### Security content
@@ -122,11 +123,9 @@ We recommend that you involve both teams when planning your deployment to ensure
 
 1. [Review the prerequisites for deploying the SAP agentless solution](prerequisites-for-deploying-sap-continuous-threat-monitoring.md).
 
-1. The following steps can happen in parallel as they involve separate teams, and aren't dependent on each other:
-
-    1. [Deploy the SAP agentless solution from the content hub](deploy-sap-security-content.md). This step is handled by the security team on the Azure portal.
+1. [Deploy the SAP agentless solution from the content hub](deploy-sap-security-content.md). This step is handled by the security team on the Azure portal.
 
-    1. [Configure your SAP system for the Microsoft Sentinel solution](preparing-sap.md), including configuring SAP authorizations, configuring SAP auditing, and more. We recommend that these steps be done by your SAP BASIS team, and our documentation includes references to SAP documentation.
+1. [Configure your SAP system for the Microsoft Sentinel solution](preparing-sap.md), including configuring SAP authorizations, configuring SAP auditing, and more. We recommend that these steps be done by your SAP BASIS team, and our documentation includes references to SAP documentation. Some of the procedures in this step can be done by the SAP BASIS team before installing the solution.
 
 1. [Connect your SAP system](deploy-data-connector-agent-container.md) using an agentless data connector with the SAP Cloud Connector. This step is handled by your security team on the Azure portal, using information provided by your SAP BASIS team.
 

articles/sentinel/sap/media/deployment-steps/deploy-data-connector-agentless.png

@@ -30,7 +30,7 @@ The procedures in this article are typically performed by your **SAP BASIS** tea
 :::zone pivot="connection-agentless"
 This article is part of the second step in deploying the Microsoft Sentinel solution for SAP applications. While steps that are performed in Microsoft Sentinel require that the solution be installed first, other preparations in the SAP environment can happen in parallel. <!--need new images across-->
 
-:::image type="content" source="media/deployment-steps/prepare-sap-environment.png" alt-text="Diagram of the deployment flow for the Microsoft Sentinel solution for SAP applications, with the preparing SAP step highlighted." border="false":::
+:::image type="content" source="media/deployment-steps/prepare-sap-environment-agentless.png" alt-text="Diagram of the deployment flow for the Microsoft Sentinel solution for SAP applications, with the preparing SAP step highlighted." border="false":::
 
 Many of the procedures in this article are typically performed by your **SAP BASIS** team. Some steps include your **security** team too.
 :::zone-end
@@ -191,6 +191,8 @@ For more information, see the [SAP documentation](https://help.sap.com/docs/inte
 
 ## Perform initial connector configuration
 
+This procedure starts in Microsoft Sentinel and requires that the solution be installed before you start.
+
 1. In Microsoft Sentinel, go to the **Configuration > Data connectors** page and locate the **Microsoft Sentinel for SAP - agent-less (Preview) (Preview)** data connector.
 
 1. In the **Configuration** area, expand and follow the instructions in the **Initial connector configuration - Run the steps below once:** area. These steps will require a mixture of your Security and SAP BASIS teams.