Skip to content

Commit 2b1fd2a

Browse files
committed
Update configure-endpoints-script.md
1 parent 3fd5a00 commit 2b1fd2a

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

defender-endpoint/configure-endpoints-script.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ ms.collection:
1515
ms.custom: admindeeplinkDEFENDER
1616
ms.topic: conceptual
1717
ms.subservice: onboard
18-
ms.date: 03/26/2025
18+
ms.date: 04/16/2025
1919
---
2020

2121
# Onboard Windows devices using a local script
@@ -32,7 +32,7 @@ ms.date: 03/26/2025
3232
You can also manually onboard individual devices to Defender for Endpoint. You might want to onboard some devices when you're testing the service before you commit to onboarding all devices in your network.
3333

3434
> [!IMPORTANT]
35-
> The script described in this article is recommended for manually onboarding devices to Defender for Endpoint. It should only be used on a limited number of devices. If you're deploying to a production environment, see [other deployment options](onboard-windows-client.md), such as Intune, Group Policy, or Configuration Manager.
35+
> The script described in this article is recommended for manually onboarding devices to Defender for Endpoint. It should only be used on a limited number of devices. If you're deploying to a production environment, see [other deployment options](onboard-client.md), such as Intune, Group Policy, or Configuration Manager.
3636
3737
Check out [Identify Defender for Endpoint architecture and deployment method](deployment-strategy.md) to see the various paths in deploying Defender for Endpoint.
3838

0 commit comments

Comments
 (0)