Guides / Teams chat messages not delivering or stuck sending

Part of: Meetings, calls and chat problems

Last reviewed 5 Oct 2026 · By Harry

Teams chat messages not delivering or stuck sending

Teams chat stuck on sending, messages missing, or notifications fail? Client, sync and policy checks before you declare an outage.

Chat shows a clock icon and never turns into a tick. Or you send a message and the other person swears it never arrived. Or chat works on the phone and not on the desktop. These are not the same as "Teams is down", and they are not the same as call freezes. Chat is a messaging path. Treat it like one.

Is it Teams?

Open the Teams status page and, if you are an admin, Service health in the Microsoft 365 admin centre. A real messaging incident usually names chat, presence or the whole client for many tenants. If status is clear and your neighbours are chatting normally, stay on this guide. If the whole client is a white screen, use Teams stuck loading instead. If only meetings fail, use can't join meeting.

User checks

1. Watch the send state. A persistent clock or "Sending" means the client has not handed the message to the service. A delivered message that the other person cannot see is a different fault (their client, retention, or they are looking at the wrong chat).
2. Web vs desktop vs mobile. Open teams.microsoft.com in a private window and send the same chat. If web works, clear the desktop cache (Teams → Help → Delete app data / clear cache, then restart) rather than rebuilding the PC.
3. Another network. Phone LTE off the office Wi-Fi. Proxies that break long-lived HTTPS and websocket upgrades cause chat to stall while status pages look fine.
4. VPN. Full-tunnel VPNs that hairpin Microsoft 365 through head office delay or drop chat. Split-tunnel the Optimize category if policy allows — see Microsoft's guidance on Microsoft 365 URLs and IP ranges.
5. Sign out and back in once. Expired tokens after Conditional Access changes look like silent send failures.
6. Wrong chat or missing person. Confirm you are in the 1:1 or group you think you are. Guests and federated users sometimes appear in search but cannot receive until external access is allowed.

Notifications vs delivery

Messages can land while the toast never fires. Check Windows Focus assist / macOS Focus, Teams notification settings (banner vs only show in feed), and per-chat mute. Mobile often stays quiet while the desktop is active — that is by design in many tenants. A "message not delivering" ticket that is really "I did not get a banner" wastes hours.

Admin and policy causes

• Messaging policies. Teams admin centre messaging policies can disable chat, Giphy, or read receipts for a group. A new starter in a restricted policy looks broken.
• External access and guest access. Federation with other Microsoft 365 tenants and Skype consumer must be allowed for some chats. The sender sees success locally while the remote side never receives.
• Retention and eDiscovery holds. Aggressive retention can remove messages shortly after send. Users report "messages disappear", which is not a transport failure.
• Compliance / DLP. Data loss prevention can block a message with sensitive content. The client may show a policy tip — read it before resetting the laptop.
• Presence and chat service degradation. When Microsoft posts a chat or presence incident, stop clearing caches every five minutes. Point users at Outlook or phone SMS for the duration and watch Service health.
• Client version rings. A broken desktop build in the Office update channel can stall send while the web client is fine. Move the user to a known-good channel or force an update after confirming web works.

Evidence worth collecting

Before escalating to Microsoft, capture: time (with time zone), chat type (1:1, group, channel), whether web worked, whether other users in the same office succeeded, and any policy tip text. Teams admin centre → Call analytics is for meetings; for chat, Message Centre / Service health and the user's client logs matter more.

When to escalate

Escalate to Microsoft when Service health names chat for your tenant, or when users on different networks and clients all fail to deliver at the same minute. Escalate to networking when only one office fails and LTE works. Escalate to identity when only guests or federated chats fail. One user with a sick desktop cache is not an outage.

Related status pages

• Microsoft Teams
• Microsoft 365
• Microsoft Azure

Related guides

• Teams stuck on loading or a white screen: what to do
• Teams “We couldn’t connect you”: can’t join meeting triage
• Slack messages not sending or notifications not arriving

FAQ

Why is my Teams message stuck on sending?

Usually the desktop client lost its connection, a proxy or VPN is interfering, or the session token expired. Try Teams in a private browser window and another network before rebuilding the PC.

The other person says they never got my Teams chat — why?

Confirm you used the right chat, that external/guest access is allowed, and that retention or DLP did not remove or block the message. Ask them to check web and mobile as well as desktop.

Is chat failure the same as a Teams outage?

Not always. Meetings can fail while chat works, and the reverse. Check the Teams status page and Service health for a messaging incident before you tell the business Teams is down.

Do cleared Teams caches delete chat history?

No. History lives in the service. Clearing client cache removes local data and the app downloads it again.