Skip to content

Commit 291f2f1

Browse files
Update powershell-onboarding.md
1 parent 42242e8 commit 291f2f1

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

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

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Onboard with PowerShell
33
description: This document walks you through the process of enabling Microsoft Defender for Cloud with PowerShell cmdlets.
44
ms.topic: quickstart
5-
ms.date: 01/04/2024
5+
ms.date: 01/11/2024
66
ms.custom: mode-api, ignite-2022, devx-track-azurepowershell
77
---
88

@@ -82,6 +82,8 @@ These steps should be performed before you run the Defender for Cloud cmdlets:
8282
8383
> [!NOTE]
8484
> We recommend that you enable auto provisioning to make sure that your Azure virtual machines are automatically protected by Microsoft Defender for Cloud.
85+
86+
> 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).
8587
>
8688
8789
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:

0 commit comments

Comments
 (0)