When Teams keeps returning to Offline, the fastest fix is not always clearing cache. Offline can be a real presence state, a stale desktop signal, a manual status choice that did not clear, or a service-side presence delay. You need to find which layer is lying.
Use Teams on the web as your control because it removes part of the desktop app from the test. Then compare devices, status duration, sleep settings, and cache only after the symptom follows a pattern. That order saves time and avoids needless sign-outs.
First decide whether presence is really offline
Open Teams on the web, set yourself to Available, and ask a coworker to check your presence from their side. If the web version shows the correct state while the desktop app keeps showing Offline, focus on the desktop app, local cache, update state, or a sleeping device. If web and desktop both show Offline, the problem is broader.
Microsoft documents Teams presence as a state influenced by user activity, app state, and organization-level behavior. That means your presence can change when your computer sleeps, when Teams loses an active session, or when another signed-in endpoint becomes the stronger signal.
For broader presence symptoms, use this wider presence checklist as a companion reference. Keep this article focused on the Offline case so you do not mix several status problems into one test.
Use web Teams as the control
Do the first test in a browser window, not in the desktop app. If your browser status holds for ten minutes but the desktop app flips back to Offline, restart or update the desktop app before changing account settings.
Check devices before clearing cache
Teams presence can be affected by more than one signed-in device. A laptop that sleeps, a phone with an old session, or a second desktop running Teams can make the current device look inconsistent. Review where you are signed in and close Teams on devices you are not actively using.
A simple sequence works well:
- Set Teams on the web to Available.
- Close Teams on old desktops and tablets.
- Wake the main Windows device and keep it unlocked for a few minutes.
- Ask another user to confirm what they see.
If the status stays Available while only one active device is running Teams, the issue was probably competing device state rather than a broken account.
Clear stale manual status choices
Manual status and duration settings can outlive the moment when you chose them. Open the profile menu, set the status back to Available, and clear any status duration if the option is present. Also remove a custom status message if it suggests you are unavailable, because coworkers may treat that message as part of the presence signal.
Calendar and activity still matter
Presence is not only the small colored dot. Calendar events, calls, meetings, screen lock, and idle time can move you to Busy, In a meeting, Away, or Offline-like states depending on the client and tenant behavior. Test while you are not in a meeting and while the computer is awake.
Refresh Teams in the least disruptive order
Start with a normal Teams restart. Then check for updates. Only after that should you clear cache or sign out of every session. Cache cleanup is useful when a local client keeps showing stale data, but it is a blunt fix if the real cause is another device or a manual status duration.
If your status is not Offline but appears as a different broken value, separate that symptom. Use a separate stuck-state guide for that related presence failure, so you only follow it when the visible state matches that issue.
When the organization controls part of the answer
Some presence behavior is controlled by tenant configuration, service health, or admin policy. If several users in the same organization suddenly appear Offline, stop troubleshooting only your device. Ask an administrator to check service health and presence-related settings before everyone clears cache.
Shared frontline devices and virtual desktops also need a different test. Sign-in state, idle timeout, and reconnect behavior can make Teams look offline after a session handoff. In those cases, collect the device name, time of the status change, and whether web Teams matched the desktop status.
Quick answers
Why does Teams switch back to Offline after I pick Available?
A stale desktop session, sleeping device, expired manual status duration, or competing signed-in device can override what you just selected. Test in web Teams first, then close old sessions and retest before clearing cache.
Does clearing Teams cache always fix Offline status?
No. Cache cleanup helps when the local desktop app is holding stale presence data. It will not fix a sleeping computer, tenant issue, old mobile session, or status duration that keeps being reapplied.
Can my calendar make Teams look unavailable?
Calendar and meeting activity can change presence, but they usually produce states such as Busy or In a meeting rather than a clean Offline state. Still, run your test outside a meeting so calendar state does not confuse the result.
What should I tell IT if the issue continues?
Give IT the time of the status change, whether web Teams matched desktop Teams, which devices were signed in, and whether other users saw the same problem. That evidence is more useful than saying the status keeps changing.
Before you call it fixed
Leave Teams open on one active device for a few minutes and ask someone else to confirm your status from their client. If it stays correct in web and desktop Teams, the fix is stable enough to resume normal use. If it reverts again, record the exact trigger: sleep, app restart, meeting start, phone sign-in, or a tenant-wide event.