By Michael Branson

Quick answer. As of September 2026, Microsoft Purview endpoint DLP can audit or block sensitive files being copied to USB drives, network shares, the clipboard, printers, unallowed Bluetooth apps and remote desktop sessions, or uploaded to restricted cloud domains, on onboarded Windows 10, Windows 11 and macOS devices (the three latest released major versions), and Teams DLP can block chat and channel messages that carry sensitive information, but Microsoft documents blind spots in both: according to Learn about Endpoint data loss prevention, endpoint DLP cannot scan data that is never saved to a local file, and according to Data loss prevention and Microsoft Teams, Teams DLP does not follow your users into a chat another tenant started. Microsoft says Teams chat DLP requires an E5 license, while E3 already covers files shared through Teams because they live in SharePoint and OneDrive. Microsoft’s Plan for Microsoft Purview compliance and risk management solutions – GCC High deployments table lists endpoint DLP and Teams chat and channel conversations as Available, with status subject to change, and does not itemize the sub-features, so confirm each one in the tenant.

The audit finding names the exits in plain words: data leaving by USB drive, by printer, by browser upload and by chat. The licence request that answers it names two features, endpoint DLP and Teams DLP, and it is on your desk to sign. You suspect the control is not as complete as the feature list reads, but you do not yet know where Microsoft itself says it is blind, and for a GCC High tenant you cannot tell which parts are actually there. Go wrong one way and you sign the upgrade, tell the auditor USB and chat are covered, and later learn that a file saved straight from Word to a USB drive was never inspected, that channel messages sat outside a policy scoped to individual users, or that a chat another company started was never evaluated against your policies. Go wrong the other way and you refuse the upgrade because a vendor pitch says the Microsoft control is weak, and keep a gap the documented controls would have closed. This guide sets out what each control stops, where Microsoft documents it is blind, what the licence line covers and what Microsoft’s government tables confirm, in Microsoft’s own words, so the coverage statement you give the auditor is one you can defend.

What endpoint DLP sees and stops on a device

When the audit names exit paths, your first mistake would be to assume every exit it names is one endpoint DLP watches. Microsoft’s Learn about Endpoint data loss prevention lists the activities it can audit and restrict on sensitive items stored on Windows 10, Windows 11 and macOS devices (the three latest released major versions), with Windows Server 2019 and later supported as well:

  • Upload to a restricted cloud service domain, or access from an unallowed browser; a user on an unallowed browser is blocked and redirected to Microsoft Edge, which then allows or blocks the upload by policy.
  • Paste to supported browsers, in preview on macOS.
  • Copy to clipboard, including redirected clipboards when using Azure Virtual Desktop with Windows 365.
  • Copy to a USB removable device.
  • Copy to a network share.
  • Print.
  • Copy or move using an unallowed Bluetooth app.
  • Copy or move using a remote desktop session, not supported on macOS.
  • Create an item and rename an item, auditable only.
  • Access by restricted apps.
  • Create Windows Recall snapshots, in preview and not on macOS.

Scope decides whether any of that is enforced. The same Microsoft page states: “For a DLP policy to be enforced on an endpoint, both the user and the device must be included in the policy scope.” Microsoft’s Microsoft Purview service description puts the timing of that check plainly: “Policies are evaluated when a scoped user logs onto an onboarded device.” The scan itself is broader than the enforcement; Microsoft’s Learn about Endpoint data loss prevention states: “All devices that are onboarded into Purview are scanned regardless if the user is in scope.”

Auditing starts before any policy exists. Microsoft’s Learn about Endpoint data loss prevention states: “Once a device is onboarded, information about audited activities flows into Activity explorer even before you configure and deploy any DLP policies that have devices as a location.” Microsoft’s Configure endpoint data loss prevention settings adds: “By default, when you onboard devices, the system automatically audits activity for Office, PDF, and CSV files.”

What gets inspected is set by file type. Microsoft’s Learn about Endpoint data loss prevention lists the monitored families (Office, PDF, text, HTML, JSON, mail, XML, archives and protected files), adds image files only when OCR is enabled, and states: “Endpoint DLP scans files with the specified extensions listed above.” For items that have never been evaluated, or whose evaluation has gone stale, the same page describes just-in-time protection: “Just-in-time protection blocks egress activities on these monitored files until policy evaluation completes successfully”.

