![]() And several Office 365 instances are happy again.Īfter several weeks of this re-installation – everything still works. And reinstalled it.Īfter reinstallation it was just a few extra units of time to use my phone Authenticator as primary MFA device again. After I had removed all MFA connections (or just made sure they exist and work on other device) I removed the Authenticator installation. Unlike when you loose your phone or have to reinstall it fully – I managed to do this in a controlled way. Reinstall it.Īfter trying “just about everthing” I started to work on the reinstall: making sure I had my other device as backup MFA or taking temporarily MFA off on some environments (non-production). The same solution has been used for decades for many different programs. It was always there, but I didn’t want to take the step. let OnePlus optimize Authenticator’s battery use (it was on by default).restrict battery use for Authenticator (yeah, I did that).I spent some time googling for answers as I didn’t want to start reconfiguring my MFAs during my vacation. In short: even with light use the battery didn’t last the full day it had done before. I didn’t switch my phone to English (yeah, guilty on using Finnish-encrypted phone UI ) before screenshot. Yes, OnePlus is a hot phone – but mine was taking it too literally. And when a battery is being drained rapidly there is the matter of heat. In short: the Authenticator was eating my charge quite rapidly. ![]() ![]() It involved the Microsoft Authenticator app that is used to Multi-factor Authentication confirmations. During the summer I got the issue onto my OnePlus 6T phone. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |