Microsoft Purview DLP Adds Administrative Units for Copilot, Copilot Chat and Cowork

According to Microsoft's AI at Work roadmap under ID 575287, along with corresponding Microsoft 365 Message Center notice MC1486284, Microsoft Purview Data Loss Prevention is extending Administrative Units (AU) support to Microsoft 365 Copilot, Copilot Chat, and Cowork. Currently listed as in development for Worldwide Standard Multi-Tenant cloud instances on the web platform, the feature is scheduled to begin rolling out in preview in late October 2026, with general availability targeted for November 2026. As with all Microsoft roadmap estimates, these rollout timelines remain subject to change.

Closing a Documented Governance Gap​

To appreciate why this update matters for enterprise IT administration and cybersecurity teams, you only have to look at Microsoft Learn's existing documentation for the Microsoft 365 Copilot and Copilot Chat DLP policy location, which explicitly states that the location does not support Administrative Units.

In large multinational corporations, universities, or heavily regulated holding companies, compliance is rarely a single monolithic operation. A European privacy officer dealing with strict regional data rules, or a healthcare division administrator managing patient data boundaries, needs the ability to tailor AI guardrails for their specific workforce. Previously, Microsoft Purview supported Administrative Units across Data Lifecycle Management, Communication Compliance, Insider Risk Management, Sensitivity Labeling, and standard DLP locations—yet left Copilot DLP policies stuck at the whole-directory level.

With roadmap item 575287 and Message Center update MC1486284, organizations will be able to delegate management of supported Copilot DLP policies to administrators scoped to their assigned Microsoft Entra Administrative Units. Rather than introducing a brand-new administrative framework, this update builds directly on existing Microsoft Purview role-based access control (RBAC) and Administrative Unit capabilities. Scoped administrators will be able to create, view, edit, and delete supported Copilot DLP policies strictly within their assigned regional, departmental, or regulatory boundaries without holding tenant-wide policy-management permissions.

Best of all for cautious systems administrators, this configuration is entirely optional. Existing tenant-wide Copilot DLP policies will continue to apply without disruption, and underlying DLP enforcement functionality remains unchanged.

Section Summary: Microsoft is removing a major delegation bottleneck by bringing Microsoft Entra Administrative Unit scoping to Purview DLP policies for Microsoft 365 Copilot, Copilot Chat, and Cowork, starting with a planned late October 2026 preview and November 2026 general availability.

What Copilot and Cowork DLP Actually Protects​

Because this update changes who can manage policies rather than what the policies detect, it helps to examine what a scoped administrator will actually be governing. Following Microsoft's recent expansion of Purview DLP to cover Microsoft Cowork (tracked under Message Center notice MC1477182), existing and new DLP policies targeting the Microsoft 365 Copilot and Copilot Chat location automatically extend to Cowork as well.

According to Microsoft Learn documentation, the Microsoft 365 Copilot and Copilot Chat policy location currently provides four primary guardrails:

• Blocking External Web Search on Sensitive Prompts: When a user's prompt contains configured Sensitive Information Types (SITs)—such as credit card numbers, passport numbers, Social Security numbers, or custom organizational SITs—DLP prevents Copilot, Copilot Chat, and Cowork from sending that prompt to external web search providers like Bing for grounding. Instead, the AI continues generating a response using only permitted internal Microsoft 365 data sources.
• Blocking Sensitive Prompts Entirely (Preview): Organizations can block Copilot, Copilot Chat, Cowork, and Copilot in Word, Excel, and PowerPoint from returning any response at all—or using the text for internal or external searches—when a typed prompt contains specified out-of-the-box or custom SITs.
• Excluding Sensitivity-Labeled Files and Emails: Administrators can prevent Copilot, Copilot Chat, and Cowork from processing or summarizing files and Exchange emails carrying specific sensitivity labels (such as "Highly Confidential" or "Personal"). While the restricted item might still appear in response citations if the user holds access permissions, its contents are excluded from the AI summary.
• Blocking External Email Grounding (Preview): To mitigate prompt-injection risks and untrusted data influence, administrators can block Copilot and Copilot Chat from referencing, summarizing, or citing emails received from senders outside the tenant's accepted domains. This rule inspects sender domain metadata rather than the email body.

Section Summary: Delegated AU administrators will manage policies that govern sensitive prompt text, external web search grounding, sensitivity-labeled files and emails, and external email exclusions across Microsoft 365 Copilot, Copilot Chat, and Cowork.

Crucial Technical Boundaries Every Admin Should Know​

