add deployment ring table

This commit is contained in:
Joey Caparas
2020-10-20 16:08:50 -07:00
parent 7a9e85ea3a
commit ff1b1e6b9d
2 changed files with 21 additions and 0 deletions

View File

@ -41,6 +41,27 @@ There are three phases in deploying Microsoft Defender ATP:
There are several methods you can use to onboard to the service. For information on other ways to onboard, see [Onboard devices to Microsoft Defender ATP](onboard-configure.md). There are several methods you can use to onboard to the service. For information on other ways to onboard, see [Onboard devices to Microsoft Defender ATP](onboard-configure.md).
## Deploy Microsoft Defender ATP in rings
Deploying Microsoft Defender ATP can be done using a ring-based deployment approach.
A ring-based approach is a method of identifying a set of machines to onboard with specific timelines and verifying that certain criteria are met before the deploying to a larger set of devices.
Adopting a ring-based deployment helps reduce potential issues or conflicts that could arise while rolling the service out. By piloting a certain number of devices first, you can identify potential issues and mitigate potential risks that might arise.
Table 1 provides an example of the deployment rings you might use.
**Table 1**
|**Deployment ring**|**Description**|
|:-----|:-----|
Pilot and deployment planning | Phase 1: Identify 50 systems for pilot testing - Focus on the security team, IT team and maybe Helpdesk
Full scale pilot | Phase 2: 100 systems <br> Phase 3: 150 systems <br> Phase 4: 500 systems <br> Phase 5: 1000 systems <br><br> Review and assess if there required tweaks to deployment.
Full deployment | Roll out service to the rest of environment in larger increments.
## In Scope ## In Scope
The following is in scope for this deployment guide: The following is in scope for this deployment guide: