teams Code 50058

How to Fix Microsoft Teams Error 50058

Diagnostic Procedures

  • 1 Identify the exact meaning of the error code
  • 2 Clear cache or credentials related to the software
  • 3 Check service server status for outages
  • 4 Perform a repair or reset on the desktop client
  • 5 Re-authenticate the connection to sync files

How to Fix Microsoft Teams Error 50058

If you are encountering Microsoft Teams Error Code 50058, you are experiencing a silent sign-in failure. The application is trying to log you in automatically using cached session tokens, but Microsoft Entra ID (formerly Azure Active Directory) cannot find an active authentication session or the session has expired.

This guide provides the necessary steps to resolve this error, clear stale tokens, and re-authenticate your connection.

1. Identify the Exact Meaning of the Error Code

Error Code 50058 maps directly to the Microsoft Entra ID error AADSTS50058 (UserInformationNotProvided).

This error triggers when:

  • Silent Authentication Fails: Teams attempts to renew your login token in the background (Single Sign-On / SSO) without prompting you for credentials, but the underlying session is expired, revoked, or invalid.
  • Password/MFA Changes: The user’s password or Multi-Factor Authentication (MFA) requirements were changed, rendering the existing silent login tokens invalid.
  • Tenant Policy Restrictions: Conditional access rules require a fresh login challenge, but the app fails to show the prompt.

Purging local caches and removing stored credentials forces Microsoft Teams to prompt you for a fresh login.

A. Windows Steps (PowerShell)

  1. Close Teams completely. Run the following command in PowerShell to terminate all Microsoft Teams processes: 
    Stop-Process -Name "ms-teams" -Force -ErrorAction SilentlyContinue
Stop-Process -Name "Teams" -Force -ErrorAction SilentlyContinue
  2. Delete the client cache files: 
    # For New Teams (v2)
Remove-Item -Path "$env:LOCALAPPDATA\Packages\MSTeams_8wekyb3d8bbwe\*" -Recurse -Force -ErrorAction SilentlyContinue

# For Classic Teams (v1)
Remove-Item -Path "$env:APPDATA\Microsoft\Teams\*" -Recurse -Force -ErrorAction SilentlyContinue
  3. Open the Credential Manager (via Start Menu), select Windows Credentials, and delete all entries containing MicrosoftOffice16, MicrosoftTeams, or virtualapp/didlogical.

B. macOS Steps (Terminal)

  1. Force quit Teams: 
    pkill -9 "Microsoft Teams"
pkill -9 "Teams"
  2. Remove the cache directories: 
    # For New Teams (v2)
rm -rf ~/Library/Group\ Containers/UBF8T346G9.com.microsoft.teams
rm -rf ~/Library/Containers/com.microsoft.teams2

# For Classic Teams (v1)
rm -rf ~/Library/Application\ Support/Microsoft/Teams
  3. Open Keychain Access, search for Microsoft Teams and Microsoft Office, and delete all matching secure keys (e.g., Microsoft Teams Identities Cache).

3. Check Service Server Status for Outages

Authentication loops can sometimes be triggered by cloud service degradation on Microsoft’s end.

  • Navigate to the Microsoft 365 Service Status Page or ask your system administrator to check the Microsoft 365 Admin Center under Health > Service health.
  • If Entra ID or Microsoft Teams is experiencing authentication issues, wait for Microsoft to resolve the outage.

4. Perform a Repair or Reset on the Desktop Client

If local application configuration files are corrupted, you can repair or reset the application.

A. Windows Apps Reset

  1. Press Windows Key + i to open Settings.
  2. Click Apps → Installed apps.
  3. Search for Microsoft Teams.
  4. Click the three dots (…) next to it and select Advanced options.
  5. Scroll down and click Repair. If the issue persists, click Reset (this clears app data).

Alternatively, you can run this PowerShell command to reset Teams V2:

Get-AppxPackage -Name "MSTeams" -AllUsers | Reset-AppxPackage

B. macOS Clean Reset

On macOS, removing the plist configuration files resets the client settings:

defaults delete com.microsoft.teams2
rm -f ~/Library/Preferences/com.microsoft.teams2.plist

5. Re-authenticate the Connection to Sync Files

Re-binding your corporate account to the operating system ensures that Single Sign-On (SSO) works correctly.

A. On Windows

  1. Open Settings (Win + I).
  2. Go to Accounts → Access work or school.
  3. Locate your account and click Disconnect.
  4. Restart your system.
  5. Return to Access work or school, click Connect, and log in with your credentials to establish a fresh relationship with Entra ID.

B. On macOS

  1. Open Microsoft Teams.
  2. If you are stuck in a loop, click your profile picture in the top-right corner (or the menu bar) and select Sign Out.
  3. Re-enter your work or school email address and complete the login verification (including MFA).

6. Summary Quick Reference Checklist

ActionCommand / PathExpected Outcome
Kill Teams ProcessStop-Process -Name "ms-teams" (Win) / pkill (Mac)Frees locked files.
Clear Windows Cache%localappdata%\Packages\MSTeams_8wekyb3d8bbweRemoves stale session cookies.
Clear Mac Cache~/Library/Containers/com.microsoft.teams2Resolves persistent cached tokens.
Reset Accounts LinkWindows Settings -> Access work or schoolRestores Device Join identity state.
Purge Keyring/CredentialsDelete Microsoft Teams keys in Windows/Mac storeForces app to prompt for credentials.