M365 Playbooks1. Plan
Design a sensitivity label taxonomy people use
A short label taxonomy with plain names, protection per label, an owner, and policy defaults, tested with the people who will apply it.
- Duration
- 4 to 6 weeks
- Complexity
- Medium
Program · Information Management
Sensitivity labels
Design a label taxonomy people understand, roll it out in stages, and extend labels to sites, Teams and automatic labelling.
Lifecycle
2. Deploy
Roll out sensitivity labels in stages
Labels published to a pilot and then the organization, with SharePoint and OneDrive support, a safe default label and clear help.
- Duration
- 8 to 12 weeks
- Complexity
- Medium
3. Maintain
Keep labels accurate and in use
A monthly review of downgrades and label use, a quarterly taxonomy review, and a safe way to change or retire labels.
- Duration
- Ongoing; first cycle in 4 to 6 weeks
- Complexity
- Low
4. Refine
Extend labels to sites, Teams and automatic labelling
Container labels for sites and Teams, automatic labelling run in simulation first, default labels for sensitive libraries, and labels used in DLP.
- Duration
- 8 to 12 weeks
- Complexity
- High
↻ Refine feeds what you learn back into Plan.