Azure Multi-Factor Authentication VS Authenticator.cc

This is the answer, more detail: https://docs.microsoft.com/en-us/azure/active-directory/authentication/concept-mfa-howitworks. Source: about 2 years ago

Make sure that you back-up the active app-configuration, this way you have an easier way to recover; make sure you are allowed to verify using more than an authenticator, more here. Source: almost 3 years ago

I would say that the "generic desktop app" approach is to be avoided. The reason is that there is a strictly better alternative that targets almost the same audience. By implementing a TOTP generator as a desktop browser extension instead, one gets visibility into which site the user visits, and can show only the relevant code, or, if there is none, a phishing warning. The users that are left behind in the browser... - Source: Hacker News / about 1 month ago

I use a browser extension from https://authenticator.cc/ While I do not know whether its UX is similar, it does have a sync feature (but not cross-browser), an export feature, can backup its data to Google Drive, can store everything encrypted (but not by default), is recommended by at least one government website (SSS Employer Portal in the Philippines), and is there for a long time. Oh, and it also remembers... - Source: Hacker News / 3 months ago

> If you are unable to use the Authy mobile apps, we recommend you look in to alternative desktop products such as the following suggestions: > https://authenticator.cc/. - Source: Hacker News / 3 months ago

Currently, I'm using the Authenticator.cc browser extension on the same device for TOTP. However, I imagine security will eventually tighten and running authentication app/protocols on the same device that is logging in wont be an option. Source: 6 months ago

The recommended extension is Authenticator, and it is compatible with Chrome, Firefox and Edge. Source: about 1 year ago