MicrosoftSeanMcNeill Hi Sean, We are in the process of implementing EDM into production and creating our EDM Upload files to be hashed. The two pieces of data we are including in the upload are social security number and account number. Do I need to upload the social security number in each format it can possibly be triggered on?. For example 111-22-3333, 111223333, or 111 22 3333. Using the built in Microsoft sensitive info type for SSN I can only make it match on the format of the social security number that is in the uploaded hash file which would be 111223333. It will not match on 111-22-3333. It really is EDM based on my testing. I saw an update on the Microsoft Roadmap for EDM supporting data configuration but assume this doesn't change anything?
Microsoft Information Protection: Exact Data Match will support data configuration
Exact Data Match will support data configuration, allowing text case and character delimiters to optionally be ignored, helping reduce the need for manually defining minor variations in the hashed and uploaded data being protected
