Teams Not Receiving Chat Messages On Desktop: Nov 2026 Fix

Updated November 20, 2026.

If chat messages reach you late, or not at all, in the Teams desktop app, Microsoft logged a service problem for exactly that.

Microsoft’s advisory TM1560260 says the cause was on its side, and that it has reverted the change responsible.

If your desktop app still lags after that, the steps below come from Microsoft’s own pages.

Quick answer: what to do right now

SituationWhat to do
Messages still late in the desktop appRestart the Teams desktop client, as Microsoft advises
You need messages immediatelyOpen Teams on the web at teams.microsoft.com
Restart did not helpSign out and back in, then update Teams
Still stuck after thatClear the Teams cache, then ask your admin to check Service health

What Microsoft says happened

Microsoft titled the advisory “Some users may have experienced delays or failures receiving chat messages in Microsoft Teams desktop client.”

ItemMicrosoft’s advisory
Advisory IDTM1560260
StartNovember 10, 2026, 13:16 UTC
EndNovember 19, 2026, 10:15 UTC
Final updateNovember 19, 2026, 11:36 UTC
StatusService restored

Microsoft’s first update on November 19 said users “may experience delays or failures receiving chat messages in Microsoft Teams desktop client.”

It added that affected users “may experience delays of several minutes before messages appear in the desktop client.”

The cause Microsoft gave

Microsoft’s stated root cause is “A recent service change caused Microsoft Teams desktop client registrations to be unexpectedly removed.”

In its words, when that happens, “the affected desktop client isn’t notified that it needs to re-register.”

Who is affected

Microsoft says the impact “was specific to some users receiving chat messages through the Microsoft Teams desktop client.”

It did not name a region, a Windows or Mac version, or a license type in its published update text.

The advisory is about the desktop client, so Teams on the web was the workaround Microsoft gave.

What Microsoft says it did

  • Microsoft reverted the service change: “We’ve completed the reversion of the service change responsible for the impact.”
  • It says people who still see problems “can restart the Microsoft Teams desktop client.”
  • It says it is “reviewing our update procedures to better identify similar issues during our development and testing cycles.”

The status is service restored, so the original fault should no longer be the cause if you still see delays today.

Step 1: restart the Teams desktop client

  1. Quit the Teams desktop client.
  2. Open Teams again.
  3. Ask someone to send you a test message in a chat.

Step 2: use Teams on the web meanwhile

Microsoft’s Teams on the web page says to find it at teams.microsoft.com.

The same page says it needs a Microsoft 365 account with a Business or Enterprise license plan, and recommends the new Microsoft Edge.

The advisory itself says users “may have been able to use Microsoft Teams on the web to access messages without delay.”

Step 3: sign out and back in

  1. Select your profile picture at the top of Teams.
  2. Select Sign out.
  3. Sign in again with the same account.

Microsoft notes that signing out removes your account’s info from the Teams app until you sign in again.

It also says signing out on one device does not sign you out on your other devices.

Step 4: check for updates

Microsoft says a notice appears at the top of the Teams window when an update is available.

  1. Select Update.
  2. Choose Update and restart Teams from the more options menu.
  3. If Teams does not reopen, open it yourself.

Microsoft adds that Teams updates automatically when an update is available and the app is idle.

Step 5: clear the Teams cache

If a restart, sign-out and update did not help, follow our step-by-step guide to clearing the Teams cache on Windows.

If Teams will not open or hangs on a loading screen, see how to fix Teams stuck loading.

If messages arrive but you get no banners, see how to fix Teams notifications not working.

How an admin checks Service health

  1. Go to admin.microsoft.com and sign in with an admin account.
  2. In the left navigation, go to Health > Service health.
  3. Review the table of services and their health state.

Microsoft says people assigned the Service Support admin and Helpdesk admin roles can view service health.

TabWhat Microsoft says it shows
OverviewAll services, their current health state, and any active incidents or advisories
Issue historyIncidents and advisories resolved within the last 7 or 30 days
Reported issuesIssues your tenant has reported from the form, and their status

Microsoft defines an advisory as a problem “affecting some users, but the service is still available,” often with a workaround.

Search for TM1560260 in Issue history to read Microsoft’s updates in full.

If you do not see your issue there, Microsoft says to use Report an issue.

Sources

The advisory wording above is Microsoft’s, as published in Microsoft 365 service status feeds; check your own Service health page for the live status.

Leave a Reply

Your email address will not be published. Required fields are marked *