Merge pull request #312983 from MartinPankraz/docs-editor/sap-agent-migrate-1773214500

Update sap-agent-migrate.md

Author: prmerger-automator[bot]

articles/sentinel/sap/sap-agent-migrate.md

@@ -51,6 +51,9 @@ Your existing investment in the Microsoft Sentinel Solution for SAP analytic rul
 1. **Monitor**: Run both the containerized agent and the agentless data connector in parallel for a defined period to ensure stability and completeness of log collection.
 1. **Decommission**: Once you have validated that the agentless data connector is functioning correctly, proceed to decommission the containerized SAP agent. See the "[Stop SAP data collection](stop-collection.md)" article for details.
 
+> [!TIP]
+> Follow the [agentless migration video playlist](https://www.youtube.com/playlist?list=PLmAptfqzxVEV69k9hwfI4zVOb_o6LgfDV) for latest insights for a smooth transition.
+
 > [!IMPORTANT]
 > Review the authorizations of the Sentinel user and role on your SAP systems used with the containerized agent. The agentless data connector requires less but different authorizations compared to the containerized SAP agent. Refer to the [configuration guide](/azure/sentinel/sap/preparing-sap?pivots=connection-agentless#configure-the-microsoft-sentinel-role) for details and SAP role sample for minimum authorizations.
 
@@ -72,6 +75,8 @@ SAP HANA database or OS-level detections are out of scope for the comparison bec
 
 ## Next steps
 
+- [Discover the agentless migration video playlist](https://www.youtube.com/playlist?list=PLmAptfqzxVEV69k9hwfI4zVOb_o6LgfDV)
+
 - [Learn more about Microsoft Sentinel Solution for SAP applications](solution-overview.md).
 
 - [Learn more about Microsoft Sentinel Solution for SAP BTP](sap-btp-solution-overview.md).