Hello everyone,
I have a tip and a work around that might help you if you run e/os 3.x (for example 3.1) and you cannot sign in for the first time to the Microsoft Authenticator App (hereafter MAA) with your school or work account, for example using a QR code.
It worked for me.
MAA works reliably and without errors now.
Disclaimer: I used an automatic translation, so some grammar may be imperfect and some settings or phone options may be named slightly differently on your device. Apologies for that.
Brief situation overview so you can compare with your own setup:
Fairphone 4 running e/os 3.1.1 (security patch 1 August 2025).
Fairphone 6 running e/os 3.1.2 (security patch 1 August 2025).
(Maybe it will be working with other phones too)
We are required by school and work to use the Microsoft Authenticator App (MAA).
We are not allowed to use SMS verification; we must use the following authentication method:
On the computer we enter our school or work email address and password.
The computer shows a pop-up with a 2-digit number.
MAA on the phone shows a prompt where that 2-digit number must be entered.
After entering and approving it, you are signed in to your school or work account.
When trying to register and set up MAA for the first time, for example with a QR code, e/os unfortunately shows an error:
The school or work account cannot be registered in MAA.
The SOLUTION:
On both the FP4 and FP6 (and possibly FP5 and other phones with e/os 3.x) you can take the following steps to work around this problem.
1a. Do you already have the Microsoft Authenticator App on your Fairphone?
Uninstall MAA from your Fairphone to completely and cleanly remove any prior sign-in or registration attempts.
1b. Reinstall MAA, but do not open it yet.
2a. Go to Murena’s Settings.
2b. Type “microG” into the search bar and tap “microG” in the results.
2c. Turn “Google device registration” ON.
This is not great for privacy, but we do it temporarily.
- In Murena Settings go to “APPS”.
4a. Tap “Authenticator” and do the following:
4b. Tap “Permissions” and allow “Notifications” fully.
4c. Set “Camera” to “Ask always”.
4d. Deny “Location” entirely — this is better for your privacy.
4e. Under “Mobile data usage” turn everything ON, except the last option (the “unrestricted…” item).
4f. Under “Battery usage” set the switch to ON (the “Background usage…” option).
4g. Set “Manage app when unused” to OFF.
4h. Set “Appear on top of other apps” (or “Display over other apps”) to ON.
5a. Now start the Microsoft Authenticator App.
5b. Follow your school’s or workplace’s instructions to set up the account in MAA (most likely by scanning a QR code).
NOTE: If Murena/e/os or MAA prompts you about “Notifications”, choose “Always allow”. If Murena asks about the camera, choose “Only this time” / “Allow once” (or similar).
6a. Is the Authenticator App set up correctly?
6b. Test by signing in to your school or work account.
Did it succeed?
6c. Type “microG” into the search bar and tap “microG” in the results.
6d. Turn “Google device registration” OFF.
Your privacy should now be preserved as much as possible, and MAA should work normally each time you sign in to your school or work account.
Okay, last tip;
When the computer gives you the 2-digit number alfter a succeed first sign-in and MAA doesn’t give a prompt. (This happens rarely, I don’t know why). Just start the App by hand and the app will show the pop-up.
Good luck with it, I hope it works for you!
Regain your privacy! Adopt /e/OS the deGoogled mobile OS and online services