While servicing channels determine the update cadence, deployment rings are the mechanism used to specify who will be receiving software from a particular servicing channel. Deployment rings can be used to configure pilot groups for new releases. A common best practice is to include a handful of users from every department in each deployment ring.
The following table illustrates a sample of an organization might structure servicing channels and deployment rings for their users:
|
Deployment ring |
Servicing branch | Weeks after SAC release |
| Preview | Windows Insider | Pre-Semi-Annual Channel Release (monthly) |
| Ring 1 Pilot IT | Semi-Annual Channel | SAC + 0 Weeks |
| Ring 2 Pilot business users | Semi-Annual Channel | SAC + 4 weeks |
| Ring 3 Broad IT | Semi-Annual Channel | SAC + 6 weeks |
| Ring 4 10% Business users | Semi-Annual Channel | SAC + 8 weeks |
| Ring 5 90% of Business users | Semi-Annual Channel | SAC + 10 weeks until all devices deployed |
In the preceding table, Windows Insiders get the earliest builds. Then, pilot IT users get it upon release. Once IT is satisfied that it is working, they begin releasing to pilot business users. Pilot business users are a representative cross-section of the organization who can test in conjunction with their daily application usage and workflow.
After pilot users have verified that it has been successful for them, the deployment can proceed through the rings until the rest of the computers are updated.
Now, we'll shift the focus from the desktop to the Microsoft 365 admin portal.