# Plan adoption for sensitivity labels - URL: https://m365playbooks.com/playbooks/plan-adoption-for-sensitivity-labels/ - Topic: Sensitivity labels and label policies (Program) - Product: Purview, SharePoint, Teams, Exchange - Stage: Prepare - Last reviewed: October 15, 2026 - Version: 1 - Written by: Sev Derghazarian ## 1. 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. ## 2. 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. ## 3. Key activities ### Prerequisites 1. **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. Who: Communications lead. Produces: An audience map. ### Decisions 2. **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. Who: Communications lead. Produces: A message plan per audience and phase. 3. **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. Who: Taxonomy owner. Produces: A champion list, or a recorded reason not to. ### Pilot configuration 4. **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. Who: Communications lead with champions. Produces: Tested guide, FAQ and messages. ### Production configuration 5. **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. Who: Communications lead. Produces: A weekly adjustment log. 6. **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._ ## 4. Test to sign-off 1. **Brief champions** (Change: Inform) A week before each Deploy phase. Move on when: Champions can explain the change in their own words. 2. **Inform before labels appear** (Change: Inform) Leadership message, then audience messages. Move on when: Each group has heard what's coming and why. 3. **Explain during the nudge phase** (Change: Explain) Examples, the guide and the FAQ, where people work. Move on when: Questions are falling, not rising. 4. **Sustain through enforcement** (Change: Sustain) Onboarding, reminders where downgrades cluster, updated examples. Move on when: Labels are part of onboarding. ## 5. Common challenges - **If you** Write messages in compliance language. What tends to happen: People skim them and still don't know which label to use.. A better approach: Lead with an everyday example and one action. - **If you** Stop listening after launch. What tends to happen: The same questions keep coming, and the guide drifts from reality.. A better approach: Keep a weekly adjustment log until the last wave is enforced. ## 6. 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? ## 7. Success measures Capture a baseline before you start, or you won't be able to show the change. - People who can name the right label for their work (Where you see it: Pulse survey or champion check-ins; Good direction: Up) - Label questions to the service desk (Where you see it: Service desk; Good direction: Down) **Ready-to-use text: Message plan** > Audience | Phase (observe / nudge / enforce) | Message | Channel | Sender | Date | What we want them to do **Ready-to-use text: 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? ## 8. Additional reading **Plan:** - [Get started with sensitivity labels](https://learn.microsoft.com/en-us/purview/get-started-with-sensitivity-labels) - [Introduction to secure by default with Microsoft Purview](https://learn.microsoft.com/en-us/purview/deploymentmodels/depmod-secure-by-default-intro) **Configure:** - [Apply sensitivity labels to your files](https://support.microsoft.com/en-us/office/apply-sensitivity-labels-to-your-files-and-email-2f96e7cd-d5a4-403b-8bd7-4cc636bae0f9) ## Changelog - Version 1, 2026-10-15, Sev Derghazarian: First version. Facts checked against Microsoft Learn on 2026-10-15.