Encountering the dreaded Microsoft Teams Error AADSTS90023: Invalid Authentication? π© You're not alone. This Azure Active Directory (AAD) frustration blocks logins, disrupting your workflow. But don't worry β we've got your back with straightforward, battle-tested solutions to get you collaborating again in minutes. Let's dive in and crush this error! π
What is Error AADSTS90023 and Why Does It Happen?
The AADSTS90023 Invalid Authentication error signals an "invalid audience" mismatch in your authentication token. Simply put, Teams can't verify your login because the token's intended recipient (audience claim) doesn't align with Microsoft's expectations.
Common culprits include:
- π Corrupted browser cookies or Teams cache.
- β Outdated app versions or conflicting extensions.
- β οΈ Conditional Access policies in your organization's Azure AD.
- π Multi-factor authentication (MFA) glitches or expired sessions.
- π Proxy/VPN interference or network restrictions.
Recent updates to Azure AD (as of the latest 2026 patches) have tightened security, making these mismatches more frequent. But fear not β most fixes are quick and don't require IT admin access. 
Step-by-Step Guide: How to Solve Microsoft Teams Error AADSTS90023
Follow these prioritized steps. Start from the top β 80% of users fix it by Step 3! π
Step 1: Clear Teams Cache (Quickest Fix β)
The #1 cause? Stale cache. Here's how:
- Quit Teams completely (right-click tray icon β Quit).
- Press Win + R, type
%appdata%\Microsoft\Teams, hit Enter. - Delete contents of these folders:
Cache,blob_storage,databases,IndexedDB,Local Storage,tmp. - Restart Teams and sign in.
Pro tip: For Mac, go to ~/Library/Application Support/Microsoft/Teams and delete the same folders. Boom β authenticated! π
Step 2: Reset Credentials and Browser Data
If cache clear fails:
- Open Credential Manager (Windows Search β Credential Manager).
- Remove all "MicrosoftAccount", "msteams", or "aad" entries under Windows Credentials.
- In your browser (Edge/Chrome), clear cookies/site data for
login.microsoftonline.comandteams.microsoft.com. - Disable extensions like ad-blockers temporarily.
Step 3: Reinstall or Update Teams
Grab the latest Teams installer. Uninstall via Settings β Apps, then reinstall. Switch to the new Teams client if on legacy β it's more stable against AAD errors.
Step 4: Check Network and MFA
Toggle VPN/proxy off. Verify MFA prompts aren't blocked. Test on mobile data vs. Wi-Fi.
Advanced: Admin-Level Fixes
If you're an admin:
| Issue | Solution |
|---|---|
| Conditional Access Policy | Review in Entra admin center β Protection β Conditional Access. Exclude test users or adjust audience claims. |
| Token Audience Mismatch | Check app registrations in Entra ID for correct "api://..." audiences per Microsoft docs. |
| Federated Identity | Validate IdP metadata issuer/audience alignment. |
Troubleshooting Table: Common Scenarios
| Symptom | Likely Cause | Fix Priority |
|---|---|---|
| Error on desktop app only | Cache corruption | Step 1 (High) |
| Web version fails | Browser cookies | Step 2 (High) |
| All devices affected | Org policy | Admin table (Medium) |
Prevention Tips for Future-Proof Teams Logins
- β Keep Teams and browsers updated automatically.
- π Use Microsoft Edge for best AAD integration.
- β οΈ Regularly review Entra ID sign-in logs for patterns.
Still Stuck? Next Steps
If these don't resolve your Microsoft Teams Error AADSTS90023, check the Teams admin center or open a Microsoft support ticket. Share your error details for faster help.
You're now equipped to banish this error forever! π Teams awaits β happy collaborating! If this helped, drop a comment below. π
