Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
[This article is prerelease documentation and is subject to change.]
Important
You're responsible for configuring and using this Biometric authentication and enrollment functionality in compliance with applicable law, including but not limited to biometric and privacy laws (for example, BIPA and the GDPR), including: (i) providing notice to data subjects, including with respect to retention periods and destruction; (ii) obtaining legally sufficient consent from data subjects; and (iii) processing and deleting the biometric data and biometric identifiers. Biometric data and biometric identifiers will have the meanings set forth in applicable biometric and privacy laws and include equivalent terms set forth in any applicable law. You will defend and indemnify Microsoft against any claims made by a third party related to this biometric functionality, including but not limited to the adequacy of consent.
This article explains how identification and authentication play distinct roles in a voice interaction and how to select a customer identifier that biometric authentication can rely on for consent, voiceprint creation, and authentication. It's intended for administrators and architects who are planning a biometric authentication implementation and need to make these design decisions before deployment.
Important
- This is a preview feature.
- Preview features aren’t meant for production use and might have restricted functionality. These features are subject to supplemental terms of use, and are available before an official release so that customers can get early access and provide feedback.
Identification compared to authentication
In a voice interaction, identification determines who the customer claims to be. It typically collects information such as an account number or customer ID and matches it to an existing customer record. Authentication is a separate step that verifies the caller is the legitimate owner of that identity. After you identify the caller, authentication challenges validate the caller's identity claim.
- Identification answers: Which customer record do you need to access?
- Authentication answers: Can you trust that this person is really the customer?
Choose a customer identifier for biometric authentication
Recording consent, creating a voiceprint, and authenticating a caller all rely on a robust customer identifier. Biometric authentication binds an existing customer identifier to each of these activities:
- Consent: The identifier records whether the customer consented to or declined biometric authentication, for both current and future interactions.
- Voiceprint creation: The identifier associates the customer with a specific voiceprint that is saved within your Dataverse environment.
- Authentication: The identifier tells the service which voiceprint to retrieve and use.
A good customer identifier has the following characteristics:
- Unique to each end user.
- Non-transferable between users.
- Persistent over time.
Avoid using a telephone number, caller ID, or automatic number identification (ANI) as the customer identifier when an organization has many end users. Multiple end users can share the same number, and telephone numbers can be reassigned to different users over time.
The platform doesn't create end-user identifiers, but it provides tools and integration patterns that automatically render the identifier to the biometric authentication service in real time.