Before your regional compliance teams start celebrating their newfound autonomy, veteran IT administrators should make sure everyone understands the fine print of how Purview DLP and Administrative Units actually behave in practice. Based on Microsoft Learn's Purview documentation, several architectural quirks can trip up an unprepared team:

1. The Uploaded File Blind Spot: DLP for Copilot only inspects the text typed directly into a prompt. If a user attaches or uploads a file directly into a Copilot prompt for analysis, Purview DLP cannot scan the contents of that uploaded file during prompt evaluation.
2. Rule Separation Requirements: In the Purview policy builder, you cannot combine Content contains > Sensitive info types and Content contains > Sensitivity labels conditions inside the same rule. You must build separate rules for each condition within the policy.
3. Custom Template Exclusivity: The Microsoft 365 Copilot and Copilot Chat location is only accessible via the Custom policy template. Turning it on disables all other workload locations for that specific policy.
4. File Open Evaluation and Propagation Delays: In Word, Excel, and PowerPoint, sensitivity label DLP enforcement is evaluated when a file is opened. If a user applies a restricted sensitivity label mid-session, Copilot skills aren't blocked until the next time the file is opened. Furthermore, changes to a Copilot DLP policy can take up to four hours to take effect across the Copilot experience.
5. Policy and Historical Data Visibility for Restricted Admins: Under Microsoft Purview's general Administrative Unit model, once you assign AUs to role group members (making them "restricted administrators"), those administrators cannot view or edit pre-existing tenant-wide policies. Those global policies remain fully operational and visible to unrestricted administrators. Similarly, restricted administrators cannot view historical data in Activity Explorer or DLP Alerts prior to their scoping; going forward, they only see alerts and events tied to users in their assigned units.
6. Dynamic Group Caveats: While you can build Administrative Units in Microsoft Entra ID using dynamic membership rules for regions or departments, members of Dynamic Distribution Groups do not automatically become members of an Administrative Unit. Additionally, you cannot add groups to an AU that uses dynamic membership rules—requiring separate AUs if you need both dynamic user rules and static group assignments.

Section Summary: While AU support solves administrative delegation, technical constraints remain—including a four-hour policy propagation window, no DLP scanning for files uploaded directly into prompts, and strict visibility boundaries that hide pre-existing global policies from newly restricted admins.

How to Prepare Your Environment for Scoped Copilot DLP​

Even though no immediate action is required and tenant-wide policies will keep humming along, organizations planning to adopt delegated AI governance should review their directory architecture before the late October 2026 preview arrives. Here is a practical checklist based on Microsoft Purview's documented workflows:

1. Verify Licensing Prerequisites: General Purview Administrative Unit support requires Microsoft Entra ID P1 or P2 licensing alongside qualifying Microsoft 365 E5/A5/G5 or corresponding Compliance and Information Protection subscriptions. Confirm your tenant's specific entitlements for Copilot DLP and Purview RBAC before delegating roles.
2. Audit Microsoft Entra Administrative Units: Sign in to Microsoft Entra ID and verify that your regional, departmental, or subsidiary Administrative Units accurately reflect your intended compliance boundaries. Ensure user memberships are populated via direct assignment or supported dynamic rules rather than Dynamic Distribution Groups.
3. Review Purview Role Groups: In the Microsoft Purview portal, accounts creating or editing policies for the Microsoft 365 Copilot and Copilot Chat location require appropriate roles—such as Purview Data Security AI Admin, Compliance Administrator, Compliance Data Administrator, Information Protection Admin, or Security Administrator. Microsoft recommends assigning roles with the fewest privileges necessary rather than relying on Global Administrators.
4. Assign Admin Units to Delegated Admins: An administrator holding the Role management role can navigate to the relevant Purview role group (or create a custom role group, which always supports the Assign admin units option) and bind specific administrators to their respective Microsoft Entra Administrative Units.
5. Configure Custom Compliance Links: While reviewing your Copilot DLP rules, consider turning on Policy Tips and configuring the Provide a compliance URL setting. Instead of sending blocked users to a generic Microsoft Learn page, you can route the "Learn about access restrictions" link to an internal SharePoint page explaining your specific regional or corporate AI usage policy.

How is your organization handling the collision between rapid AI adoption and regional data sovereignty? Are you keeping Copilot governance locked down at the global tenant level, or will you be handing the keys to regional compliance teams as soon as Administrative Unit support hits general availability in November?

Section Summary: Administrators can prepare for the October preview and November 2026 rollout by auditing Microsoft Entra Administrative Unit memberships, verifying E5/Compliance and Entra P1/P2 licensing, and mapping least-privilege Purview AI and compliance roles to regional staff.