Why is Microsoft Authenticator saying my Samsung phone is rooted after the June update?

The timing makes the phone update worth investigating, but it doesn't establish the cause. Similar reports involve multiple Samsung models, including the S23, S24 Ultra and S25. Check the exact software build and Authenticator version on affected phones, then pass those details and the error to your work IT team.

They can compare affected and unaffected devices and check whether the work account's device requirements are involved. An up-to-date app doesn't rule out a compatibility issue.

Developer settings have been suggested as a possible trigger, but that's a guess, not a confirmed fix. If they're enabled, you could try turning them off and checking again. The error alone doesn't prove the phone has been rooted.

Be careful about clearing Authenticator's storage as a test. The app may appear to work immediately afterward but show the error again once an account is added. Make sure you have a way to recover your accounts and check with IT before removing work credentials.

Other authentication apps may still work, so testing one can help describe the problem, but it won't necessarily explain why Microsoft Authenticator rejects the device. A different authenticator might also not satisfy your organization's work account requirements, so check with IT before switching.