Success Factors to AD integration question

[RaviRIyer]

We are enabling the SAP Success factors to AD integration using the standard pattern of HR driven provisioning. 

LINK

We have recently merged multiple domains into one and now several users have an existing employee ID which does not  match their employee ID from Success Factors, we want to ensure the employee number from Success factors is Primary but at the same time not create new Entries in AD for existing users when this employee number does not match between Entra and SF. 

As per the documentation - 
if personIdExternal maps to employeeId and is set as the matching attribute, then the provisioning service uses the personIdExternal value to search for the user with employeeId filter.
If a user match is found, then it updates the target attributes.
If no match is found, then it creates a new entry in the target.

I wanted to know if we can have multiple checks before a new ID is created in AD/Entra ie check for personIDExternal and if not found, then check with firstName and lastName and if not found, then create a new entry else update. 

Any recommendations here would be very helpful, thank you.