Planning rule: list every exit path the audit names, map each one to the activity above that covers it, and write down the action you will set for it (audit, block with override, or block). An exit with no activity beside it is not covered by endpoint DLP, whatever the licence says.

Where endpoint DLP is blind, in Microsoft’s words

The failure that surprises teams most is a file that never touched the disk. Microsoft’s Learn about Endpoint data loss prevention states: “If data is never saved to a file on the local device, Endpoint DLP cannot scan or classify it.” It gives the example an auditor will recognize: “For example, if a user opens a document in Word and saves it directly to a USB device without first storing it locally, Endpoint DLP cannot inspect or block that action.” For removable media Microsoft points to a different control of its own, and the same page states: “If you’re looking for device control for removable storage, see Microsoft Defender for Endpoint Device Control Removable Storage Access Control.”

Content that endpoint DLP cannot read is a second class of gap. Microsoft’s Learn about Endpoint data loss prevention lists file types it does not monitor at all (executables, libraries, drivers, system and settings files, and partial downloads among them) and says of the feature for unsupported extensions: “In contrast, the Apply restrictions to only unsupported file extensions feature does not scan file content.” Microsoft’s Data Loss Prevention policy reference states: “Encrypted files can’t be inspected for sensitive info types or trainable classifiers.” And the same endpoint page states: “Endpoint DLP cannot detect the sensitivity label from another tenant on a document.”

Browser paste and clipboard copy carry narrower rules than the activity names suggest. Microsoft’s Configure endpoint data loss prevention settings states: “Advanced classification doesn’t work for text files larger than 64 MB, even if you set the bandwidth limit to Do not limit bandwidth.” It also states: “The Paste to browser action doesn’t support advanced classification.” For paste, Microsoft’s Learn about Endpoint data loss prevention states: “Evaluation is performed on the content that is being pasted.” For clipboard copy, the same page states: “If the rule is configured to Block or Block with override copying is blocked when the source content is sensitive except when the destination is within the same Microsoft 365 Office app.”

Servers are not laptops. Microsoft’s Learn about Endpoint data loss prevention states: “Endpoint DLP is not supported on Windows Servers configured as Domain Controllers or Windows Servers with the Core Server option selected during installation.” On the servers it does support, the same page states: “By default, Endpoint DLP isn’t enabled for Windows servers when they’re initially onboarded.” It adds: “Installing the supported Windows Server KBs disables the Classification feature on the server.”

Virtual desktops change what a copy looks like. Microsoft’s Get started with endpoint data loss prevention states: “You can’t monitor Copy to Clipboard and Enforcing Endpoint DLP on Azure Virtual Desktop environments via browsers.” For USB drives in virtualized environments it states: “USB storage devices are treated as network shares.” The same page states: “You need to include the Copy to network share activity to monitor Copy to a USB device.”

A fleet with Macs needs its own list. Microsoft’s Learn about Endpoint data loss prevention marks these macOS differences in its activity and settings tables:

  • Copy or move using a remote desktop session: not supported on macOS.
  • Paste to supported browsers: in preview on macOS.
  • VPN settings: not supported on macOS.
  • Access by apps not included in the restricted apps list or groups: not supported on macOS.
  • Set evidence cache on device: in preview on macOS.
  • Offline enforcement: for a Windows device that goes offline, existing policies keep being enforced, just-in-time protection in block mode holds a new file until evaluation completes, and policy changes arrive when the device reconnects; of that offline behaviour the page states: “This functionality isn’t supported on macOS endpoint devices.”

Offline devices and policy changes lag. Microsoft’s Learn about Endpoint data loss prevention states: “Policies that are updated while a device is offline won’t be pushed to that device.” It also states: “While policies that have already been pushed to an offline device are enforced, the enforcement events don’t appear in activity explorer until the device is back online.” And for every change: “When a policy is updated in Microsoft Purview portal, it generally takes about an hour for those updates to be synchronized across the service.”

Planning rule: for each blind spot above, write down one of three answers before the auditor asks: closed by another named Microsoft control, closed by configuration, or accepted as a documented limitation with its owner. A blind spot with no answer is the line the audit will find.

What Teams DLP does to a message, and to a file

If someone in your tenant posts an account number in a chat, that is the case Teams DLP is bought for, and the first question is what actually happens to that message. Microsoft’s Microsoft Purview service description states: “With DLP for Teams, organizations can block chats and channel messages that contain sensitive information, such as financial information, personally identifying information, health-related information, or other confidential information.”

Messages to guests carry a condition that decides most external cases. Microsoft’s Data loss prevention and Microsoft Teams states: “If you have a DLP policy defined in your tenant to prevent this, messages with sensitive information that are sent to external users are deleted.” The next sentence sets the limit: “However, your tenant must be the initiator of the chat or the thread.”

Files travel a different route from messages. For a document shared with guests in a Teams chat or channel, the same Microsoft page says the document will not open for them if a DLP policy is defined to prevent it, and states: “Your DLP policy must include SharePoint and OneDrive in order for protection to be enforced.” Users are told differently too: “DLP for Microsoft Teams does not send user notification emails like DLP for Exchange, SharePoint, and OneDrive.” Instead the page says users receive message flags only. After adding the Teams location to a policy, the page states: “Allow approximately one hour for your changes to work their way through your data center and sync to user accounts.”

Combining locations narrows how a policy matches. Microsoft’s Data Loss Prevention policy reference states: “But, when you select SharePoint sites and Teams chat and channel messages locations, the policy will only support detecting sensitive items by SIT.” If a pilot policy is flagging too much, tuning it is a separate guide’s subject.

Planning rule: put Teams chat and channel messages and the SharePoint and OneDrive locations in the policy together, or the file half of the chat is not covered, and tell users that a blocked message shows as a flag in Teams, not as an email.

Where Teams DLP stops: scoping, shared channels and other tenants’ chats

When the policy that looked complete in your pilot was scoped to named users, channel messages were never in it. Microsoft’s Data loss prevention and Microsoft Teams sets out how the policy scope decides what is protected:

  • Scoped to individual user accounts: one-to-one and group chats are protected; standard, private and shared channel messages are not.
  • Scoped to security groups, distribution groups or non-mail-enabled security groups: chats and channel messages are both protected.
  • Scoped to Microsoft 365 groups: chats and channel messages are both protected.

Shared channels follow the sender, not the channel. Microsoft’s Data loss prevention and Microsoft Teams states: “Because DLP evaluation is driven by the sender’s identity, each user’s messages are evaluated against the DLP policies of their own tenant, regardless of which tenant owns the shared channel.” So members from another organization in your shared channel are evaluated against their own organization’s policies, not yours.

Chats with people in another organization follow the host. For external access chats, the same page states: “DLP policy enforcement in these cross-tenant conversations is based on the hosting tenant, which is the tenant that initiated the chat or thread.” It draws the consequence itself: “Therefore, in a cross-tenant conversation, a user’s home-tenant DLP policies don’t automatically follow the user into a conversation hosted by another tenant.”

Planning rule: scope Teams policies to groups wherever channels carry regulated data, and write down, in the coverage statement, that chats another organization starts and messages its members send in shared channels are governed by that organization’s policies, not yours.

What the E3 line already covers, and what needs E5

When your licence request arrives as one line, E5 for DLP, what it adds is narrower than that line suggests. Microsoft’s Data loss prevention and Microsoft Teams states: “Office 365 and Microsoft 365 E3 include DLP protection for SharePoint, OneDrive, and Exchange.” It continues: “This also includes files that are shared through Teams because Teams uses SharePoint and OneDrive to share files.” The message half is the part that moves: “Support for DLP protection in Teams Chat requires an E5 license.” The licence decision itself, and what E5 costs, is covered in Microsoft 365 E3 vs E5 Cost: What E5 Really Costs and When to Upgrade.

For endpoint DLP, Microsoft’s Microsoft Purview service description lists these licences in its endpoint DLP row:

  • Microsoft 365 E5/A5/G5.
  • Microsoft Purview Suite/EDU/GOV/FLW, and Microsoft Defender + Purview Suite FLW.
  • Microsoft 365 E5/A5/F5/G5 Information Protection & Governance.

For Teams, Microsoft’s Microsoft Purview service description adds that turning on DLP for Teams needs the Microsoft Communications DLP service selected, under one of the licences it lists for DLP for Teams, in the Microsoft 365 administration portal.

Planning rule: separate the file-sharing risk the E3 line already covers from the message and device risk the upgrade buys, and put only the second in the business case.

GCC and GCC High: what Microsoft’s tables confirm, and what they leave to the tenant

