OTP Provision
Entra MFA Toolkit · OTPProvision
Bulk-activate hardware OTP tokens in Microsoft Entra ID.
OTPProvision imports and activates hundreds or thousands of OATH TOTP tokens through Microsoft Graph, SHA-1 and SHA-256 alike. Tokens arrive ready to use, and nobody has to read a code off a device.

- Time to first import
- About 20 minutes
- Server required
- None, static files
- License
- Microsoft Entra ID P1 or P2
- Tokens
- 6-digit TOTP, 30 or 60 sec
- Input formats
- CSV, TSV, PSKC XML, JSON
The problem
Uploading tokens scales. Activating them doesn’t.
Enrolling a hardware OATH token in Entra ID has always been two jobs. The first is a file upload. The second needs someone to hold each device, read its six-digit code and type it in, after the tokens have already been handed out.
Upload the token’s identity
Serial number and secret seed go into the tenant inventory.
Scales with a fileActivate it against a user
Someone reads a code off the device and types it in, one token at a time.
Manual, per tokento activate one token by hand. A thousand tokens is a week of someone’s time.
columns for the hash algorithm in the legacy admin-center CSV, so SHA-256 tokens can’t be uploaded that way.
OTPProvision uploads and activates each token in a single Graph call. The manual step is gone.
How it works
The seed file already knows the code.
A TOTP code is a pure function of three inputs. Your token vendor already shipped you every seed, so OTPProvision computes the same code the device would show and sends it as the activation code. Entra ID validates it exactly as it would a typed one.
Same three inputs
Whether the device or OTPProvision does the math, it uses the same values.
Same six digits
A live demo using an RFC 6238 test seed. Both sides compute the code independently.
New code every 30 seconds.
One call to Graph
The code is computed immediately before the request, then assigned and activated together.
hardwareOathMethods/
assignAndActivate
{ "verificationCode": "––––––" }
Why this isn’t a security bypass: activation was never an authentication control. It’s a binding check that the seed on file matches the device in hand. Whoever runs an import already holds every seed in the file, so automating the check grants no new capability.
Compared
More than a CSV generator.
Other tools stop at building a file for you to upload by hand. OTPProvision talks to Microsoft Graph directly, so it can activate tokens as well as upload them.
| Entra admin center CSV upload | CSV generator tools | OTPProvision | |
|---|---|---|---|
| Upload tokens to tenant inventory | |||
| Activate tokens on users’ behalf | |||
| SHA-256 tokens | |||
| Mixed SHA-1 and SHA-256 in one file | |||
| Dry run against your live tenant | |||
| Safe to re-run after a failure | |||
| Day-two inventory and help-desk checks | Partial |
Built for real rollouts
From vendor file to sign-in, start to finish.
Two lists, paired for you
Paste a user list and a vendor file of serials and seeds, or pull users from an Entra group, including nested groups. Duplicates are rejected.
Activate now or self-service
Activate tokens that ship soon, or upload them unassigned so users claim their own at aka.ms/mysecurityinfo when they receive the device.
Dry run first
Checks consent, permissions, every user and every seed against your live tenant, then reports what a real run would do. It writes nothing.
Safe to re-run
Reads existing inventory first and skips or resumes tokens already imported. Progress is journaled, so a crashed tab costs at most a second of records.
Hex or Base32, detected
Seeds in hex are converted to the Base32 Graph requires. Seeds that are valid in both encodings are flagged for you instead of guessed.
Packing lists and labels
A packing list CSV and printable labels, one card per person with a large serial number, so the right device reaches the right person.
Day-two inventory
Search every token in the tenant by serial, user or model. Unassign to return a token to the pool, or unassign and delete.
Help-desk token check
Get a plain-language verdict on any serial, or see the code a token should be showing right now and compare it with what the user reads out.
Works with any TOTP token
Nothing is tied to one brand. Any 6-digit TOTP token whose seed you hold will import, from CSV, TSV, PSKC XML or JSON.
Security model
Your seeds go to Microsoft and nowhere else.
OTPProvision is a static page that runs in the administrator’s own browser. There is no backend to trust, and no part of it runs on a machine you don’t control.
No server, no third party
Seeds are read into memory, sent to graph.microsoft.com over TLS, then discarded. No telemetry, no analytics, no FEITIAN endpoint.
Nothing written to disk
The crash-safe journal keeps serials, users and outcomes only. A unit test asserts that no seed ever reaches storage.
Delegated sign-in only
It acts as the signed-in administrator and can never exceed what that person may do. No application permissions and no client secret to leak.
Fully auditable
Every write goes through Graph under the administrator’s identity, so Entra’s audit log records it like any other change.
Verified cryptography
Codes are computed with the browser’s native WebCrypto and verified against all twelve RFC 6238 test vectors for SHA-1 and SHA-256.
Readable source
Dependency-free JavaScript with no build step, so the files you host are the files you read. 98 automated tests run without a tenant.
The honest trade-off
Activating from the seed skips the physical check that the device in the box matches the seed on file. Three simple habits cover it.
- Spot-check before importing. Compare the live code for a few seeds against tokens pulled from the box. A mismatch means the file doesn’t match the shipment.
- Keep a fallback method enabled until tokens are confirmed in use.
- Watch last-used dates. A token activated weeks ago and never used deserves a call.
Deployment
First import in about 20 minutes.
Most of that time is the one-time app registration. After that, an import is a file, a dry run and a click.
Confirm prerequisites
Entra ID P1 or P2, the hardware OATH tokens method enabled, and an operator with the right authentication roles.
Register the app
One Azure CLI script, generated by the page with your hosting URL filled in. Single-page app, no client secret, four delegated permissions.
Host the page
localhost, IIS, nginx, internal SharePoint or any static host. Air-gapped networks can keep the sign-in library local too.
Load your token data
Drop one file, or paste a user list and a vendor file to pair them. Download the merged CSV as your record of who got which serial.
Dry run
Every time. It shows per token whether a real run would activate, upload, resume, skip or block, and writes nothing.
Pilot, then import
Start with 5 to 10 tokens on real users, including an actual sign-in. Then run the full batch and keep the results CSV.
Microsoft Entra ID P1 or P2
Privileged Authentication Administrator, or Authentication Policy Admin + Authentication Admin
Global Administrator or Privileged Role Administrator to grant admin consent
Entra ID and Microsoft Graph reachable. No inbound access, no server.
FAQ
Questions administrators ask.
Is it safe to compute our one-time codes?
Yes. A TOTP code is a pure function of the seed, the current time and the algorithm, so anyone holding the seed file can already generate every code in it, with or without this tool. OTPProvision automates a binding check on data you already hold and grants no capability the seed file didn’t already grant.
Does our seed data go to a FEITIAN server?
No. There is no backend. Seeds are read into page memory, sent to Microsoft Graph over TLS and discarded. The only other network call is Microsoft’s own sign-in endpoint.
Is the process different for SHA-256 tokens?
The activation flow is identical; one field changes. The difference is that the legacy admin-center CSV has no column for the hash algorithm, so for SHA-256 tokens Graph is the only route. One file can mix both algorithms.
Does it work with non-FEITIAN tokens?
Yes. Any 6-digit TOTP token whose seed you hold will import. 60-second tokens are supported. 8-digit tokens aren’t, because Entra ID requires 6 digits, and those rows are rejected with an explanation before any call is made.
How long do 1,000 tokens take?
Mostly as long as Entra’s own rate limiting allows. Requests go 20 at a time, and when Entra asks the tool to wait, it waits and retries. Re-running is safe, so plan for picking up where you left off rather than one uninterrupted window.
Should we activate now or use self-service?
Activate now if tokens ship soon. If distribution is weeks or months away, upload them unassigned and let users claim tokens when they receive them, since a token that sits in a drawer for a long time can drift out of Entra’s time window.
Is this supported by Microsoft?
OTPProvision uses Microsoft’s own documented Graph API. Hardware OATH management 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. If the endpoints move to v1.0 unchanged, the migration is a single line.
What should we do with the seed file afterwards?
Treat it like a list of passwords. Either destroy it, accepting that a deleted token must be replaced, or archive it with your other high-value secrets so tokens can be re-imported later. Don’t leave it in a Downloads folder or an email thread.
Get started
Roll out your next OTP shipment in an afternoon.
Tell us about your Entra ID environment and token rollout, and we’ll get you set up with OTPProvision and the deployment guide.
Questions? Email sales@ftsafe.us or call (408) 352-5553.
Also in the Entra MFA Toolkit
Ready for phishing-resistant MFA?
KeyProvision does the same for FIDO2 security keys, pre-enrolling hardware-bound passkeys for users who can’t self-register.
Passkeys for Entra ID →Microsoft and Microsoft Entra ID are trademarks of the Microsoft group of companies.

