Would your regional teams or subsidiaries like to manage their own DLP policies for Copilot, without touching the tenant-wide ones? That is precisely what Microsoft announces in message center post MC1486284: support for Microsoft Entra ID administrative units in Microsoft Purview Data Loss Prevention (DLP) policies that target Microsoft Copilot and Copilot Chat. This article details the timeline, the scope of the delegation, the constraints that still apply and the audits to run today to be ready.
What changes between late October and early November 2026
At the time of writing (October 4, 2026), the feature is not yet available. The Microsoft Learn pages consulted still state that the "Microsoft 365 Copilot and Copilot Chat" policy location does not support administrative units. The rollout described by MC1486284 covers the Worldwide, GCC, GCC High and DoD environments.
May 2026
DSPM and administrative units
According to the Purview what's new page, Data Security Posture Management (DSPM) supports administrative units, in parity with classic DSPM and DSPM for AI.
June 2026
External email condition (preview)
The condition "Email is received from > External users" enters preview for Copilot DLP protection.
Late October 2026
MC1486284 rollout begins
Administrative units become usable for Copilot DLP policies, on Worldwide, GCC, GCC High and DoD.
Early November 2026
Planned end of rollout
Microsoft expects to have finished by this date. No action is required on your part.
The change does not create a new administration model. It extends Purview role-based access control (RBAC) and existing administrative units to a location that was excluded until now.
What a delegated administrator will (and will not) be able to do
An administrator scoped to an administrative unit will be able to create, view, edit and delete the supported Copilot DLP policies within their unit. Tenant-wide policies and those of other units remain inaccessible to them.
| Topic | Unit-scoped administrator | Unrestricted administrator |
|---|---|---|
| Policies of their own unit | Create, read, edit, delete | Yes, depending on their Purview roles |
| Tenant-wide policies | Cannot edit | Yes, depending on their Purview roles |
| Policies of another unit | Cannot manage | Yes, depending on their Purview roles |
| Applicability of rule enforcement | Unchanged | Unchanged |
The enforcement engine does not change: only management delegation evolves. End users see no new experience, and tenant-wide policies keep working as they do today.
The Purview role is still mandatory
The DLP policy reference specifies that an administrator restricted to an administrative unit only targets their own units, and must also belong to a role or role group that administers DLP, for example Compliance administrator or Information Protection Admin. The unit limits the scope; it grants no rights by itself. The Purview Data Security AI Admin role makes it possible to edit Copilot-related DLP policies, without access to the content of prompts and responses.
How scope is evaluated: by the user, not by the content
The administrative unit boundary is determined by the user who starts the Copilot interaction, not by the owner or storage location of the referenced content. Copilot evaluates each interaction against all applicable policies: those of the tenant and those of the user's unit.
Concretely, imagine a multi-subsidiary organization. A user in subsidiary A asks Copilot about a document stored in subsidiary B's space. The policies of subsidiary A (plus those of the tenant) apply to this interaction, because the initiator belongs to A. This scenario illustrates the principle described by Microsoft; it is not a measured case.
This rule has a design consequence: user membership in units becomes part of your security posture. A user placed in the wrong unit inherits the wrong rules.
Copilot location constraints still apply
A Copilot policy limited to an administrative unit will follow the same constraints as any policy for this location. The Microsoft Learn documentation on DLP for Microsoft 365 Copilot and Copilot Chat lists several:
- the Copilot location exists only in the Custom policy template; selecting it disables all other locations in the policy;
- alerts, notifications and simulation mode are supported;
- sensitive information types (SITs) entered in the prompt can block processing or web search;
- files and emails carrying a sensitivity label are covered (emails sent from January 1, 2025);
- files uploaded into a prompt are not scanned: only the typed text is.
Tony Redmond (Office 365 for IT Pros) adds in his write-up on the Copilot DLP policy and blocking web searches that the default policy "Protect sensitive M365 Copilot interactions" ships in simulation mode, and that SITs created from a document fingerprint cannot be used in it.
SITs and labels: separate rules
SITs and sensitivity labels cannot be combined in a single rule. Plan two rules per policy if you cover both cases. Policy updates can also take up to four hours to be picked up by Copilot: do not test the change ten minutes after saving it.
Implementation: audit your administrative units before enabling
Microsoft recommends reviewing the unit structure and role assignments before delegating. The scripts below are read-only: they change nothing. They do not create any policy, because the feature is not yet rolled out.
- Module:
Microsoft.Graph.Identity.DirectoryManagement(Microsoft Graph PowerShell), installed withInstall-Module Microsoft.Graph.Identity.DirectoryManagement -Scope CurrentUser. - Minimum delegated permissions:
AdministrativeUnit.Read.AllandRoleManagement.Read.Directory. - Output: a console table and a CSV file
audit-unites-administratives.csvwith, per unit, the number of users, groups and Entra delegated administrators.
1# Connexion avec les scopes en lecture seule2Connect-MgGraph -Scopes 'AdministrativeUnit.Read.All','RoleManagement.Read.Directory' -NoWelcome3 4# Parcours de toutes les unités administratives du tenant5$rapport = foreach ($au in Get-MgDirectoryAdministrativeUnit -All) {6 # Membres de l'unité (utilisateurs, groupes, appareils)7 $membres = @(Get-MgDirectoryAdministrativeUnitMember -AdministrativeUnitId $au.Id -All)8 $utilisateurs = @($membres | Where-Object { $_.AdditionalProperties['@odata.type'] -eq '#microsoft.graph.user' })9 $groupes = @($membres | Where-Object { $_.AdditionalProperties['@odata.type'] -eq '#microsoft.graph.group' })10 11 # Administrateurs auxquels un rôle Entra est délégué sur cette unité12 $admins = @(Get-MgDirectoryAdministrativeUnitScopedRoleMember -AdministrativeUnitId $au.Id -All)13 14 [pscustomobject]@{15 UniteAdministrative = $au.DisplayName16 Id = $au.Id17 Utilisateurs = $utilisateurs.Count18 Groupes = $groupes.Count19 AdminsDelegues = $admins.Count20 }21}22 23# Affichage et export24$rapport | Sort-Object UniteAdministrative | Format-Table -AutoSize25$rapport | Export-Csv -Path .\audit-unites-administratives.csv -NoTypeInformation -Encoding UTF8The Entra assignments visible here do not replace the review of Purview role groups, which is done in the Microsoft Purview portal. Check that each administrator is attached only to the units they manage.
To inventory existing DLP policies before creating new ones, use the ExchangeOnlineManagement module with an account that is a member of a DLP role (for example Compliance administrator).
1# Connexion au service Security & Compliance2Connect-IPPSSession3 4# Inventaire des stratégies DLP du tenant avec leur mode5Get-DlpCompliancePolicy | Select-Object Name, Mode, Comment | Sort-Object Name | Format-Table -AutoSizeTo examine a single unit, two equivalent approaches:
1# Remplacez la valeur par l'identifiant d'une unité relevé dans le CSV2$auId = '00000000-0000-0000-0000-000000000000'3Get-MgDirectoryAdministrativeUnitMember -AdministrativeUnitId $auId -All |4 Select-Object Id, @{n='Type';e={$_.AdditionalProperties['@odata.type']}}Verifying the result and diagnosing discrepancies
Once the feature is available in your tenant, validate the behavior in simulation mode before enforcing a block. Microsoft recommends starting in simulation and applying least privilege.
Post-deployment checks
- A test administrator limited to one unit sees and edits only the policies of that unit
- The same account cannot edit a tenant-wide policy or one from another unit
- A Copilot interaction by a user in the unit does trigger the policy in simulation
- Alerts and incident reports are enabled before switching the mode to "On"
- At least four hours have passed between the last change and the test
| Symptom | Probable cause | Resolution |
|---|---|---|
| The unit administrator sees no policy | They belong to no DLP role or role group, or the policy is not in their unit | Add a suitable DLP role (Compliance administrator, Information Protection Admin) and check the target unit |
| The change has no effect | Propagation delay, up to four hours | Wait, then retest with a user of the unit |
| A file uploaded into the prompt is not blocked | Only typed text is scanned | Complement with storage controls, or with rules on sensitivity labels |
| Cannot combine SIT and label | Copilot location limit | Create separate rules in the same policy |
| A document fingerprint SIT is rejected | Not supported by the Copilot policy | Use another SIT type |
Frequently asked questions
Do we need to act if we do not use administrative units?
No. Microsoft states that no action is required and that organizations without administrative units do not need to change their existing Copilot policies. Tenant-wide policies keep working as they do today.
Which license is needed for this feature?
The message center post specifies that the license requirements of Microsoft Purview DLP and Microsoft Copilot continue to apply, with no additional license specific to this change. To compare editions, see our Purview DLP license matrix.
Will end users see a difference?
No. No new experience is introduced for them. Copilot keeps evaluating each interaction against the tenant policies and those of the user's unit.
Does content stored in another unit change the policy applied?
No. The boundary is determined by the user who initiates the interaction, not by the owner or location of the referenced content.
Where to start
The rollout requires no action, but delegation is only worthwhile if your units and roles are clean. Prepare the ground before the end of October 2026.
Next actions
- Run the audit script and fix empty or poorly populated units
- Review Purview role groups: each administrator is assigned only to the units they manage
- Review your tenant-wide Copilot DLP policies before creating per-unit ones
- If the default policy "Protect sensitive M365 Copilot interactions" is in simulation, remove unneeded SITs, add missing ones and enable incident reports
- Plan simulation-mode tests as soon as the feature appears in your tenant
If your organization is centralized, keep a single administration: Microsoft Education recommended this as long as support did not exist, and delegation brings nothing without local teams to empower. If you manage several entities with distinct regulatory constraints, delegation by unit becomes relevant, provided you have made user membership reliable. To place this work in context, our Purview data governance map and our update on Purview in September 2026 give the background, and the article on network DLP and unmanaged AI covers the other side of protection against leaks to AI.
Going further
- Microsoft Purview DLP for Microsoft 365 Copilot and Copilot Chat: conditions, actions, limits and required roles for Copilot policies.
- Data Loss Prevention policy reference: difference between an unrestricted administrator and one restricted to a unit.
- Administrative units in Microsoft Purview: how administrative units work in Purview.
- DLP Policy for Copilot Can Block Web Searches: Tony Redmond's hands-on feedback on the default policy.
- What’s new in Microsoft Purview: tracking of Purview updates, including DSPM and administrative units.