If your tenant is GCC High, the question is not whether endpoint DLP exists but which parts of it are there, and Microsoft’s tables answer only the first half. Microsoft’s Plan for Microsoft Purview compliance and risk management solutions – GCC High deployments, last updated May 21, 2025, marks the row “Endpoint data loss prevention” as “Available”, the row “Teams chat and channel conversations” as “Available” and the row “Data surfaced in Activity Explorer” as “Available”, as it does the alerts dashboard, files in SharePoint, OneDrive and email, and the on-premises scanner. Its footnote states: “Identified status is subject to change as project plans and priorities are reevaluated.” In the same table the row “Content explorer includes Teams data” reads “In development”.

Microsoft’s Plan for Microsoft Purview compliance and risk management solutions – GCC deployments marks the same endpoint and Teams rows “Available”, carries the same footnote, and also lists Content explorer for Teams data as “In development”.

Both tables list endpoint DLP and Teams DLP as single rows. Neither itemizes the endpoint activities, just-in-time protection, macOS support, Windows Recall, network share coverage, evidence collection, browser restrictions, shared-channel behaviour or cross-tenant chats, so whether any one of those runs in a given GCC High tenant is not stated on either page as read for this guide in September 2026. This guide does not say any of them works or fails there.

Devices reach DLP through Defender onboarding, and Microsoft’s Learn about Endpoint data loss prevention states: “Onboarding devices to Defender also onboards them to DLP.” For government clouds, Microsoft’s Microsoft Defender for Endpoint for US Government customers states: “This offering is available to GCC, GCC High, and DoD customers and is based on the same prevention, detection, investigation, and remediation as the commercial version.” It adds: “However, there are some differences in the availability of capabilities for this offering.” And it states: “Defender for Endpoint for US Government customers doesn’t have complete parity with the commercial offering.” None of the known gaps that page lists is a DLP feature, and this guide reads that sentence only as what it says about Defender for Endpoint.

Planning rule: before the auditor sees a coverage statement, confirm each activity, setting and scoping behaviour this guide lists in the tenant itself, record how it was confirmed, and treat the table’s Available as a starting point, not the answer.

What the auditor can be shown

The audit that follows the rollout asks for evidence, not configuration, and the evidence has to exist before enforcement starts. Activity from an onboarded device reaches Activity explorer from onboarding, as the endpoint section above sets out, and for each audited activity Microsoft’s Learn about Endpoint data loss prevention lists the attributes recorded; for a copy to a USB device they include:

  • The file name, its path and its extension.
  • File hashes and the sensitive information type matched.
  • The device name and the application that performed the copy.
  • The removable media manufacturer, model and serial number.

The matched items themselves can be kept as well. Microsoft’s Configure endpoint data loss prevention settings states: “When DLP identifies items that match policies on devices, it can copy them to an Azure storage account.” The same page says that copy is useful for auditing policy activity and troubleshooting specific matches. Remember the offline lag from the blind-spot section: events from a disconnected device appear only after it is back online. Detecting CUI itself is a separate guide’s subject.

Planning rule: decide which evidence is kept, where it is stored and for how long, and who can read it, before the first policy moves from audit to block.

When these controls are the wrong answer

If an audit line is not an endpoint DLP or Teams DLP problem at all, the honest answer is to say so. Microsoft’s Learn about Endpoint data loss prevention and Data loss prevention and Microsoft Teams mark the edges:

  • The work never lands on the device as a file: endpoint DLP will not see it. DLP for cloud apps in the browser and on the network are separate Purview capabilities this guide does not describe.
  • Removable media control is the whole requirement: Microsoft itself points to Microsoft Defender for Endpoint Device Control for removable storage.
  • The data sits on domain controllers or Server Core installations: endpoint DLP is not supported there.
  • Collaboration runs mostly in chats and channels other organizations host: their policies apply, not yours.
  • The real question is whether another DLP product is better: that is a product decision this guide does not make.
  • The real question is detecting CUI, or what the licence costs: detection is a separate guide’s subject, and cost is covered in the E3 and E5 guide linked above.

What to ask of whoever helps you deploy it, and how i3solutions answers

