Merge pull request #262997 from AlizaBernstein/WI-147394-add-note-AMA-not-required-dfservers

WI-147394-add-note-AMA-not-required-dfservers

Author: prmerger-automator[bot]

articles/defender-for-cloud/powershell-onboarding.md

@@ -2,7 +2,7 @@
 title: Onboard with PowerShell
 description: This document walks you through the process of enabling Microsoft Defender for Cloud with PowerShell cmdlets.
 ms.topic: quickstart
-ms.date: 01/04/2024
+ms.date: 01/11/2024
 ms.custom: mode-api, ignite-2022, devx-track-azurepowershell
 ---
 
@@ -81,7 +81,7 @@ These steps should be performed before you run the Defender for Cloud cmdlets:
     ```
 
     > [!NOTE]
-    > We recommend that you enable auto provisioning to make sure that your Azure virtual machines are automatically protected by Microsoft Defender for Cloud.
+    > We recommend that you enable auto provisioning to make sure that your Azure virtual machines are automatically protected by Microsoft Defender for Cloud.<br/>As part of the Defender for Cloud updated strategy, Azure Monitor Agent (AMA) will no longer be required for the Defender for Servers offering. However, it will still be required for Defender for SQL server on machines. As a result, deploying Azure Monitor Agent (AMA) with the Defender for Cloud portal is available for SQL servers on machines, with a new deployment policy. Learn more about how to [migrate to SQL server-targeted Azure Monitoring Agent's (AMA) auto-provisioning process](defender-for-sql-autoprovisioning.md).
     >
 
 1. Optional: It's highly recommended that you [define the security contact details](configure-email-notifications.md) for the subscriptions you onboard, which will be used as the recipients of alerts and notifications generated by Defender for Cloud: