Error when trying to sign in to teams app

Dear @Scott Boston,

I understand that you’re having trouble signing in to Microsoft Teams. As a forum moderator, I genuinely wish I could directly access your account or delve into the backend systems to diagnose and fix this for you. However, our role here is limited to providing general guidance and solutions that can be applied by users.

Based on your description and my research, since you’re able to sign in successfully via the web but not through the desktop app on your iMac (macOS Tahoe), the issue is unlikely to be related to your account or password. Instead, it is most commonly caused by a corrupted authentication token or a Keychain conflict stored locally on your Mac.

In this situation, the Teams app attempts to reuse an outdated or broken authentication “handshake” with Microsoft’s services, which results in the “unexpected error” message. To resolve this, you’ll need to clear the local cache to force a fresh sign-in.

Please follow the steps below to see if this resolves the issue:

1.Clear Teams cache

1. If Teams is still running, right-click the Teams icon in the dock, and then select Quit or press Command+Q.
2. In the Finder, open the /Applications/Utilities folder, and then double-click Terminal.
3. Enter the following commands, and press Return after each command:
   rm -rf ~/Library/Group Containers/UBF8T346G9.com.microsoft.teams
   rm -rf ~/Library/Containers/com.microsoft.teams2
4. Restart Teams.

For reference: Clear the Teams client cache - Microsoft Teams | Microsoft Learn

2.Fix the Keychain Conflict

Sometimes the "Login Keychain" on Mac holds onto an old password that blocks the new app from connecting.

Quit Teams completely (right-click the icon in the Dock and select Quit, or use Activity Monitor to force quit if needed).

Open Keychain Access (Finder > Applications > Utilities > Keychain Access).

In the search bar, look for these terms one by one and delete all matching entries (check both "login" and "System" keychains on the left sidebar):

• com.microsoft.oneauth
• com.microsoft.adalcache
• OneAuthAccount
• msoCredentialSchemeADAL
• msoCredentialSchemeLiveId
• Microsoft Teams Identities Cache
• Teams Safe Storage
• MSOpenTech.ADAL.1
• MicrosoftOfficeRMSCredential

Also search for and delete any entries related to "Liveid", "teams", "skype", or "Exchange" that have matching timestamps.

Sign in to the account you want and restart Microsoft Teams.

If you spot multiple similar entries, delete them all, user report this has resolved similar issues where basic keychain clears miss nested auth data.

3.Uninstall and Reinstall Teams Completely

If the above doesn't work, a full wipe and reinstall often clears stubborn accounts:

• Quit Teams.
• Drag the Teams app from Applications to the Trash (or use a third-party uninstaller like App Cleaner & Uninstaller for a deeper clean)
• Empty the Trash, restart your Mac.
• Download the latest Teams version from the official Microsoft site and install it fresh.
• When you open it, sign in only with the desired account.

If none of the steps above resolve the issue, it’s possible that your organization’s Conditional Access policy allows web access but blocks the desktop app (for example, requiring device compliance, Intune enrollment, or specific security conditions). In that case, I recommend checking with your IT administrator.

I hope this information is helpful. Please follow these steps and let me know if it works for you. If you have any questions or need further assistance, please feel free to share them in the comments so I can continue to support you. I'm looking forward to your reply.

If the answer is helpful, please click "Accept Answer" and kindly upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread. 

Because sign-in works in the browser but fails in the Teams Mac app with a generic “unexpected error,” the problem is almost certainly with the local Teams client or its local configuration, not the account itself.

Use these targeted steps on the Mac client:

1. Check for a Teams status/error code

• On the Teams sign-in window, look in the lower-left corner for a status code (for example, 0xCAA20003, 0xCAA82EE7, etc.).
• If a code is shown, use the documented guidance:
  • 0xCAA20003 (authorization problem): Ensure the Mac’s date and time are correct. Incorrect time prevents secure (HTTPS) sign-in.
  • 0xCAA20004 (conditional access issue): Tenant admin must verify Microsoft Entra ID and Conditional Access policies for this user.
  • 0xCAA70004 / 0xCAA70007 / 0xCAA82EE2 / 0xCAA82EE7 (network/proxy/DNS issues): Confirm internet access and that no proxy, firewall, or network inspection tool is blocking Teams traffic.
  • 0xCAA90018 (wrong credentials): The macOS sign-in identity differs from Microsoft 365 credentials; sign in again with the correct username and password.
• If the code is missing from the table or no code appears, capture whatever code is shown and pass it to the organization’s IT admin for deeper investigation.

2. Confirm the tenant and account are healthy

• Since sign-in works in the web client, the account and tenant are generally functional.
• If there is any doubt about domain or Office 365 configuration, the IT admin should verify that the user is correctly licensed and that modern authentication is enabled and not blocked for this account.

3. Verify connectivity and environment

• Make sure the Mac has working internet access.
• If other Office apps (Word, Excel, Outlook) also show sign-in issues, treat it as a broader authentication/network problem and check for:
  • Misconfigured proxy
  • Network sniffing/inspection tools that are not configured to handle HTTPS
  • Firewall rules blocking Microsoft 365 endpoints
• If only Teams fails and the browser works, the issue is most likely local to the Teams desktop app.

4. Ensure the Teams client is current

• If the app opens far enough, select Settings and more (…) > Check for updates to ensure the latest Teams build is installed.
• If the app cannot be accessed, proceed directly to a clean reinstall (next step), which will also install the latest version.

5. Perform a clean reinstall of Teams on macOS A standard uninstall may leave behind cached org/account data that can cause sign-in failures. Do a full cleanup:

• Uninstall the Teams app from the Mac.
• Remove Teams-related local data so the app starts with a clean profile. On Mac, this includes deleting Teams’ container/group-container folders under the user’s Library (as demonstrated in similar Mac scenarios where old organizations remained stuck). This clears cached org membership and corrupted local state.
• Re-download and install the latest Teams for Mac client.
• Try signing in again with the same account that works in the browser.

6. If the error persists after a clean reinstall

• The organization’s IT admin should:
  • Run the Teams sign-in diagnostics for the affected user.
  • Confirm there is no Conditional Access or device management policy blocking the Mac.
  • Collect Teams debug logs from the Mac client and open a Microsoft support request, including:
    • Correlation Id
    • Timestamp
    • Any status/error code shown in the client
    • Confirmation that Teams web sign-in works on the same device

If at any point the issue appears only in the Teams web client (for example, stuck in a login loop in the browser), use the browser-specific “Teams is stuck in a login loop” guidance. In this case, the symptoms point to a desktop-app-specific problem, so focus on local cleanup, reinstall, and tenant-side diagnostics.

References:

• Why am I having trouble signing in to Microsoft Teams?
• Resolve sign-in errors in Teams
• Unable to remove Organization from Teams on my Mac - Microsoft Q&A