Exporting Microsoft Authenticator TOTP secrets

The article explains that Microsoft Authenticator uses a proprietary scheme called phonefactor for Office 365 TOTP 2FA, preventing the use of standard TOTP apps. However, after registration, the app generates codes using regular otpauth, and the secrets can be extracted from a rooted Android device's SQLite database at `/data/data/com.azure.authenticator/databases/PhoneFactor`. The extracted 32-character `oath_secret_key` can then be imported into any standard TOTP application.

Background Workplaces may enforce TOTP 2FA to be enabled Office 365 accounts, which require the Microsoft Authenticator https://www.microsoft.com/en-us/security/mobile-authenticator-app app to be installed. Regular TOTP applications such as Aegis https://getaegis.app/ , Authy https://authy.com/ , or LastPass https://www.lastpass.com/ cannot be used as Microsoft uses a proprietary scheme called phonefactor . Furthermore, the application requires Google Services Framework GSF to be installed likely to provide device notifications , and will refuse to work when it is not present on the device. Forunately, after the registration is complete, the underlying mechanism the app uses to generate TOTP codes is regular otpauth , and its secrets can be exported with a little bit of effort. Extracting the keys 1. To extract the keys, a complete registration must first be done with a rooted Android device. I used a virtual Android device created with Android Studio's Device Manager https://developer.android.com/studio/run/managing-avds . 2. Once complete, an SQLite database storing the keys can be found on the device at: /data/data/com.azure.authenticator/databases/PhoneFactor accessing the /data partition is what requires root 3. ADB https://developer.android.com/studio/command-line/adb can then be used to connect to the device/emulator, using its bundled sqlite3 tool to view the database: $ adb root Ensure we run as the root user $ adb shell Launch a shell as the root user emu64xa:/ whoami root emu64xa:/ sqlite3 /data/data/com.azure.authenticator/databases/PhoneFactor Connect to the database file sqlite SELECT name, username, oath secret key from accounts; GitHub|Chowder@github.com|w0swofa8wl02vqml0pkbzphvp54zyx5x The 32-length string in the oath secret key column can then be imported into any TOTP application.