KeyProvision
Entra MFA Toolkit · KeyProvision
Hand every user a security key that already works.
KeyProvision pre-registers FIDO2 security keys to users’ Microsoft Entra ID accounts before handover. IT enrolls the key, one at a time or in bulk, and the user just signs in with the key and its PIN.

- Time to first key
- About 20 minutes
- Per key
- About 20 to 30 seconds
- Workstation
- Windows 10 or 11, 64-bit
- Operator role
- Authentication Administrator
- Entra ID P1/P2
- Not required
The problem
Rollouts stall at self-enrollment.
Handing out a key is easy. Getting each user to sign in with an existing method, follow six screens, set a PIN and touch the key is where rollouts stall. New hires have no working sign-in on day one. Frontline and shared-desk staff often have no time or no machine. Every key left in a drawer is a user still on a password.
Hand over a key
The key does nothing yet.
EasyThe user enrolls it themselves
Needs a working sign-in, time and confidence. IT can’t do it for them from a browser, because WebAuthn enrolls whoever is signed in.
Where rollouts stallfor the user. The key and its PIN already work when they receive it, and they don’t need to be present.
per key once it’s plugged in, most of it the touch. Bulk mode removes the rest.
from download to first key, most of it the one-time app registration.
How it works
Microsoft handles the account. KeyProvision talks to the key.
Microsoft Graph already lets an administrator request a registration challenge for any user and submit the finished credential back. What it doesn’t provide is the part in the middle: talking to the key. KeyProvision does that directly over USB using CTAP2, the protocol between a computer and a security key.
1. Challenge from Entra
KeyProvision asks Microsoft Graph for a registration challenge for the selected user, as the signed-in administrator.
2. Credential on the key
It sets a random six-digit PIN on a blank key, then the key creates the credential when the administrator touches it.
3. Registered to the user
The credential goes back to Graph and the key appears on the user’s account as SN: serial date, so every method traces to a physical key.
Why this isn’t a security bypass: pre-registration is a Microsoft-supported operation that requires Authentication Administrator or higher. Anyone with that role can already issue a Temporary Access Pass and enroll a key as the user. KeyProvision doesn’t widen what they can do; it makes the legitimate path fast, and records it.