Whoever helps you deploy endpoint DLP and Teams DLP, hold the work to criteria drawn from Microsoft’s Learn about Endpoint data loss prevention and Data loss prevention and Microsoft Teams:

  • Show every exit path the audit names mapped to an endpoint activity or a Teams location, with the action set for it.
  • Show every Microsoft-documented blind spot on this page with how it is closed or why it is accepted, and who owns it.
  • Show the Teams policy scope, groups or individual accounts, and what it leaves out.
  • Show which sub-features were confirmed in your GCC High tenant, and how each was confirmed.
  • Show the evidence kept, in Activity explorer and in any evidence storage account, where it is stored and who can read it.
  • Hand the policies and the runbook to your team to operate.

i3solutions maps governance to named control families, enforces it in the platform through Entra ID, Purview, and Azure Policy, and evidences it continuously rather than reconstructing it at audit. i3solutions builds and tests Purview DLP policies as part of a CMMC Level 2 implementation. The work is delivered as a project, with specialists embedded in your team where it needs them: map the audit’s exit paths to endpoint DLP and Teams DLP, build and test the policies, confirm what your tenant, including a GCC High tenant, actually offers, and evidence the result against your control families. For government-cloud estates, i3solutions installs and helps configure applications inside IL4 and IL6 government cloud environments and other government networks. Delivery is senior and US-based. i3solutions has been a Microsoft Partner with 30 years of enterprise technology delivery experience and has delivered 1,500+ Microsoft engagements across aerospace and defense, financial services, and health sciences. An i3solutions engagement does not produce managed-service ownership, a replacement for the internal team, open-ended scope expansion, or vendor lock-in. The wider governance approach is set out in Embedding Governance into How the Enterprise Operates and Scales.

Key Takeaways

The points below restate what Microsoft’s Learn about Endpoint data loss prevention, Data loss prevention and Microsoft Teams and Plan for Microsoft Purview compliance and risk management solutions – GCC High deployments say:

  • Endpoint DLP watches named exits on onboarded devices; an exit with no matching activity is not covered.
  • It cannot see data never saved locally, encrypted files or labels from another tenant, it is not supported on domain controllers or Server Core, and Macs lack several settings.
  • Teams DLP protects channel messages only when the policy is scoped to groups, and a chat another organization starts runs under that organization’s policies.
  • E3 covers files shared through Teams; DLP for Teams chat needs E5.
  • Microsoft’s GCC High table lists both controls as Available, subject to change, without itemizing sub-features, so confirm each one in the tenant.

Frequently Asked Questions

Can endpoint DLP block a file saved straight from Word to a USB drive?

No, not when the file is never saved locally first. According to Microsoft Learn, if data is never saved to a file on the local device, endpoint DLP cannot scan or classify it, so a document saved from Word directly to a USB device without first being stored locally cannot be inspected or blocked. For removable storage, Microsoft Learn points to Microsoft Defender for Endpoint Device Control.

Does Teams DLP work on chats another company started?

Not with your policies. According to Microsoft Learn, DLP enforcement in a cross-tenant conversation is based on the hosting tenant, the tenant that initiated the chat or thread, and a user’s home-tenant DLP policies do not automatically follow the user into a conversation hosted by another tenant.

Do Teams DLP policies cover channel messages?

Only when the policy is scoped to groups. According to Microsoft Learn, a policy scoped to individual user accounts protects one-to-one and group chats but not standard, private or shared channel messages, while a policy scoped to security groups, distribution groups or Microsoft 365 groups protects both.

Does Microsoft 365 E3 include DLP for Teams?

For files, yes; for chat messages, no. According to Microsoft Learn, Office 365 and Microsoft 365 E3 include DLP protection for SharePoint, OneDrive and Exchange, including files shared through Teams, and DLP protection in Teams chat requires an E5 license.

Is endpoint DLP available in GCC High?

According to Microsoft Learn, Microsoft’s GCC High planning table, last updated May 21, 2025, lists endpoint data loss prevention and Teams chat and channel conversations as Available, with status subject to change. The table lists each as a single row, so confirm each sub-feature in the tenant itself.

Does endpoint DLP work on Windows Server?

On some servers, and not by default. According to Microsoft Learn, endpoint DLP supports Windows Server 2019 and later, is not supported on domain controllers or Server Core installations, is not enabled for Windows servers when they are first onboarded, and installing the supported Windows Server KBs disables the Classification feature on the server.

Planning the Decision

If the audit has named USB, print, upload and chat and the licence request is on your desk, map each exit to the activity or location that covers it, write down every blind spot with its answer, and confirm the sub-features in your own tenant before you sign the coverage statement, so what you tell the auditor is what the tenant does.

Contact a senior architect