Merge pull request #281708 from Howie425/patch-20

Update trusted-launch-existing-vm.md

Author: prmerger-automator[bot]

articles/virtual-machines/trusted-launch-existing-vm.md

@@ -33,7 +33,6 @@ Azure Virtual Machines supports enabling Azure Trusted Launch on existing [Azure
   - Existing Azure VM backup can be migrated from the *Standard* to the *Enhanced* policy. Follow the steps in [Migrate Azure VM backups from Standard to Enhanced policy (preview)](../backup/backup-azure-vm-migrate-enhanced-policy.md).
 
 ## Best practices
-
 - Enable Trusted Launch on a test Generation 2 VM and determine if any changes are required to meet the prerequisites before you enable Trusted Launch on Generation 2 VMs associated with production workloads.
 - [Create restore points](create-restore-points.md) for Azure Generation 2 VMs associated with production workloads before you enable the Trusted Launch security type. You can use the restore points to re-create the disks and Generation 2 VM with the previous well-known state.
 
@@ -181,6 +180,9 @@ Make sure that you install the latest [Azure PowerShell](/powershell/azure/insta
 
 1. Start the upgraded Trusted Launch VM. Verify that you can sign in to the VM by using either RDP (for Windows VMs) or SSH (for Linux VMs).
 
+>[!NOTE]
+> Make sure to change the `-SecurityType` to `TrustedLaunch`, for all deployment scripts this will ensure when virtual machines are provisioned, they will be automatically Trusted Launch. 
+
 ### [Template](#tab/template)
 
 Follow the steps to enable Trusted Launch on an existing Azure Generation 2 VM by using an ARM template.
@@ -293,6 +295,19 @@ Follow the steps to enable Trusted Launch on an existing Azure Generation 2 VM b
 
 ---
 
+## Azure Advisor Recommendation
+
+Azure Advisor populates an **Enable Trusted Launch Compatible Images and VM Sizes for Existing Generation 2 VMs** operational excellence recommendation for existing Generation 2 VMs to adopt [Trusted Launch](trusted-launch.md), a higher security posture for Azure VMs at no additional cost to you. Ensure Generation 2 VM has all prerequisites to migrate to Trusted Launch, follow all the best practices including validation of OS image, VM Size, and creating restore points. For the Advisor recommendation to be considered complete, follow the steps outlined in the [**Enable Trusted Launch on an existing VM**](trusted-launch-existing-vm.md) to upgrade the virtual machines security type and enable Trusted Launch. 
+
+### What if there is Generation 2 VMs, that doesn't fit the prerequistes for Trusted Launch ? 
+
+For a Generation 2 VM, that has not met the prerequistes to upgrade to Trusted Launch, look how to fulfill the prerequistes. 
+1. If using an OS image not supported, upgrade to Trusted Launch|Gen2 image, most Windows OS support Trusted Launch except Windows 2012 Datacenter offerings. In the case of Linux OS, upgrade to the newest SKU offered by the image distribution. 
+2. If using a virtual machine size not supported, please look for an [equivalant Trusted Launch supported size](/sizes/resize-vm.md) that supports Trusted Launch.
+
+> [!NOTE]
+> For M-series and ARM64 virtual machine users, please dismiss the recommendation for all resources. 
+
 ## Related content
 
 - After the upgrades, we recommend that you enable [boot integrity monitoring](trusted-launch.md#microsoft-defender-for-cloud-integration) to monitor the health of the VM by using Microsoft Defender for Cloud.