Bobby_ono
Looking at the policies with
Get-DLPCompliancePolicy 'policy_name' | FL
shows that the policy is in fact working and I now understand how the Exchange scoping works. The ExchangeLocation attribute is set to All regardless of which radio button is selected during the creation wizard. There are two other attributes that represent the Specific Groups radio button:
- ExchangeSenderMemberOf
- ExchangeSenderMemberOfException
These are blank/$null when 'All Groups' is selected.
There are a few other attributes that reveal how many times the policy has been 'matched':
- MatchedItemsCount
- TopNLocationStatistics
- WorkloadStatistics
These attributes show the policy is matching my test emails. Policy currently in test mode, so the content is delivered to the recipient. I know which part of the policy isn't working now, which is the notification email to the sender - in my case is an external sender.
The documentation on DLP policy notifications covers this scenario - https://learn.microsoft.com/en-us/purview/use-notifications-and-policy-tips#options-for-configuring-email-notifications
External senders receive only a templatized notification without full details to prevent any unintended loss of information about the policy configuration.
Hope this might help you Bobby.
edit: Worked out the notification issue on my end - the notification email was ending up in gmail spam folder.