Currently, if you set up a Form Matching strategy record you can only specify specific email address fields. For example, a Form Matching Strategy that has Emailaddress1 field will only check the Emailaddress1 field for a duplicate and not any of the other email address fields.By default, D365 comes with 3 email address fields, which are emailaddress1, emailaddess2, emailaddress3.We use all 3 of the email address fields to store the contact's different email types (Personal, Business, Student).Therefore we are limited with the Form Matching strategy to just one of the three fields and it is therefore highly probable that we will get duplicates created if a user were to enter their email address for emailaddress2 or emailaddress3.If I create a Form Matching Strategy record that has all three of these email fields then they become mandatory on the form which makes no sense and would be confusing for the user to have 3 email fields to fill out.Because of this limitation basically, the use of D365 forms is not possible and we have to use external forms submitted through a HTTP post. We can then use a Flow to better handle the duplicate checking and details of the Form.This is a significant issue as we are implementing a D365 compliance profile Preference Center for users to provide consent to any of their Contact Points (3 x email addresses) and we are unable to match them successfully with a D365 Form. I would like to suggest the idea of being able to have a single email address input field on a form and then list the different email address fields in the Form Matching Strategy records to check for duplicates. If found update the contact record with all the other details but not the email address. If not found, create a new contact record.