Bulk Register for cohorts
Paste UPNs or emails, or load a security group, then start the batch. Each key plugged in is matched to the next user: touch, unplug, plug in the next.
One failed key never stops the batch. At the end, print the handoff sheet or export CSV: user, PIN and key serial.
Compared
Covers the users self-service misses.
For users who can enroll at aka.ms/mysecurityinfo, they should. KeyProvision covers everyone else and lets IT hand over a key that is guaranteed to work.
| User self-enrollment | KeyProvision | |
|---|---|---|
| Works for new hires with no sign-in method yet | ||
| User doesn’t need to be present | ||
| Enroll a whole cohort in one sitting | ||
| IT confirms the key works before handover | ||
| Every key traceable to a serial number in Entra | ||
| Offboarding and key reissue in the same tool |
Features
The full key lifecycle, in one app.
Bulk Register
Paste a roster or load a security group, then enroll key after key without reselecting users or retyping anything.
Single-user enrollment
Search the directory, select a user, connect a key. Ideal for new hires and help-desk replacements.
Pre-flight checks
Confirms FIDO2 is enabled, your role is recognized and the key model is on your tenant’s allow-list before anything is registered.
Safe PIN handling
Blank keys get a random six-digit PIN, shown once. Keys that already have a PIN keep it. PINs are never written to disk or sent to Microsoft.
Offboarding
Scan departing users or a group, review every FIDO2 key found, type REVOKE, and they stop working for your tenant immediately.
Key Manager
For help-desk calls on any FIDO2 key: PIN attempts left, change PIN, fingerprints, stored accounts and factory reset for reissue.
Handoff sheet and CSV
One sheet per batch pairing each user with their PIN and key serial. KeyProvision keeps no copy.
Audit log
An append-only record of every key issued and revoked, with operator, user, serial and result. Filter and export to CSV. Never contains PINs.
Automatic updates
New versions download in the background and install when the app closes. It never restarts mid-task.
Security model
Your data goes to Microsoft and nowhere else.
KeyProvision is a Windows desktop app that talks to Microsoft directly from the administrator’s PC. There is no backend, no telemetry and no FEITIAN endpoint that receives customer data.
Delegated sign-in only
Administrators sign in as themselves, with Conditional Access and MFA applied. No application permissions and no client secret to leak.
Nothing sensitive stored
On disk: tenant and client IDs, the license file and the audit log. Never PINs, passwords, access tokens or private keys.
Hardened app
A sandboxed interface with no access to the operating system. The access token can only be sent to graph.microsoft.com, and the local interface is reachable only from the PC itself.
Tamper-resistant
The app checks its own code at start-up and refuses to run if it was modified. It can’t be run as a debugger, and developer tools are disabled.
Audited twice
Entra’s audit log records every registration and removal under the administrator’s identity, and KeyProvision keeps its own log.
Tenant-locked license
Signed by FEITIAN and bound to your tenant ID, checked against the tenant Microsoft actually signs you in to. One license covers every administrator.
The honest trade-off
Enrolling a key for someone means the administrator knows its PIN. Three simple habits cover it.
- Treat handoff sheets as secrets. Shred printed sheets and delete CSVs once keys are distributed.
- Have users change their PIN on first use in Windows Settings → Accounts → Sign-in options → Security key.
- Watch Entra’s audit log for registrations you didn’t expect.
Deployment
First key in about 20 minutes.
Most of that is the one-time app registration. After that, a rollout is a roster, a stack of keys and a handoff sheet.
Confirm prerequisites
Passkey (FIDO2) enabled under Authentication methods, key restrictions reviewed, and an operator with Authentication Administrator or higher.
Register the app
One Azure CLI script or a few portal steps: single-page app, no client secret, seven delegated permissions, admin consent.
Install
Per-user installer for Windows 10 and 11. No administrator rights needed, and it can be pushed with your software-deployment tool.
Connect and license
Enter your tenant and client IDs, sign in, and load the license file FEITIAN issues for your tenant.
Pilot a key
Provision a test user’s key, confirm it in Entra, then sign in with it on another machine. If that works, you’re ready.
Roll out
Run Bulk Register by cohort, distribute keys individually, then destroy the handoff sheet.
Windows 10 or 11, 64-bit, with a USB port
Authentication Administrator, or Privileged Authentication Administrator for admins’ keys
Any FIDO2-certified USB key, CTAP 2.0 or 2.1
A KeyProvision license per tenant. No Entra ID P1/P2 needed.
FAQ
Questions administrators ask.
Is it safe to enroll keys for other people?
Yes. Pre-registration is a Microsoft-documented Graph operation that requires a role Microsoft already trusts with every user’s authentication methods. Anyone with that role can already issue a Temporary Access Pass and enroll a key as the user. KeyProvision does the legitimate version of that, faster and with a record.
Does any of our data go to a FEITIAN server?
No. There is no backend. KeyProvision talks to Microsoft directly from the administrator’s PC. Its only other network calls download a signed license-revocation list and software updates, and neither sends anything about your tenant.
Which keys work?
Any FIDO2-certified USB key supporting CTAP 2.0 or 2.1, including FEITIAN keys and other vendors’. Fingerprint management needs a biometric key. Microsoft Authenticator passkeys and Windows Hello aren’t covered, since those are created on the user’s own device.
What if the key already has a PIN?
KeyProvision asks for it and uses it only to authorize the registration. The key keeps its PIN, and any other accounts on it are untouched.
Does the user need to be present?
No, that’s the point. The user needs the key, the PIN and nothing else.
Can a key be reissued to someone else?
Yes. Offboard the previous user, factory-reset the key in Key Manager, then provision it for the new user.
What license do we need?
A KeyProvision license for your Entra tenant. It covers every administrator on any number of PCs, and can’t be used in another tenant. Microsoft Entra ID P1 or P2 isn’t required to provision keys.
Is this supported by Microsoft?
KeyProvision uses Microsoft’s own documented Graph API. FIDO2 provisioning is currently in preview under the Graph beta endpoint, which is Microsoft’s status for the API and applies to any tool using it, including PowerShell.
Is there a macOS version?
Not at present. KeyProvision runs on Windows 10 and 11.
See it in action
Book a 30-minute KeyProvision demo.
A live walkthrough from first key to bulk rollout, the features that matter most for your deployment, and a straightforward breakdown of pricing.
Questions? Email sales@ftsafe.us or call (408) 352-5553.
Also in the Entra MFA Toolkit
Evaluating hardware-bound passkeys?
Request two free sample keys for your Entra ID tenant. Still issuing OTP tokens? OTPProvision bulk-activates them in Entra ID.
Passkeys for Entra ID →OTPProvision →
Microsoft, Microsoft Entra ID and Windows are trademarks of the Microsoft group of companies.

