Authenticator version 6.2405.3618 & 6.2406.3956 causing "Update Required" error on Business Office 365 accounts

Tinmor Chen 11 Reputation points

Hi, ever since I updated my Authenticator to version 6.2405.3618, my entire Office apps on my phone all asking to sign-in my Office 365 accounts again, when I tap on the "sign-in" banner, it will then ended up with error "Update Required", and today there is newer version 6.2406.3956, but it didn't change anything, I'm still getting the same error on all Office apps.  The only way I can work with the apps with my Office 365 accounts is by uninstalling Authenticator or installing back older version 6.2404.2872.  After some troubleshooting, I find that it only affects my work Office 365 accounts (2 different organizations both with E1 & Business Premium licenses), my free personal Microsoft accounts doesn't have this problem.  Any ideas?  My phone is RedMagic 8s Pro with Android 14.


Microsoft Authenticator
Microsoft Authenticator
A Microsoft app for iOS and Android devices that enables authentication with two-factor verification, phone sign-in, and code generation.
6,115 questions
0 comments No comments
{count} vote

1 answer

Sort by: Most helpful
  1. Tinmor Chen 11 Reputation points

    Nevermind, I figured out the issue myself.  It turns out that after version 6.2404.2872, the Company Portal no longer works with authenticator version 6.2405.3618 or later, which includes stand-alone office apps like Word, Excel, PowerPoint.  Instead, you will need to download "Intune" to replace "Company Portal" and download "Microsoft 365 (Office)" to replace Word, Excel, PowerPoint.  Once I replaced the apps, everything is working again with my work Office 365 accounts.  I really wish Microsoft would give a warning message after the new Authenticator update, that explains the changes, and instead of giving an "Update Required" error but at least pointing out which app that is causing the issue.  This is basically wasting me 5 days of trying to figure out what's going on and no one from Microsoft actually giving any answers to this issue. 😑

    0 comments No comments