Accessing and using Microsoft Teams on smartphones and tablets across platforms
Reset the Microsoft 365 account credentials on the phone, because the matching 5SR96 reports affect Outlook and Teams mobile and the displayed message shows that the mobile sign-in credential was rejected.^1^
Reset the mobile sign-in state
- In Outlook mobile, open Settings → select the affected email account → Reset Account. Then force-close and reopen Outlook.^2^
- If Outlook still returns
5SR96, remove the affected work or school account from Outlook, Teams, and Microsoft 365 Copilot. - Force-close all three apps.
- If the phone has Microsoft Authenticator or Intune Company Portal, open it and verify that the same work account is present and usable.
- Reopen Outlook first and add the correct work or school account. Complete any MFA or device-registration prompt.
- After Outlook signs in, open Teams and Copilot and select the same account.
Starting with Outlook matters operationally because Microsoft mobile apps can share and reuse authentication tokens through shared app storage or a broker such as Authenticator. Outlook can also discover an account already registered by another Microsoft app or Company Portal.^3^
If the error remains, clear the local app state:
- Android: Use the phone’s Settings → Apps → [app] → Storage → Clear cache. If clearing cache is insufficient, remove and reinstall the affected apps.
- iPhone/iPad: Remove and reinstall the affected apps to clear their local state.
Reinstalling removes locally stored app data, so confirm that any unsynchronized local content is no longer needed.
If this is an organizational account
Because the same account works on the PC but fails across three apps on one phone, the administrator should inspect the failed mobile sign-in rather than reset the working PC profile.
An administrator with at least Reports Reader access should:
- Open Microsoft Entra admin center → Entra ID → Monitoring & health → Sign-in logs.
- Filter using:
- Correlation ID:
[GUID] - Date/time:
2026-11-19 01:04:28 UTC - The affected username
- Status: Failure
- Correlation ID:
- Open the matching event and review Failure reason, Sign-in error code, Authentication Details, Device Info, and Conditional Access.^4^
- If Conditional Access was evaluated, check whether the phone was rejected for compliance, registration, approved-app, or app-protection requirements. The event’s Conditional Access and Troubleshooting and support tabs identify the policy and reason.^5^
- If the log is inconclusive, run Entra ID → Diagnose & solve problems → Sign-in Diagnostic → Troubleshoot and search with the correlation ID, application, user, and timestamp. Correlation-based searches cover events within 48 hours.^6^
Microsoft does not publish 5SR96 in the standard Teams status-code table. For an unlisted code that remains unresolved, Microsoft directs users to provide the status code to their IT administrator.^7^ If escalation is required, include the correlation ID, UTC timestamp, affected apps, phone OS/version, and the sign-in log’s request ID and failure reason; do not post tenant or account identifiers publicly.
References
- Error code 5sr96 in Outlook and Teams Mobile - Microsoft Q&A
- How do I clear the cache or locally reset/refresh the client/app?
- Account setup with modern authentication in Exchange Online
- How to troubleshoot Microsoft Entra sign-in errors
- Troubleshoot sign-in problems with Conditional Access
- What is the Sign-in diagnostic in Microsoft Entra ID?
- Why am I having trouble signing in to Microsoft Teams? | Microsoft Support