2.4.2. DLP Policy Requirements Across Locations, Including Copilot
💡 First Principle: DLP watches actions on data in specific places. A policy has three parts — where it applies (locations), what it looks for (conditions such as SITs or labels), and what it does (actions such as block, warn or notify) — so designing one means matching each requirement to a location first.
Locations for Microsoft 365 DLP policies: Exchange Online, SharePoint, OneDrive, Teams chat and channel messages, Devices (endpoint DLP), and the Microsoft 365 Copilot and Copilot Chat location. Endpoint devices must be onboarded to Purview before they can be policy locations; the Allow action exists only for device-scoped policies, and devices don't support email notifications. The recommended rollout is design, deploy in simulation mode, train users with policy tips, then enforce.
The Copilot location is newer and has its own rules — the Learn page is now titled DLP for Microsoft 365 Copilot and Cowork, and it covers Microsoft Copilot, Copilot Chat, Copilot Cowork, and Copilot in Word, Excel and PowerPoint:
| Condition | Action | Effect |
|---|---|---|
| Content contains a sensitivity label | Prevent Copilot from processing content | Labeled files and emails aren't used in responses (they may still appear as citations); in Word, Excel and PowerPoint, Copilot skills are disabled for those files |
| Content contains sensitive information types — in prompts | Prevent Copilot from processing content (processing prompts) | Copilot doesn't respond to the prompt, and it isn't used for internal or web search (preview) |
| Content contains SITs — for web search | Prevent web searches | Blocks web grounding only; Copilot still answers from internal data |
| Email received from external users | Prevent Copilot from processing content | External emails excluded from grounding and summaries (preview) |
Constraints that the exam can test:
- The Copilot location is available only in the Custom policy template, and selecting it disables every other location in that policy — you can't add it to an existing Exchange or SharePoint policy.
- The label and SIT conditions can't be combined in one rule — use separate rules in the same policy.
- DLP evaluates only typed prompt text, not files uploaded into a prompt.
- In Office apps the policy is evaluated when the file is opened, and policy changes can take up to four hours to apply.
- Copilot always runs as the prompting user — DLP excludes items; it never grants access. Scoping to administrative units follows the prompting user.
Who can create Copilot DLP policies: the Entra AI Administrator and Global Administrator, the Purview Data Security AI Admin role (which can't read prompts or responses), and the usual compliance roles such as Compliance Administrator and Information Protection Admin.
⚠️ Exam Trap: "Add the Microsoft 365 Copilot location to the existing DLP policy that protects SharePoint" is always wrong — the Copilot location needs its own policy from the Custom template. And excluding labeled content doesn't make those files invisible: they can still appear as citations.
Reflection Question: Compliance wants Copilot never to use documents labeled Highly Confidential, and never to respond to prompts containing customer passport numbers. How many policies and rules do you need, and why can't one rule do both?