Yes, you can use them!
All OATH-compliant tokens come with a seed file containing each token's secret key. For the Mi-Token hardware tokens, we need to reformat that seed file into a CSV format defined by Azure AD, then securely send you the CSV file. You will need to modify the CSV file to add usernames to each token and then upload it to Azure.
The following article from Microsoft describes the CSV file structure:
https://docs.microsoft.com/en-us/azure/active-directory/authentication/concept-authentication-oath-tokens
The file we provide you contains the seed data in Hexadecimal format. Azure AD requires the seed info to be expressed in base32 format. Convert the seed strings into base32 before using them.
You can convert the Hex Strings to Base32 on this site: https://tomeko.net/online_tools/hex_to_base32.php?lang=en
For example: Hex seed info: 1669EBDCC7108C272FD876ED6E7F562583BE16A9
Base32 String: CZU6XXGHCCGCOL6YO3WW472WEWB34FVJ
The following is a sample screenshot of the string conversion:
Notes:
- There are no licensing implications in using Mi-Token hard tokens with Azure AD.
- Basically we just reformat the seed file for the tokens into a format that Azure AD likes and then they import it. Assignments are manually made but that's on Azure, not us.