Skip to content

Commit bd491da

Browse files
committed
Update production-deployment.md
1 parent 1ba1d44 commit bd491da

File tree

1 file changed

+5
-3
lines changed

1 file changed

+5
-3
lines changed

defender-endpoint/production-deployment.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ ms.custom: admindeeplinkDEFENDER
1717
ms.topic: how-to
1818
ms.subservice: onboard
1919
search.appverid: met150
20-
ms.date: 04/15/2025
20+
ms.date: 06/19/2025
2121
---
2222

2323
# Prepare to deploy Microsoft Defender for Endpoint deployment
@@ -40,8 +40,10 @@ In this deployment scenario, you're guided through the steps on:
4040
- Tenant configuration
4141
- Network configuration
4242

43-
> [!NOTE]
44-
> For the purpose of guiding you through a typical deployment, this scenario will only cover the use of Microsoft Configuration Manager. Defender for Endpoint supports the use of other onboarding tools but we won't cover those scenarios in the deployment guide. For more information, see [Identify Defender for Endpoint architecture and deployment method](deployment-strategy.md).
43+
> [!IMPORTANT]
44+
> Microsoft recommends that you use roles with the fewest permissions. This helps improve security for your organization. Global Administrator is a highly privileged role that should be limited to emergency scenarios when you can't use an existing role.
45+
46+
For the purpose of guiding you through a typical deployment, this scenario will only cover the use of Microsoft Configuration Manager. Defender for Endpoint supports the use of other onboarding tools but we won't cover those scenarios in the deployment guide. For more information, see [Identify Defender for Endpoint architecture and deployment method](deployment-strategy.md).
4547

4648
[!Include [defender-endpoint-setup-guide.md](../includes/mde-automated-setup-guide.md)]
4749

0 commit comments

Comments
 (0)