Microsoft Purview DLP for Microsoft 365 Copilot: Scoping Policies with Administrative Units via PowerShell

๐Ÿค– AI Executive Brief & TL;DR Purview DLP ยท Microsoft 365 Copilot
What you need to know
  • Copilot is its own DLP location. Policies target it with the location ID 470f2276-e011-4e9d-a6ec-20768be3a4b0 and the CopilotExperiences enforcement plane.
  • The rule action is "exclude from processing". Matching files and prompts aren't used to ground Copilot responses. Copilot DLP doesn't block the user from opening the file.
  • Regional teams can own their own policies. -PolicyRBACScopes scopes a policy to an Entra administrative unit, so an EMEA admin only sees and manages EMEA policies.
Connect-IPPSSession; Get-DlpCompliancePolicy | Select Name, Mode, Workload

Most Copilot data-exposure problems are permission problems: Copilot can only ground on content the user can already open. Fixing oversharing is the long-term answer (see our Copilot tenant security runbook). But oversharing cleanup takes months. Purview DLP for Microsoft 365 Copilot is the control you can turn on this week. It stops Copilot from processing content that carries specific sensitivity labels or sensitive information types, even when the user technically has access.

This guide covers how the Copilot DLP location works, how to create the policy and rules in PowerShell, and how to delegate policies to regional compliance teams with Entra administrative units.

NOTE:
Lab status: The Graph and Autodiscover checks in today's posts were run against the LAB 365 dev tenant. The Purview cmdlets in this post were not lab-run: the lab host doesn't have the ExchangeOnlineManagement module installed yet. They follow Microsoft's documented syntax. Run them in a test policy (-Mode TestWithoutNotifications) first.

How Copilot DLP evaluates a prompt 1. User prompt Copilot Chat, Word, Teams, Cowork User scope checked (tenant or admin unit) 2. Grounding Semantic Index finds files the user can read Labels and SITs on each file evaluated 3. DLP rule match Label or SIT matches a Copilot DLP rule Item excluded from content processing 4. Response Built only from allowed content Match logged in Activity explorer The user can still open the file directly; DLP only removes it from Copilot's grounding.

1. Prerequisites

RequirementDetail
LicensingMicrosoft 365 Copilot for the users in scope, plus a Purview licence that includes DLP for Copilot (E5 or E5 Compliance).
RoleCompliance Administrator or Compliance Data Administrator. For admin-unit scoped policies, the regional admin needs the role assigned scoped to that admin unit.
ModuleExchangeOnlineManagement v3.x for Connect-IPPSSession.
LabelsSensitivity labels already published, if you want label-based rules (recommended).
POWERSHELL
Install-Module ExchangeOnlineManagement -Scope CurrentUser
Connect-IPPSSession -UserPrincipalName [email protected]

2. Create a tenant-wide Copilot DLP policy

Copilot uses the Applications workload with a fixed location ID. The policy also needs the CopilotExperiences enforcement plane.

POWERSHELL
# Microsoft 365 Copilot DLP location
$copilotLocation = @'
[{"Workload":"Applications","Location":"470f2276-e011-4e9d-a6ec-20768be3a4b0","Inclusions":[{"Type":"Tenant","Identity":"All"}]}]
'@

New-DlpCompliancePolicy -Name "Copilot - Block Highly Confidential" `
    -Comment "Exclude Highly Confidential content from Copilot grounding" `
    -Mode TestWithoutNotifications `
    -Locations $copilotLocation `
    -EnforcementPlanes @("CopilotExperiences")

Start in TestWithoutNotifications mode. That lets you see matches in Activity explorer without changing what users get back from Copilot.


3. Add the rule: exclude labelled content from processing

The rule matches a sensitivity label and tells Copilot not to process the matching item.

POWERSHELL
# Find the label GUID
Get-Label | Select-Object DisplayName, ImmutableId

$labelId = "<ImmutableId of 'Highly Confidential'>"

New-DlpComplianceRule -Name "Copilot - Highly Confidential label" `
    -Policy "Copilot - Block Highly Confidential" `
    -ContentContainsSensitiveInformation @{
        operator = "And"
        groups   = @(@{
            operator = "Or"
            name     = "Default"
            labels   = @(@{ name = $labelId; type = "Sensitivity" })
        })
    } `
    -RestrictAccess @(@{ setting = "ExcludeContentProcessing"; value = "Block" })

To match on sensitive information types instead (for example credit card numbers in prompts), swap the label group for a sensitivetypes entry. If you have the choice, label-based rules are more predictable than pattern matching.


4. Delegate to regional teams with administrative units

Large tenants rarely want one central team owning every Copilot policy. Purview supports administrative-unit scoped policies:

  1. Create the admin unit in Entra (e.g. AU-EMEA) and add its users. Dynamic membership on country works well.
  2. Assign the EMEA compliance admin the Compliance Administrator role scoped to AU-EMEA in the Purview portal (Roles & scopes โ†’ Role groups).
  3. Create the policy with -PolicyRBACScopes so only users in that unit are evaluated, and only scoped admins can see it.
POWERSHELL
# Object ID of the Entra administrative unit
$auEmea = (Get-MgDirectoryAdministrativeUnit -Filter "displayName eq 'AU-EMEA'").Id

$emeaLocation = @'
[{"Workload":"Applications","Location":"470f2276-e011-4e9d-a6ec-20768be3a4b0","Inclusions":[{"Type":"Tenant","Identity":"All"}]}]
'@

New-DlpCompliancePolicy -Name "Copilot - EMEA Customer Data" `
    -Mode TestWithoutNotifications `
    -Locations $emeaLocation `
    -EnforcementPlanes @("CopilotExperiences") `
    -PolicyRBACScopes $auEmea
IMPORTANT:
An admin-unit scoped policy only applies to users in that unit. Keep one tenant-wide baseline policy (section 2) so users outside every regional unit are still covered.

5. Audit what you have

POWERSHELL
Get-DlpCompliancePolicy |
    Select-Object Name, Mode, Enabled, PolicyRBACScopes, WhenChanged |
    Format-Table -AutoSize

Get-DlpComplianceRule |
    Select-Object Name, ParentPolicyName, Disabled |
    Format-Table -AutoSize

Once matches look right in Purview โ†’ Data loss prevention โ†’ Activity explorer (filter on Activity: DLP rule matched, Location: Microsoft 365 Copilot), switch the policy to enforce:

POWERSHELL
Set-DlpCompliancePolicy -Identity "Copilot - Block Highly Confidential" -Mode Enable

6. Rollout checklist

  • [ ] Sensitivity labels published and applied to your most sensitive libraries
  • [ ] Tenant-wide Copilot DLP baseline created in test mode
  • [ ] Regional admin units created, with scoped Compliance Administrator role assignments
  • [ ] Regional policies created with -PolicyRBACScopes
  • [ ] Two weeks of Activity explorer review before switching to -Mode Enable
  • [ ] Oversharing remediation still running in parallel. DLP buys time but doesn't replace fixing permissions