Changes as per PM and dev

Author: paulinbar

defender-endpoint/TOC.yml

@@ -267,21 +267,21 @@
               href: mde-linux-prerequisites.md
             - name: Choose a deployment method
               items:
-              - name: Installer script based deployment
-                href: linux-installer-script.md
               - name: Enabling deployment to a custom location
                 href: linux-custom-location-installation.md
+              - name: Installer script based deployment
+                href: linux-installer-script.md
               - name: Ansible based deployment
                 href: linux-install-with-ansible.md
               - name: Chef based deployment
                 href: linux-deploy-defender-for-endpoint-with-chef.md
               - name: Puppet based deployment
                 href: linux-install-with-puppet.md
-              - name: Saltstack-based deployment
+              - name: Saltstack based deployment
                 href: linux-install-with-saltack.md
               - name: Manual deployment
                 href: linux-install-manually.md
-              - name: Deployment using golden images
+              - name: Golden image based deployment
                 href: linux-deploy-defender-for-endpoint-using-golden-images.md
               - name: Direct onboarding with Defender for Cloud
                 href: /azure/defender-for-cloud/onboard-machines-with-defender-for-endpoint?toc=/defender-endpoint/toc.json&bc=/defender-endpoint/breadcrumb/toc.json

defender-endpoint/linux-deploy-defender-for-endpoint-using-golden-images.md

@@ -18,7 +18,7 @@ search.appverid: met150
 ms.date: 009/01/2025
 ---
 
-# Deploy Microsoft Defender for Endpoint on Linux using golden images (preview)
+# Deploy Microsoft Defender for Endpoint on Linux using golden images
 
 [!INCLUDE [Microsoft Defender XDR rebranding](../includes/microsoft-defender.md)]
 
@@ -31,21 +31,21 @@ Golden images are preconfigured virtual machine templates used to rapidly deploy
 
 This guide walks you through:
 
-- Installing Microsoft Defender for Endpoint on a golden image.
+- Deploying Microsoft Defender for Endpoint on a golden image.
 
 - Preparing the image for cloning.
 
 - Ensuring unique identifiers for each virtual machine instance.
 
 - Specific steps for cloud and on-premises environments.
 
-## Step 1: Install Microsoft Defender for Endpoint on a golden image
+## Step 1: Deploy Microsoft Defender for Endpoint on a golden image
 
-1. Prepare the case virtual machine
+1. Prepare the base virtual machine
 
    - Install your preferred [supported Linux distribution](./mde-linux-prerequisites.md#supported-linux-distributions) and apply all necessary system updates.
 
-1. Install Microsoft Defender for Endpoint
+1. Deploy Microsoft Defender for Endpoint on a golden image
 
    There are several methods and tools that you can use to deploy Microsoft Defender for Endpoint on Linux (applicable to AMD64 and ARM64 Linux servers):
 
@@ -65,28 +65,30 @@ This guide walks you through:
 
    - [Guidance for Defender for Endpoint on Linux Server with SAP](./mde-linux-deployment-on-sap.md)
 
-1. Validate Installation
+1. Validate the deployment
 
    Check the health status of the product by running the following command. A return value of `true` denotes that the product is functioning as expected:
 
    ```bash
    mdatp health
    ```
 
+After you've successfully deployed Defender on the golden image, there is no need to deploy it separately on each virtual machine clone.
+
 ## Step 2: Prepare the golden image for cloning
 
-Before making a snapshot of the virtual machine, follow these steps to ensure that each clone has a unique machine identity:
+Before making a snapshot of the virtual machine, follow these steps to ensure that each virtual machine clone will have a unique machine identity:
 
 ### On-premises machines
 
-Follow these steps for the respective virtualization platforms:
+For on-premises virtual machines, make sure that the golden image generated from it is configured such that when it is cloned, each virtual machine clone will have a unique hardware UUID.
+
+If you are using **KVM/libvirt** or **VMware/Hyper-V** as the virtualization platform, it is recommended to use the following instructions:
 
 - **KVM/libvirt**: Omit the \<uuid\> element in domain XML or set a fresh UUID using: uuidgen
 
 - **VMware/Hyper-V**: Enable platform settings to generate a new BIOS GUID during clone or conversion.
 
-Ensure that the machines are configured to have a unique hardware UUID.
-
 ### Cloud virtual machines
 
 Cloud platforms (for example, Azure, AWS, GCP) automatically inject unique metadata and identifiers via their instance metadata services (IMDS). No manual steps are required. Microsoft Defender for Endpoint automatically detects and uses these values to generate unique machine IDs.