A unified data governance solution that helps manage, protect, and discover data across your organization
Create a separate Exchange-only DLP policy, then add a NOT group with Recipient is for each ticketing-system address; the recipient options are absent from the current editor because its available conditions are constrained by the policy locations you selected.
Configure the exception
- In the Microsoft Purview portal, open Data Loss Prevention → Policies.
- Create a custom policy for Exchange email only, or duplicate the existing policy and change its locations so that only Exchange email is selected.
- Keep the existing policy for SharePoint, OneDrive, Teams, or other locations.
- When multiple locations are selected, the rule editor exposes only conditions shared by those locations. Microsoft recommends considering workload-specific policies when different conditions are required.^1^ Location selection also determines which conditions and actions are available.^2^
- Edit the Exchange policy’s rule.
- Under Conditions, keep the conditions that detect your Internal sensitivity label and external recipients.
- Select Add group, and switch that group to NOT.
- Inside the
NOTgroup, select Add condition → Recipient is. - Select the mailbox, mail user, or mail contact representing each ticketing-system address.
- Save the rule and initially run the policy in simulation mode. Test:
- Internal-labeled email to an ordinary external address → blocked.
- Internal-labeled email to the ticketing address → allowed by the exception.
- Email containing both an excepted and a non-excepted external recipient → verify each recipient’s outcome.
For Exchange DLP, Recipient is has the exception predicate ExceptIfSentTo and evaluates recipients in the To, Cc, and Bcc fields. It accepts a mailbox, mail user, or mail contact represented in the organization.^3^
If the ticketing address is not selectable
Create or use an Exchange mail contact for the external ticketing address, then return to the DLP rule and select that contact under Recipient is. This is preferable to loose text matching because it identifies the specific recipient object.
If creating a contact is not appropriate, Exchange DLP also provides:
- Recipient address contains words
- Recipient address matches patterns
- Recipient domain is
Use a domain exception only if every recipient in that domain should bypass the rule. The address text and pattern predicates inspect the recipient’s primary email address, not proxy addresses.^3^
For several ticketing recipients, a supported alternative is a distribution group, mail-enabled security group, or Microsoft 365 group and the Sent to member of exception. DLP supports those mail-enabled group types for recipient-based conditions.^3^
Important behavior with multiple recipients
Recipient-based conditions can cause message bifurcation: Exchange may allow delivery to an excepted ticketing recipient while blocking delivery to another external recipient on the same message. Test mixed-recipient messages before enabling enforcement.^3^
This exception applies to Exchange email recipients. It does not whitelist the same address for SharePoint or OneDrive sharing; those workloads must remain in a separate policy and use the exclusions available for their locations.
References