2.4. Protect Data in Microsoft 365 with Microsoft Purview
💡 First Principle: Data protection is three questions asked in order: what is this data (classification), what may happen to it (protection and loss prevention), and how long must it exist (lifecycle). Copilot doesn't add a fourth question — it makes the first three urgent, because it can reach and recombine any data a user is permitted to see.
Why care? With Copilot in the tenant, Purview is the safety net. A label's encryption decides whether Copilot can extract a document's content. A DLP policy for the Copilot location decides whether labeled content or sensitive prompts are processed. Retention decides how long Copilot interactions are kept as business records. And DSPM tells you where AI is touching sensitive data in the first place.
A useful mental model is three roles. Sensitivity labels are the lock — they travel with the item and carry encryption and markings. DLP is the guard — it watches activities (sending, sharing, copying, prompting) and blocks or warns. Retention is the archivist — it keeps what must be kept and deletes what must go, regardless of what users want.
⚠️ Common Misconception: Many people believe sensitivity labels filter Copilot's output by classification. They don't, directly. A label protects content through its encryption usage rights — Copilot needs both VIEW and EXTRACT to summarize an encrypted item — and Copilot's output inherits the label of its sources. Excluding labeled content from Copilot responses is a job for a DLP policy on the Copilot location.