Teams for Android never saves a signed-in account to the account list, and two old accounts cannot be removed (Android 16 / OxygenOS 16)

Question

Teams for Android never saves a signed-in account to the account list, and two old accounts cannot be removed (Android 16 / OxygenOS 16)

Mateusz 0

Device: OnePlus 15 (CPH2747), personal device - not company-owned, not Intune-enrolled
OS: OxygenOS 16 (Android 16)
App: Microsoft Teams, latest version from Google Play, only other Microsoft app installed: Microsoft Authenticator
Date/time set to automatic, sufficient free storage

Problem 1 - a successful sign-in is never persisted

When I open Teams I get the account picker. I sign in with a valid work account. The sign-in completes and Teams works normally. If I then tap "Add account" seconds later, without closing or backgrounding the app, the account I just signed into is not in the list. It was never written anywhere. After a while the session ends and I am back to the picker with no trace of that account.

This is not a background-kill problem. The account is missing while the app is still running in the foreground.

Problem 2 - two old accounts cannot be removed

The same picker shows two accounts from a former employer. They survive clearing app data and full uninstall/reinstall. They are not present in Microsoft Authenticator and not present in Android Settings > Users & accounts > Work or school account - both of those contain only my current accounts, the ones Teams refuses to save.

What I have already tried, all without effect

Cleared Teams cache and cleared app data
Uninstalled and reinstalled Teams several times
Uninstalled Intune Company Portal entirely
Verified Microsoft Authenticator holds only the new accounts; removed nothing relevant there
Verified Android Settings > Users & accounts holds only the new accounts
Checked OxygenOS app cloning - Teams is not cloned, no second instance exists
Disabled battery optimisation and allowed unrestricted background activity for Teams
Multiple reboots
Followed the Android System WebView workaround from a related thread on this forum: removed WebView updates, rebooted, reinstalled updates, signed in again. No change.

The same two accounts work perfectly in Teams desktop on Windows. No repeated sign-outs there, both accounts sign in and persist normally. Teams in a mobile browser also works. The problem is isolated to the Teams Android app on this device.

So, the questsions are:

If the account list is not in Teams app data, not in the Android AccountManager, and not in Authenticator, where does Teams for Android actually persist it? I assume the OneAuth shared account store, but on Windows that is an editable folder while on Android there appears to be no supported way to inspect or clear it.
Is there any way to purge or reset that store on Android short of a factory reset?
Is this a known incompatibility between the Microsoft authentication stack and Android 16? Several reports in other threads describe sign-in failures on Android 16 with a similar shape, but those are rather old cases.

0 comments

1 answer

Your answer

Answer 1

Good day,

Thank you for providing such a detailed description of the issue and for outlining all the troubleshooting steps you have already completed.

Based on the information you shared, the behavior you're experiencing does not appear to be related to a typical sign-out, cache, or battery optimization issue. The fact that newly authenticated accounts are not retained even while the Teams app remains open, while older accounts continue to appear after clearing app data and reinstalling the application, suggests that the problem may be related to the underlying Microsoft authentication components used by Teams on Android rather than the Teams app data itself.

Regarding your questions, Microsoft documentation confirms that Teams Mobile can display Microsoft 365 accounts that are currently signed in or were previously used on the device. However, the available documentation does not identify the exact storage location of these account records, nor does it provide a supported method to manually clear any underlying shared authentication store that may exist outside of the Teams app.

For reference: How different technologies affect Microsoft Teams sign-in, including restricting sign-in, and sign-i…

At this time, I was unable to find any official Microsoft documentation confirming a known incompatibility between Microsoft Teams and Android 16 or OxygenOS 16. While similar symptoms have been reported by some users, there is currently no published Microsoft advisory that identifies this as a known product issue. The fact that the same accounts work correctly in Teams Desktop and through a mobile browser indicates that the accounts themselves are functioning properly, and that the issue appears to be isolated to the Teams Android application on this device.

Given the advanced troubleshooting you have already performed, the most appropriate next step would be to collect Teams diagnostic logs and submit them to Microsoft for further investigation. The Teams mobile app allows users to attach diagnostic logs through:

Profile picture > Settings > Help and feedback > Send feedback > Attach logs to help troubleshoot.

For reference: Send diagnostic log files from Microsoft Teams mobile app | Microsoft Support

Alternatively, you can ask your organization's IT administrator to submit a support ticket through the Microsoft 365 Admin Center.

When contacting Microsoft Support, I also recommend including the following details:

Device model (OnePlus 15, CPH2747)
OxygenOS and Android build versions
Teams app version and build number
A screen recording showing a successful sign-in followed by the account not appearing in the account list
Confirmation that the device is personal, not Intune-enrolled, and has no active work profile
Confirmation that clearing app data, reinstalling Teams, and checking Authenticator and Android account settings did not resolve the issue

These details will help the support team determine whether the issue originates from the Teams client, Microsoft's authentication framework, or a device-specific interaction with the operating system.

I hope this helps clarify the situation. Please let me know if you have any additional questions or if you need assistance gathering the diagnostic information.

Kind regards.

If the answer is helpful, please click "Yes". If you have extra questions about this answer, please click "Comment".