This looks similar to when we run imports from an external app (Workday) that matches on first name and last name and has conflicts because multiple accounts exist with the same first name and last name. To resolve this we press the gray arrow which is found on the right side of your image you provided. This brings up options where we can search and select an account which then resolves the conflict.

Just to add a bit into this. You can add some automation (and complexity) leveraging inline hooks.

https://developer.okta.com/docs/reference/import-hook/

Essentially, on an import it can send a payload to a destination. That destination could be designed to determine if a conflict is going to occur and send back a modification to the import. The import will then do the evaluation shown in your screenshot with the new values.

This is useful in scenarios where you have lets say an email structure of "first letter of first name.lastname@domain". Having a john doe & then jane doe joins the company and is brought in on an import. If in your environment you have some sort of "handling" process for when this occurs it can likely be automated with an inline hook.

The hook would evaluate if j.doe@domain already exists. Then automate your remediation process and send back the updated new email. (j.doe1, or fullFirstName.Lastname, etc..)