Skip to main content
This page is for the Entra ID administrator connecting TruU IDV to your tenant. When you finish, TruU can look up employees, their groups and their profile photos, with read-only permissions you can revoke at any time. TruU IDV reads from your tenant. It never writes to it, never holds administrator credentials, and never sees passwords.

Before you start

  • An Entra ID administrator who can create an app registration and grant admin consent to Microsoft Graph application permissions (Global Administrator or Privileged Role Administrator).
  • For the one-click script: access to Azure Cloud Shell, or a terminal with the Azure CLI signed in to the tenant.
  • An Owner or Admin seat in TruU IDV.

Permissions TruU requests

All three need admin consent. TruU requests no write permission of any kind. If you also use Entra ID for enterprise SSO into the console, that is configured separately.

Set it up

Open Settings → Directory and choose Microsoft Entra ID. Pick a setup method.
1

Copy the command

The console shows a one-line command for Azure Cloud Shell. It fetches the current setup script for your workspace, so you always run the latest version. Generate new command issues a fresh one and invalidates the previous command.
2

Run it in Azure Cloud Shell

Open Azure Cloud Shell signed in to the right tenant and paste the command. It creates the app registration, adds the three permissions, grants admin consent, and hands the credentials back to TruU. Your account must be able to grant consent; if it can’t, the script stops and the console shows “Your account can’t finish this setup.”
3

Wait for the connection

The console continues on its own when the script finishes. Entra can take a minute to propagate a new app registration; if a permission check fails right away, choose Retry.

Review the attribute mapping

After connecting, the wizard scans your directory and proposes which attribute each factor uses: Phone (SMS), Email, Knowledge, Badge, Proofing matching and the Face reference photo. Swap in a different attribute where coverage is better, then finish. See Attribute mapping and coverage.

Test it

TruU checks the connection when you connect, daily, and on demand from Credential health: it requests a token with the app’s credentials and lists one user, which proves the secret is valid and User.Read.All is granted. Verified domains (Organization.Read.All) are read during sync and used for just-in-time provisioning. Then send yourself a verification and confirm your own record is found.

How it works

  • Live lookups. Group membership is read for the person at verification time. The group list shown in use case rules is cached briefly and refreshed on sync.
  • Hosts. TruU calls only login.microsoftonline.com and graph.microsoft.com for this connection. Nothing needs to be opened on your side.
  • Secrets. The client secret is held in a managed secrets service and never returned. Rotating it deletes the old value. Every connection change is recorded in the audit trail.

Troubleshooting