Risk · 08
A label is a boundary, not a sticker
Microsoft Learn's comparison of E3, E5 and E7 treats sensitivity labels, data loss prevention and retention as part of getting data ready for Copilot, not as paperwork beside it. A company new to AI often buys the assistant first and discovers the label programme second. The order shows up in the answers.
What differs by suite
On the Learn table, E3 can create custom labels and apply them by hand. E5 adds default label policies and automatic labelling, including containers such as a SharePoint site or a Teams space. E7 keeps that and adds the claim that sensitivity context flows to agents, and that data loss prevention can extend to agent interactions.
Retention is part of the same boundary
The homepage of this site already notes a roadmap item: Purview retention by last access for SharePoint and OneDrive, preview November 2026, general availability January 2027, roadmap 472030. If Copilot can read a file, how long the file lives is part of what it may see later.
Agents do not invent a cleaner estate
DSPM for AI, on the same Learn page, is wider on E5 and E7 than on E3, including visibility of prompts and responses at E5. That is a log of what was asked, which only helps if someone looks at it. FrontierOrg, fiction, refuses to publish a green board status over a red control.
Monday
Pick ten files a team would happily put in a Copilot prompt. Note which ones have a sensitivity label and which ones do not. Unlabelled is the finding.
Who is allowed to downgrade a label on a file Copilot has already used in an answer?
Sources: Microsoft Learn, E3, E5 and E7 licence features (opens in a new tab). Microsoft 365 roadmap 472030 (opens in a new tab).
Where this note mentions FrontierOrg, that is a fictional method for rehearsing a decision. It is not a company, not a client, and not a case study.