Where most complaints about this service are coming from, over the last 24 hours.
Shows where the service URL was unreachable during the detected outage periods. Percentages indicate the share of failed checks from monitoring locations in each country.
Tap what’s going wrong — one click helps thousands of others see the outage.
The most common culprit is a cached session that went stale. Clear your browser cookies, open a private window, and try logging in at login.microsoftonline.com again. If you use the desktop app, go to File → Account → Sign Out, then sign back in. Also check that your system clock is accurate — a time mismatch of more than a few minutes breaks authentication silently.
First, check the outbox for stuck messages and delete any that are frozen there. Then go to Send/Receive → Work Offline and toggle it off if it's active. If the issue persists on the web version too, the problem is likely on the account level — try removing and re-adding the account in the desktop client.
This usually happens when the app loses its connection mid-session. Click your profile picture, choose Sign Out, relaunch Teams, and sign back in. If messages show as sent but recipients don't see them, the issue is likely a brief server-side delay — give it a few minutes before escalating.
Heavy browser extensions are often behind sluggish Microsoft 365 performance in the browser. Try disabling them one by one, or switch to a clean browser profile. For desktop apps, go to File → Options → Add-ins and disable COM add-ins that you don't actively use — they load at startup and quietly eat resources.