Skip to main content- Identity verificationIdentity Verification proves who is on the phone before a technician acts on a request; this page explains the two methods, who can use them and how the management screen is laid out.
- Setting up identity verificationHow to connect Identity Verification to your Microsoft Entra tenant with the setup wizard, run preflight, and get each client's Microsoft administrator to consent.
- Clients and per-client policyHow to onboard a client for Identity Verification, preview its users, and set its method, assurance level, Face Check and consent, one client at a time or many at once.
- Issuance campaignsHow to send a client's users their credential instructions, announcements, reminders and expiry warnings, and issue their credentials in bulk, for clients that use Microsoft Entra Verified ID.
- Verifying a callerHow a technician proves who is on the phone during a call: the verification panel on the call and ticket screens, the browser extension card, what each result means and what to do next.
- Issuing credentials and supervised overridesHow a technician issues a Microsoft Entra Verified ID credential during a call and how to record a supervised override when nothing can verify the caller.
- Credentials and the verification logHow an administrator finds, reviews and revokes issued credentials, reads and filters the verification log, checks that the log has not been changed and exports it.
- Sandbox, configuration and HaloPSA integrationHow an administrator rehearses verifications in the Sandbox, reviews the Configuration tab, and controls what Identity Verification writes to HaloPSA tickets and starts from HaloPSA webhooks.