You send a message from your phone and it never shows up on the desktop. Or a colleague replies, they can see it, and your client is still showing the conversation from an hour ago. Teams chat not syncing is annoying precisely because everything looks connected — you’re online, you can send — but the conversation is out of step.
The reassuring part is where your data lives. Chat history sits in the Microsoft 365 cloud, not on your laptop. So a sync problem is almost never lost messages; it’s a client that has stopped pulling the latest from the service. The fix is to figure out which client is behind and make it refresh, working from the cheapest, least disruptive step up to a full reset.
This guide goes in that order: confirm it’s not an outage, force a refresh, clear the cache, reset the client, then rule out network and policy causes. Most cases clear up in the first two or three steps.
Step 1: Check it’s not a service outage
Before touching the client, rule out the simplest explanation: the service itself. If multiple people across different devices and networks all see chats lagging at the same time, it’s a Microsoft-side issue and there’s nothing to fix locally.
- Check the Microsoft 365 service health dashboard in the admin center for any active Teams advisory or incident.
- Compare with a colleague. If their chat is fine on the same network, the problem is your client. If everyone’s is broken, it’s the service.
- Try Teams on the web at teams.microsoft.com from the same machine. If web works and the desktop app doesn’t, the issue is the desktop client, not the service or your account.
That last test is the most useful single check. The web client and the desktop client hit the same back end, so if the web shows current messages and the app doesn’t, you’ve isolated the fault to the installed client.
Step 2: Force the client to refresh
The lightest fix is to make the client reconnect and pull fresh data. None of this touches your data or signs you out.
- Switch focus to the chat. Teams refreshes a conversation when you open it; clicking into the lagging chat sometimes pulls the missing messages immediately.
- Relaunch Teams properly. Don’t just close the window — quit it from the system tray so the process actually stops, then reopen it. A window close often leaves the app running in the background, so it never reconnects.
- Check your connection. A weak or intermittent network leaves Teams half-connected: present enough to look online, not stable enough to sync. Confirm other cloud apps are working too.
If a real relaunch and a stable connection bring the conversation back up to date, you’re done. If the client comes back and is still showing stale chat, move on to the cache.
Step 3: Clear the client cache
A corrupt or stale local cache is one of the most common reasons a single client stops updating. The cache exists to make Teams start fast and work offline, but when it goes bad it can pin you to an old view of a conversation. Clearing it forces Teams to rebuild from the service.
The exact steps and folder paths depend on whether you’re on new Teams or classic Teams, and getting the wrong folder accomplishes nothing. The full procedure — quitting the right process, the precise cache locations, and what to expect afterward — is in how to clear the Microsoft Teams cache on Windows. The short version for new Teams on Windows:
%localappdata%\Packages\MSTeams_8wekyb3d8bbwe\LocalCache# New Teams runs as ms-teams; classic Teams runs as Teams
Get-Process ms-teams -ErrorAction SilentlyContinue
Get-Process Teams -ErrorAction SilentlyContinue
# If either returns a process, quit Teams from the tray and re-check before deleting the cacheAfter a cache clear, the first launch is slower while Teams pulls everything fresh, and that’s exactly the point — it rebuilds the conversation view from the service rather than the stale local copy.
Step 4: Reset or reinstall the client
If a clean cache doesn’t fix it, the install itself may be the problem. Reset before you reinstall — it’s faster and often enough.
- Sign out fully and back in. This re-establishes your session and clears stale authentication state. If chat updates after signing out and in, the issue was a stuck session, not the data.
- Check for updates. An out-of-date client can misbehave in ways that newer builds fixed. Let Teams update and relaunch.
- Reinstall as a last resort. If sign-out and cache clear both fail, uninstall and reinstall the client. For new Teams, remove the packaged app and reinstall the current version. A reinstall is heavier than a cache clear but rebuilds everything cleanly.
A persistent sign-in prompt or a client that won’t hold its session is its own symptom with its own causes; if you’re stuck in that loop, Teams keeps asking you to sign in covers it in detail.
Escalation order for chat not syncing
| Service health + web client test | Rules out an outage and isolates client vs service |
|---|---|
| Force refresh / proper relaunch | Fixes a temporarily stalled connection — no data touched |
| Clear the cache | Fixes stale or corrupt local data — most common single-client fix |
| Sign out / update / reinstall | Fixes a broken session or install |
| Network + policy check | Fixes the case where one network or account is the only place it breaks |
Step 5: Rule out network and policy causes
If one specific network is the only place sync breaks, or only one account is affected everywhere, the cause is environmental rather than the client.
Network. Teams needs steady access to Microsoft 365 endpoints. A proxy or firewall that blocks or throttles them can leave chat partially working — you send but don’t receive, or messages arrive only when you reopen a chat. If sync is fine at home and broken at the office, ask your network team to confirm the required Microsoft 365 URLs and ports are allowed and not being inspected in a way that breaks the connection.
Policy and account. A messaging policy can restrict what a user can do in chat, though it won’t normally stop sync outright. More relevant: if a single account misbehaves on every device while others are fine on the same network, the problem follows the account, not the machine — worth a look at the user’s licensing and any recent policy changes.
Narrowing down a stubborn sync problem
- Does the web client show current messages on the same machine? (client vs service)
- Is it one user everywhere, or everyone on one network? (account vs network)
- Did it start after a network or firewall change? (environmental)
- Does another network fix it instantly? (points to the original network)
- Is the client fully up to date? (rules out a known client bug)
When only notifications, not messages, are behind
Sometimes the chat itself is current the moment you open it, but you never got told a message arrived. That’s a notification problem, not a sync problem, and the fix path is different — it’s about notification settings, focus assist, and background app behavior rather than cache or service health. If that matches what you’re seeing, start with Teams notifications not working instead of resetting the whole client.
Wrapping up
Teams chat not syncing is almost always a client that has fallen behind the service, not lost data. Work in order: confirm it isn’t an outage with the service health dashboard and the web-client test, force a proper relaunch, then clear the cache, which fixes the majority of single-client cases. If that fails, sign out, update, or reinstall, and only then look at network and policy if one specific network or account is the common factor.
The web-client comparison is the test worth doing first every time — it tells you in seconds whether you’re fixing the client or waiting on the service. For the cache specifics, see clearing the Teams cache on Windows, and find more fixes in the Microsoft Teams guides.
