Microsoft Teams Status: How to Check If Teams Is Down Right Now (2026)
Where to find the official Microsoft Teams status page, what each service component means, and how to diagnose Teams meeting, messaging, and sign-in failures in real time.
Is Microsoft Teams Down Right Now?
Check Microsoft 365 Service Health at admin.microsoft.com/servicestatus (admin login required) or the public status page at status.office.com. Microsoft also posts outage updates at @MSFT365Status on X/Twitter.
Microsoft Teams Service Health Components
The Microsoft 365 Service Health Dashboard lists Teams under "Microsoft Teams" with separate tracking for each capability. Here is what each component covers:
Monitor Teams availability independently
Better Stack monitors your Teams web endpoint and any Teams-dependent integrations — get alerted to degradations faster than waiting for Microsoft's Service Health Dashboard to update.
Try Better Stack Free →Common Teams Issues and Fixes
| Symptom | Likely Cause | Where to Check |
|---|---|---|
| Teams meetings not connecting | Teams Meetings incident or firewall blocking UDP ports | admin.microsoft.com Service Health + check ports 3478-3481 UDP |
| No audio or video in meetings | Device permissions issue or Teams media relay degradation | Teams Settings → Devices; run M365 Connectivity Test |
| Messages not delivering | Teams Chat incident or client sync issue | M365 Service Health → Teams Messaging; sign out and back in |
| Teams app crashes on startup | Corrupted Teams cache or outdated client version | Clear Teams cache folder and update to latest client version |
| Cannot sign into Teams | Azure Active Directory incident or SSO misconfiguration | M365 Service Health → Azure Active Directory; check Entra admin center |
| Teams calendar not showing meetings | Exchange Online incident or mailbox sync delay | M365 Service Health → Exchange Online; wait 15 min for sync |
| Teams files tab not loading | SharePoint/OneDrive incident affecting Teams Files | M365 Service Health → SharePoint Online |
| Teams bots not responding | Bot Framework service degradation or bot-side failure | status.botframework.com + check bot provider status |
Microsoft Teams Troubleshooting: Step-by-Step
Check Microsoft 365 Service Health
IT admins should check admin.microsoft.com → Health → Service Health and filter for "Microsoft Teams." Look for any active advisories or incidents. Non-admins can check status.office.com or @MSFT365Status on X. If there is a listed incident, it explains your symptoms — wait for Microsoft's resolution updates.
Try Teams in a browser
Open teams.microsoft.com in a private browser window. If the web version works while the desktop app fails, the issue is with the desktop client — not the platform. Clear the Teams cache or reinstall the desktop app.
Clear the Teams desktop cache
Quit Teams completely, then delete the cache: Windows: %AppData%\Microsoft\Teams (delete all subfolders except Downloads). Mac: ~/Library/Application Support/Microsoft/Teams (delete subfolders except Downloads). Restart Teams — it rebuilds the cache on launch (takes 1-2 minutes).
Check your network for Teams requirements
Run the Microsoft 365 Network Connectivity Test at connectivity.office.com to identify network-layer issues. Teams requires access to specific Microsoft CDN URLs and UDP ports 3478-3481 for media. Corporate firewalls frequently block these — contact your IT team if the test shows failures.
Disconnect VPN if audio/video is failing
VPNs often degrade Teams call quality by routing media traffic through tunnel with high latency. Microsoft recommends VPN split tunneling for Teams to exclude Teams media traffic from the VPN tunnel. If you are on a VPN and calls are poor, try disconnecting VPN as a test.
Check Azure AD / Entra ID sign-in logs
If users cannot sign into Teams, check Azure Active Directory (now Entra ID) at entra.microsoft.com for sign-in failure logs. Also verify the Microsoft 365 Service Health for Azure AD incidents, which would prevent all Microsoft 365 logins including Teams.
Monitor Teams-dependent integrations proactively
Set up external monitoring for your Teams webhooks, bots, and dependent services — know before users report issues.
Try Better Stack Free →Frequently Asked Questions
Where is the official Microsoft Teams status page?
Microsoft Teams status is reported at admin.microsoft.com/servicestatus (requires Microsoft 365 admin login) and publicly at status.office.com. For a public overview without login, check portal.office.com or the Microsoft 365 Service Health Dashboard at portal.office.com/adminportal/home#/servicehealth. Microsoft also posts major outage updates at @MSFT365Status on Twitter/X.
Why is Microsoft Teams not working right now?
Microsoft Teams failures have several common causes: (1) A Microsoft 365 platform incident — check the Microsoft 365 Service Health Dashboard (admin.microsoft.com) or status.office.com, (2) Network or firewall issues — Teams requires specific ports and URLs; corporate firewalls often block Teams traffic, (3) Client cache corruption — delete the Teams cache (AppData/Roaming/Microsoft/Teams on Windows or ~/Library/Application Support/Microsoft/Teams on Mac) and restart, (4) Single Sign-On (SSO) / Azure AD issues — if your organization uses SSO, an Azure AD incident can prevent Teams login, (5) VPN interference — some VPNs block Teams media traffic; try disconnecting VPN and using Teams' built-in split tunneling.
Why are Microsoft Teams meetings not connecting?
Teams meeting connection failures commonly occur due to: (1) A Teams Meetings incident on the Microsoft 365 Service Health Dashboard — check admin.microsoft.com for 'Microsoft Teams' incidents affecting Meetings, (2) Audio/video device issues — go to Teams Settings → Devices and test your microphone and camera, (3) Network quality issues — Teams requires stable bandwidth; run the Microsoft 365 Network Connectivity Test at connectivity.office.com, (4) Firewall blocking media ports — Teams uses UDP ports 3478-3481 for media; contact your IT team if media fails while messaging works, (5) Meeting join link expiration — Teams join links can expire; generate a new meeting invite if older links fail.
Why are Teams messages not sending or delivering?
Teams message delivery failures can be caused by: (1) A Teams Chat/Messaging incident on the Microsoft 365 Service Health Dashboard, (2) The recipient's Teams client being offline — look for the grey dot indicating offline status, (3) Message retention policies — your organization may have data retention policies that prevent message delivery to external users, (4) Guest access restrictions — if messaging external contacts, check that your organization's Teams guest access policy allows it, (5) Teams client sync issues — sign out and back in, or clear the Teams cache to force a fresh sync with Microsoft servers.
Is Microsoft Teams down for everyone or just me?
To determine if Teams is down globally: (1) Ask your IT admin to check admin.microsoft.com → Health → Service Health for active Teams incidents, (2) Check status.office.com for public-facing status, (3) Monitor @MSFT365Status on Twitter/X for outage announcements, (4) Test Teams in a browser at teams.microsoft.com — if the web version works but the desktop app fails, it is a client-side issue, (5) Try Teams on a mobile device — if mobile works but desktop does not, clear the desktop Teams cache, (6) Test your network with Microsoft 365 Connectivity Test at connectivity.office.com to rule out local network issues.
Alert Pro
14-day free trialStop checking — get alerted instantly
Next time Microsoft Teams goes down, you'll know in under 60 seconds — not when your users start complaining.
- Email alerts for Microsoft Teams + 9 more APIs
- $0 due today for trial
- Cancel anytime — $9/mo after trial