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.
Important
Biometric authentication and fraud detection capabilities can be enabled independently or in combination depending on your use case. The use of one doesn't require the use of the other.
- For biometric authentication, 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.
- For fraud detection, you're responsible for configuring and using this fraud detection functionality in compliance with applicable law. You're solely responsible for any fraud-risk determinations, fraudster designations, and your fraud watchlists used in connection with this functionality. Microsoft doesn't recommend, suggest, or make any such determinations or designations. You may not use the output of the fraud detection functionality, including any match or no-match results, to evaluate, determine, or inform an individual's eligibility for credit, employment, insurance, housing, or any other purpose governed by the Fair Credit Reporting Act (FCRA) or similar laws. The fraud detection functionality is intended solely for fraud prevention and authentication purposes. Microsoft doesn't provide this functionality as a consumer reporting agency, and the functionality doesn't generate or provide consumer reports. You will defend and indemnify Microsoft against any claims made by a third party related to this fraud detection functionality. By checking I agree, you attest that your organization will comply with these obligations.
This article explains what biometric authentication and fraud detection is, why organizations use it, how it verifies identity, detects fraud, and the ways it fits into a voice interaction. It's intended for administrators and decision-makers who are evaluating biometric authentication and fraud detection for Dynamics 365 Contact Center.
Learn about the capabilities, intended uses, limitations, and responsible use of biometric authentication and fraud detection in the Application card for biometric authentication and fraud detection.
Why use biometric authentication
Biometric authentication is a voice-security service that verifies your customer's identity from their voice during a natural conversation. Alongside knowledge-based questions, PINs, passwords, or one-time passcodes, biometric authentication combines voice biometrics, synthetic-speech detection, and playback detection to confirm that callers are who they claim to be. Because verification happens passively as your customer speaks, biometric authentication reduces friction for your customer and shortens the identity checks that customer service representatives perform on every call. All voiceprints and associated metadata are stored within your Dataverse environment.
Biometric authentication and fraud detection adds a voice-based identity factor to the contact center so that authentication can happen without extra steps for the customer. Organizations typically adopt it for the following reasons:
- Streamlined authentication in the voice channel. Identity verification runs automatically as the customer speaks, so callers don't have to answer a series of security questions.
- Reduced call handle time. Authentication occurs passively in the background of a normal conversation. Authentication decisions are rendered during call introductions and intent capture.
- Higher authentication success rates. Because verification doesn't depend on PINs, passwords, one-time passcodes, or access to a trusted phone or email, more customers can be authenticated successfully.
- A better representative experience. Representatives spend less time asking knowledge-based questions and can focus on resolving the customer's issue.
- An additional factor for a multifactor strategy. A voiceprint can serve as one factor alongside other verification methods.
- Real-time protection against spoofing. Biometric authentication and fraud detection detects non-natural speech patterns, synthetic (AI-generated) speech, and recorded playback to help block impersonation attempts as they happen.
Why use fraud detection?
Fraud detection is a voice-security service that compares caller audio to your fraud watchlist, alerting fraud analysts and/or contact center representatives that a potential match has been detected. All fraudster voiceprints are created from a dedicated Dynamics 365 Contact Center biometric authentication and fraud detection user interface by authorized users from your organization. All data resides within your Dataverse tenant.
- Real-time protection against fraudster attacks. Fraud detection matches live speaker audio against fraudster voices on your watchlist. It alerts both representatives and fraud analysts in real time when it detects a potential match.
- Simplified fraud detection performance management. The service includes a dedicated fraud analyst UI to work fraud alerts, provide human feedback, and create and manage fraudster voiceprints.
How Biometric authentication works
Biometric authentication verifies identity by comparing a caller's live speech to a stored voiceprint — a secure mathematical representation of the customer's voice, stored within your Dataverse environment. The service follows a three-step model: consent, enrollment, and authentication.
Consent
Before a customer's voice can be used for authentication, the customer grants permission for biometric authentication to create and store a voiceprint within your Dataverse environment. Consent is captured explicitly, and enrollment proceeds only after the customer agrees. You must obtain legally sufficient consent from the customer for voiceprint enrolment.
Enrollment
After consent is granted, biometric authentication collects your customer's speech to build a voiceprint. The service converts that speech into a secure mathematical representation and associates it with a customer identifier and stores it within your Dataverse environment. The voiceprint — not the raw audio — is what biometric authentication uses for later comparisons.
Authentication
On future calls, biometric authentication compares the caller's live speech against the stored voiceprint stored within your Dataverse environment. During this comparison, the service evaluates two kinds of signals:
- Speaker similarity — how closely the live voice matches the enrolled voiceprint.
- Anti-spoofing signals — whether the audio shows evidence of synthetic speech, recorded playback, or other non-natural patterns.
Biometric authentication combines these signals into an authentication decision.
Authentication decisions and outcomes
After biometric authentication and fraud detection evaluates a call, it produces a decision in real time. In a live conversation, the service shows a pass/fail indicator to the representative. In an automated conversation, it returns a response to the voice agent. Based on the decision, the interaction can:
- Grant access when the caller is confidently authenticated.
- Trigger step-up authentication when additional authentication is needed.
- Route the call for manual review when there is an authentication failure or fraudster match.
Interaction types
Biometric authentication applies across two interaction types, which differ in how the customer's speech is collected:
- Human-to-Bot (H2B) — Authentication happens while the customer interacts with a voice agent. As the voice agent collects the customer's speech, biometric authentication uses the same audio to enroll or authenticate. If the customer doesn't provide enough speech, the voice agent can ask more questions to gather it, and biometric authentication returns the result to the agent.
- Human-to-Human (H2H) — Authentication happens passively during a natural conversation between the customer and a customer service representative (CSR).
The same underlying voiceprint, speaker-similarity, and anti-spoofing concepts apply to both interaction types. Only the experience that gathers the speech differs, not the biometric evaluation itself.