Testing random 9 digit that looks like an SSN there are no blocks, no alerts email goes through

This test used a fake SSN with a legit prefix pulled from a test pdf. Unsecure email.
Proofpoint blocked this email and required a secure send. Microsoft did not block the message

This is a sample data test to check for any other blocks, pulled from a testing site.
Microsoft did see this test and reported that it has sensitive data. ^^^

Proofpoint also reported this data but allowed a send encrypted.

The message was received externally.
Conclusion on this particular rule base:

 Proofpoint was able to discern between false numbers and real ones both in a single
unencrypted message and with a PDF
 Microsoft did not see the SSN sent in the second message, Proofpoint did. Proofpoint
allowed secure send in both cases.
 Both Proofpoint and Microsoft saw the attached document. It seems Microsoft is simply
alerting, while Proofpoint is allowing a secure send.
 From what I am seeing in this test, and without access to Microsoft and its rules,
Proofpoint has finer tuned items
 This is OUT OF BOX testing both Proofpoint and Microsoft are configured outside of my
time here.
 While this DOES show that there is some DLP rules in place, it isn’t a full test of all
implementations.
 This is a test of NON ENCRYPTED emails sent with DLP data. A SECURE email test
does not apply here

Testing has ensued for SECURE emails being sent to the wrong recipient, and warning the
user to check the recipients. THIS IS SEPARATE from UNENCRYPED testing. Proofpoint
has a smart send feature that can queue an email and require the user to verify in this case,
this is what we are testing.