M365 PlaybooksPurview · SharePoint · Teams · Exchange· Prepare · Adoption
Plan adoption for sensitivity labels
Purpose
Labels only work if people choose the right one without thinking hard about it. An adoption plan makes sure each group hears what changes for them, why, and what to do, at the moment it becomes relevant, and that what people struggle with feeds back into the labels and the guidance.
Overview
Who's affected and how, what each group hears in each Deploy phase, champions, and how feedback changes labels and guidance.
- Effort
- About 5 to 8 person-days, then a few hours a week
- Duration
- Drafted in 2 weeks; runs through Deploy
- Complexity
- Low
- Who's in the room
- Communications lead, taxonomy owner, champions in each department, service desk lead
- Beyond E5
- Nothing beyond Microsoft 365 E5.
Risk of not doing it
People meet labels as an unexplained prompt, pick whatever closes it, and the data looks labelled without meaning anything.
Key activities
The plan in order: what must be true first, what to decide, then how to configure the pilot and production.
Prerequisites
Map who's affected and how
Start from the impacts register in the Prepare playbook. Typical groups: everyone who writes documents and email; people who share with partners every day; executive assistants; site and team owners; report builders; and the service desk. For each, note what changes and what they gain.
Decisions
Decision: How do messages reach each group?
One announcement to everyone is forgotten by the time labels appear. Tie messages to the Deploy phases instead, following the site's lean change framework: inform before people see labels, explain while defaults and prompts arrive, sustain once enforcement starts.
Options
- One announcement to everyone
- Messages per audience, tied to the observe, nudge and enforce phases
Recommended default: Messages per audience, tied to the observe, nudge and enforce phases
Decision: Use champions?
A colleague who can say "use Confidential for this" in a team meeting does more than any email. One champion per department, briefed a week ahead of each phase, is usually enough.
Options
- No champions
- One champion per department
Recommended default: One champion per department
Pilot configuration
Build and test the assets
The one-page labelling guide (linked from the label policy's help link), real examples per department, a short FAQ built from the Prepare stage's known issues, and the messages themselves. Test them with the pilot group and rewrite whatever people misread.
Production configuration
Run the plan and listen
Send each message when its phase starts, and collect what people ask: service desk tickets, champion feedback, downgrade reasons. Each week, change the guide, the tooltips or the next message based on what you heard.
Make it enforceable
The help link in the label policy keeps the guide one click away inside Office apps, and the observe, nudge and enforce phases make sure no one meets an enforced rule they were never told about.
Partly enforced. The gaps are a risk until a mechanism covers them.
Test to sign-off
Brief championsChange: Inform
A week before each Deploy phase.
Move on when: Champions can explain the change in their own words
Inform before labels appearChange: Inform
Leadership message, then audience messages.
Move on when: Each group has heard what's coming and why
Explain during the nudge phaseChange: Explain
Examples, the guide and the FAQ, where people work.
Move on when: Questions are falling, not rising
Sustain through enforcementChange: Sustain
Onboarding, reminders where downgrades cluster, updated examples.
Move on when: Labels are part of onboarding
Common challenges
If youWrite messages in compliance language
What tends to happenPeople skim them and still don't know which label to use.
A better approachLead with an everyday example and one action.
If youStop listening after launch
What tends to happenThe same questions keep coming, and the guide drifts from reality.
A better approachKeep a weekly adjustment log until the last wave is enforced.
Checkpoints
Pilot
- Does every audience have messages for each phase?
- Has the pilot group read the guide and FAQ and found them clear?
Production
- Are champions briefed ahead of each phase?
- Is feedback changing the guide, tooltips or messages?
Success measures
Capture a baseline before you start, or you won't be able to show the change.
| Measure | Where you see it | Good direction |
|---|---|---|
| People who can name the right label for their work | Pulse survey or champion check-ins | Up |
| Label questions to the service desk | Service desk | Down |
Ready-to-use text
Message plan
Audience | Phase (observe / nudge / enforce) | Message | Channel | Sender | Date | What we want them to do
FAQ starters
Which label should I use? | Why does my document already have a label? | Why am I asked for a reason? | Why can't my partner open this file? | Why can't Copilot summarize this file? | Who do I ask?
Additional reading
Changelog
Changelog (1 version)
| Version | Date | Author | Change |
|---|---|---|---|
| 1 | Sev Derghazarian | First version. Facts checked against Microsoft Learn on 2026-10-15. |