/verify should also take persistedFaceIds
Currently /verify only takes faceIds, it could also take persistedFaceIds from personobjects which would improve ease of use
Face is now able to compare a person_id from a Person object through their verify_face_to_person() function. The persisted_face_ids are the ids belonging to a single Person, so if you used a person_id in your comparison, it would check all of its persisted faces.
Second to @Krishna, this limitation is preventing our further exploration/use of the service.
Making persistedFaceIds usable for /findsimilars also seems logical, but at this point is not working.
This will be deciding feature of whether we would want to implement our requirement through Microsoft Cognitive Services.
Though Important, I can wait for some time if there is a plan for implementing it in near future.
Once done, We are talking at the least thousand transactions on any day.