Why Teams Presence Gets Stuck
Microsoft Teams calculates your presence from several independent signals simultaneously: keyboard and mouse activity on the desktop app, screen lock and sleep state, your Outlook calendar, an active call or meeting, your Teams mobile app state, and any manual override you've set. When those signals contradict each other — or when the presence sync service has a hiccup — the status visible to your colleagues can freeze at the wrong value.
The key thing to understand: presence is calculated per client and then aggregated server-side. Your desktop might be reporting Available while your phone (which locked and went to sleep) is still reporting Away from a stale session. Teams resolves the conflict, but not always in your favour.
The 7 Fixes (In Order of Speed)
Reset your status manually
Click your profile picture → click your current status → select Available. Then optionally set a duration (e.g. "Available for 4 hours"). This is the 30-second fix and works when the status is simply lagging behind actual activity.
Fully quit and relaunch Teams
Minimising Teams does not close it — it continues running in the system tray. Right-click the Teams icon in the taskbar (Windows) or menu bar (Mac) and choose Quit. Then relaunch. This forces a fresh presence handshake with Microsoft's servers.
Clear the Teams cache
On Windows: quit Teams, press Win+R, type %appdata%\Microsoft\Teams, and delete the contents of the Cache, blob_storage, databases, and Local Storage folders. On Mac: ~/Library/Application Support/Microsoft/Teams. Your messages are stored server-side; clearing the cache only removes local temp files.
Sign out and sign back in
Go to your profile picture → Sign out. This is stronger than quitting because it de-registers your presence endpoint entirely. When you sign back in, Teams re-registers fresh. Best used when quit + cache clear didn't resolve the issue.
Check for a phantom calendar event
Open Outlook and look for any active or upcoming calendar block — particularly recurring meetings that may have been cancelled or moved. Teams sometimes holds the "In a meeting" status for a deleted event. Remove the orphaned calendar entry or wait for the next sync cycle (~15 minutes).
Force-quit the Teams mobile app
If the Teams app on your phone backgrounded while you were Away, it may still be reporting that status. Force-close the mobile app on iOS or Android, or sign out of it temporarily. The server-side aggregation will then rely solely on your desktop session.
Wait for the server-side sync window
Presence aggregation has a server-side propagation delay of up to a few minutes. If you've tried the above fixes and the status is still wrong for others but correct for you, it's likely a replication lag. Give it 5–10 minutes before escalating.
Cause-to-Fix Reference
| Symptom | Likely Cause | Best Fix |
|---|---|---|
| Stuck on Away despite activity | Stale presence cache or idle timer lag | Fix 03 Clear cache |
| Shows "In a meeting" when free | Phantom calendar event | Fix 05 Remove calendar block |
| Shows Offline to others, Available to you | Presence endpoint not re-registered | Fix 04 Sign out / sign in |
| Flickers between Away and Available | Mobile app conflict | Fix 06 Force-quit mobile |
| Status correct for you, wrong for colleagues | Server-side propagation lag | Fix 07 Wait 5–10 min |
| Goes Away again within minutes | Inactivity timer — normal behaviour | Use a presence app |
Why Teams Keeps Going Away Even When You're Active
This is worth addressing separately because it's the most common complaint — and it's not actually a bug. Teams has a built-in inactivity timer that flips you to Away after roughly 5 minutes of no keyboard or mouse input on the desktop app, regardless of what you're doing. If you're reading a document, on a phone call, or watching a screen recording, Teams sees no input and marks you Away.
The manual status reset (Fix 01) and cache clear (Fix 03) won't solve this because the root cause is Teams's presence calculation logic, not a sync error. The only reliable solutions are:
- Keep moving: A single mouse nudge every few minutes resets the 5-minute timer.
- Use a cloud-based presence tool: Services like Stay Green On Teams maintain your Available status server-side, so no local activity is needed. Your laptop can be closed.
- Keep the Teams web app open in an active browser tab: The web client tracks browser-tab focus rather than system input, but only stays Active while the tab is focused and the screen isn't locked.
See our full guide on keeping Teams active for a detailed comparison of every approach.
When the Fix Doesn't Stick
If your status resets correctly but then goes wrong again within the same session, you have a recurring sync issue — not a one-off glitch. The most reliable resolution in this case is to sign out fully (Fix 04), clear the cache (Fix 03), and then sign back in. This combination re-establishes your presence endpoint from a clean state.
If the problem persists across multiple sign-ins, contact your Microsoft 365 admin. Tenant-level presence settings and network proxy configurations can affect how Teams reports status, and those are outside what you can fix from the client side.