fixes and updates

Author: denisebmsft

defender-endpoint/linux-install-with-puppet.md

@@ -308,9 +308,9 @@ If you encounter issues during installation, try these self-troubleshooting step
 
 1. See [Log installation issues](linux-resources.md#log-installation-issues) for more information on how to find the automatically generated log that is created by the installer when an error occurs.
 
-2. see [Installation issues](/defender-endpoint/linux-support-install) for more information on commonly occurring installation issues
+2. see [Installation issues](/defender-endpoint/linux-support-install) for more information on commonly occurring installation issues.
 
-3. If health of the device is false, see [MDE agent health issues](/defender-endpoint/health-status)
+3. If health of the device is false, see [Defender for Endpoing agent health issues](/defender-endpoint/health-status).
 
 4. For product performance issues, see [Troubleshoot performance issues](/defender-endpoint/linux-support-perf), [performance tuning](/defender-endpoint/linux-support-perf?branch=main)
 

defender-endpoint/mde-linux-prerequisites.md

@@ -182,11 +182,25 @@ You can use one of the following methods to deploy Microsoft Defender for Endpoi
 
 6. Arm64-based Linux servers, see [Microsoft Defender for Endpoint on Linux for Arm64-based devices (preview)](/defender-endpoint/mde-linux-arm)
 
-If you experience any installation failures, see [Troubleshooting installation failures in Microsoft Defender for Endpoint on Linux](/defender-endpoint/linux-support-install)
-
 > [!IMPORTANT]
 > Installing Microsoft Defender for Endpoint in any location other than the default install path isn't supported.
 > Microsoft Defender for Endpoint on Linux creates a mdatp user with random UID and GID.
 > If you want to control the UID and GID, create a mdatp user before installation using the /usr/sbin/nologin shell option.
 > Here's an example: mdatp:x:UID:GID::/home/mdatp:/usr/sbin/nologin.
 
+## Installation instructions 
+
+There are several methods and tools that you can use to deploy Microsoft Defender for Endpoint on Linux:
+
+- [Installer script based deployment](/defender-endpoint/linux-installer-script)
+- [Ansible based deployment](/defender-endpoint/linux-install-with-ansible)
+- [Chef based deployment](/defender-endpoint/linux-deploy-defender-for-endpoint-with-chef)
+- [Puppet based deployment](/defender-endpoint/linux-install-with-puppet)
+- [SaltStack based deployment](/defender-endpoint/linux-install-with-saltack)
+- [Manual deployment](/defender-endpoint/linux-install-manually)
+- [Direct onboarding with Defender for Cloud](/azure/defender-for-cloud/onboard-machines-with-defender-for-endpoint)
+- For Arm64-based Linux servers, see [Microsoft Defender for Endpoint on Linux for Arm64-based devices (preview)](/defender-endpoint/mde-linux-arm)
+- For Linux Server with SAP, see [Deployment guidance for Defender for Endpoint on Linux Server with SAP](/defender-endpoint/mde-linux-deployment-on-sap)
+
+> [!IMPORTANT]
+> Installing Microsoft Defender for Endpoint in any location other than the default install path isn't supported. On Linux, Microsoft Defender for Endpoint creates an mdatp user with random UID and GID values. If you want to control these values, create an mdatp user before installation using the /usr/sbin/nologin shell option. Here's an example: `mdatp:x:UID:GID::/home/mdatp:/usr/sbin/nologin`.