Is Microsoft Teams Down? How to Check Teams Status, Fix Connection Issues & Troubleshoot Calls (2026 Guide)

The Collaboration Layer Everyone Depends On

Microsoft Teams isn't just a chat app. With 320+ million monthly active users as of 2026, it's the communication nervous system for most of the corporate world. When Teams goes down, it's not just messages that stop — meetings cancel, file collaboration freezes, phone systems (Teams Phone) go silent, and entire workflows built on Teams integrations grind to a halt.

What makes Teams outages particularly disruptive is its deep integration with the Microsoft 365 ecosystem. Teams doesn't operate independently — it depends on Entra ID (formerly Azure AD) for authentication, Exchange Online for calendar and meetings, SharePoint for file storage, OneDrive for personal files, and Azure for the underlying infrastructure. A failure in any of these services can cascade into Teams, even when Teams itself is technically operational.

This guide goes deep into Teams architecture, shows you how to diagnose whether the problem is Teams, your network, or your organization's configuration, and gives you actionable workarounds for every type of Teams failure.

Microsoft Teams Architecture: Why It's Complex

Understanding Teams' architecture explains why outages are so varied — and why "Teams is down" can mean very different things for different users.

The Seven Pillars of Teams

Teams is built on seven interconnected service pillars, each of which can fail independently:

1. Entra ID (Authentication Foundation) Every Teams action starts with authentication through Microsoft's Entra ID (formerly Azure AD). This is the single most critical dependency — if Entra ID goes down, you can't log in to Teams, and existing sessions may invalidate. Entra ID processes billions of authentications daily across all Microsoft 365 services, making it both the most resilient and the most impactful component when it fails.

2. Teams Messaging Service (Chat & Channels) The real-time messaging backbone handles chat messages, channel posts, reactions, and presence indicators. Built on a distributed messaging architecture with regional data residency (your data stays in your geo), this service handles message delivery, read receipts, typing indicators, and notification routing. Messages are stored in Azure Cosmos DB with Exchange Online as the compliance backend.

3. Calling & Media Infrastructure Teams Phone and calling uses Microsoft's Transport Relay infrastructure — a global network of media relay servers that handle audio/video streams. Calls can be peer-to-peer (direct between clients when on the same network) or relayed through Microsoft's servers. Teams Phone System (PSTN calling) adds another dependency on SBC (Session Border Controller) gateways and Microsoft's telephony infrastructure.

4. Meeting & Conference Service Meeting infrastructure is separate from 1:1 calls. Meetings use dedicated conference servers that handle multi-party mixing, recording, live transcription, breakout rooms, and meeting policies. Large meetings (1,000+ participants) and webinars use additional scaling infrastructure. Town halls and live events have their own dedicated pipeline.

5. SharePoint & File Service Layer Every Teams channel has a SharePoint site behind it. The Files tab, shared files in chat, and OneNote notebooks all depend on SharePoint Online and OneDrive. When SharePoint has issues, Teams chat still works but file sharing, the Files tab, and meeting recordings become unavailable.

6. Exchange Online (Calendar & Scheduling) Meeting scheduling, calendar integration, presence status from Outlook, and meeting-related notifications all flow through Exchange Online. If Exchange has issues, you can still chat and call, but scheduling meetings or seeing calendar-based presence fails.

7. App Platform & Integrations Teams hosts thousands of third-party apps, bots, and connectors (Trello, Jira, ServiceNow, Power Automate flows). These run in the Teams App Framework and depend on both Teams infrastructure and the third-party service. App failures are the most confusing because they look like Teams issues but are actually third-party problems.

The Dependency Chain

Here's why Teams outages cascade unpredictably:

Azure Infrastructure
  └── Entra ID (Authentication)
        ├── Teams Messaging Service
        │     ├── Chat & Channels
        │     ├── Presence & Notifications
        │     └── Compliance & eDiscovery
        ├── Teams Calling & Media
        │     ├── VoIP / P2P Calls
        │     ├── Teams Phone (PSTN)
        │     └── Media Processing (recording, transcription)
        ├── Teams Meetings
        │     ├── Conference Servers
        │     ├── Breakout Rooms
        │     └── Live Events / Town Halls
        ├── SharePoint Online → Files, Tabs, Wiki
        ├── Exchange Online → Calendar, Scheduling, Presence
        └── App Platform → Bots, Connectors, Power Automate

Key insight: A "Teams outage" is almost never all seven pillars going down simultaneously. More commonly, one pillar fails — creating partial outage symptoms that are confusing to diagnose. You might be able to chat but not call, or join meetings but not see the calendar.

Common Teams Failure Modes

1. Authentication Failures (Entra ID)

Symptoms: Can't sign in, get "We're sorry — we've run into an issue" error, desktop app shows spinning wheel, signed out unexpectedly.

Root cause: Entra ID service disruption, conditional access policy change, or token refresh failure.

Diagnostic steps:

• Try signing in to portal.office.com (tests Entra ID directly)
• Check if other Microsoft 365 apps work (Outlook, OneDrive)
• If nothing works, it's an Entra ID outage, not Teams-specific
• If only Teams fails, clear your Teams credentials:
  • Windows: Settings > Accounts > Email & accounts > Remove your work account, then re-add
  • Mac: Keychain Access > search "Microsoft" > delete Teams-related entries

2. Chat & Message Delivery Failures

Symptoms: Messages show "not sent" with a red exclamation mark, channels won't load, typing indicators missing, read receipts delayed.

Diagnostic steps:

• Send a message in a different channel — if it works, the original channel may have a sync issue
• Check if mentions and notifications are working (separate subsystem)
• Try the web app — if web works but desktop doesn't, clear the desktop cache:

# Windows: Close Teams completely first
rd /s /q "%appdata%\Microsoft\Teams\Cache"
rd /s /q "%appdata%\Microsoft\Teams\blob_storage"
rd /s /q "%appdata%\Microsoft\Teams\databases"
rd /s /q "%appdata%\Microsoft\Teams\GPUcache"
rd /s /q "%appdata%\Microsoft\Teams\IndexedDB"

# Mac: Close Teams completely first
rm -rf ~/Library/Application\ Support/Microsoft/Teams/Cache
rm -rf ~/Library/Application\ Support/Microsoft/Teams/blob_storage
rm -rf ~/Library/Application\ Support/Microsoft/Teams/databases

• If the web app also fails, it's a backend messaging service issue — check apistatuscheck.com for confirmation

3. Call Quality & Drop Issues

Symptoms: Audio cutting out, video freezing, "poor network" banner, calls disconnecting after a few minutes.

Call quality is almost always a network issue, not a Teams outage. Here's how to verify:

Run the Teams call quality diagnostic:

1. In Teams, click your profile picture > Settings > Calls
2. Make a test call (call echo bot)
3. If the test call is clear but real calls aren't, the issue is with the other party's network

Network requirements for Teams:

Feature	Bandwidth	Latency	Jitter	Packet Loss
Audio calls	130 Kbps	< 100ms	< 30ms	< 1%
Video (720p)	2.5 Mbps	< 100ms	< 30ms	< 1%
Screen sharing	2 Mbps	< 100ms	< 30ms	< 3%
Large meetings	6.5 Mbps	< 100ms	< 30ms	< 1%

The VPN problem: VPNs route Teams media traffic through your organization's network instead of directly to Microsoft. This adds latency and reduces quality. Solution: configure VPN split tunneling to let Teams traffic bypass the VPN. Microsoft provides specific IP ranges and ports for this.

4. Meeting Join Failures

Symptoms: "Something went wrong" when clicking meeting link, stuck on "Joining..." screen, meeting lobby timeout, can't see the meeting on calendar.

Diagnostic decision tree:

1. Can you join any meeting, or just this specific one?

   • Specific meeting → link may be expired/malformed. Ask organizer to resend
   • All meetings → authentication or client issue

2. Are you internal or external (guest)?

   • External/guest → organization may have disabled guest access or external meeting join
   • Internal → check calendar sync (Exchange dependency)

3. Does the web app work?

   • Web works, desktop doesn't → clear desktop cache, reinstall
   • Neither works → check Entra ID status, then Teams meeting service status

4. Is it a large meeting / webinar / town hall?

   • Large format meetings have separate infrastructure with different capacity limits
   • Town halls are limited to 10,000 attendees (20,000 in preview)

5. Screen Sharing & Presentation Failures

Symptoms: Black screen when sharing, "You can't share right now" error, other participants can't see shared content, application sharing works but desktop sharing doesn't.

Permission checklist:

• macOS: System Settings > Privacy & Security > Screen Recording > Enable for Microsoft Teams
• Windows: If sharing individual apps works but not desktop — run Teams as administrator
• Linux: Screen sharing requires PipeWire (Wayland) or X11 — check your display server

GPU conflicts: If shared content appears as a black rectangle:

1. Teams Settings > General > Disable GPU hardware acceleration
2. Restart Teams
3. Try again — this resolves most black-screen sharing issues

Meeting policy restrictions: Organization admins can restrict screen sharing. Check with your IT department if you get "You don't have permission to share content in this meeting."

6. File & Tab Failures (SharePoint Dependency)

Symptoms: Files tab shows error, can't upload/download files in chat, shared files won't open, OneNote tabs fail to load.

Root cause: Almost always a SharePoint Online issue, not Teams.

Verification:

1. Go to sharepoint.com directly — can you access your sites?
2. Try OneDrive.com — can you access your files there?
3. If SharePoint/OneDrive work but Teams files don't, clear Teams cache

Workaround: Share files through OneDrive links directly instead of through Teams file sharing during SharePoint outages.

Outage Patterns: When Teams Goes Down

Deployment-Related Outages

Microsoft deploys updates to Teams on a ring-based schedule:

• Ring 0 (Dogfood): Microsoft internal — catches most issues
• Ring 1 (TAP): Technology Adoption Program customers
• Ring 2/3 (Production): General availability, rolled out by region

Most Teams outages happen during Ring 2/3 rollouts. Tuesday and Wednesday are the highest-risk days for deployment-related issues, as Microsoft typically pushes production changes mid-week.

Geographic & Regional Patterns

Teams infrastructure spans 60+ Azure regions. Outages are frequently regional:

• US East / US Central — highest traffic, most impacted during capacity issues
• Europe West (Netherlands/Ireland) — frequently affected by EU data residency processing
• Asia Pacific — time zone differences mean European/US outages sometimes cascade into APAC during overnight maintenance windows

If Teams is down for you but not for colleagues in another region, it's almost certainly a regional infrastructure issue.

Peak Load Failures

Teams experiences peak load patterns that can trigger capacity issues:

• Monday mornings (8-10 AM by time zone) — weekly usage spike as everyone logs in
• January / Back-to-school seasons — annual peaks in new user onboarding
• Major weather events — sudden shift to remote work floods capacity
• Global events — COVID-19 drove Teams from 75M to 300M daily users in 2 years

Cascading Microsoft 365 Failures

The most disruptive Teams outages aren't Teams-specific — they're Microsoft 365 platform failures that cascade:

July 2024 — CrowdStrike Incident: A faulty CrowdStrike Falcon update caused Windows BSOD on 8.5+ million machines globally. While not a Teams server issue, it knocked out millions of Teams desktop clients, disrupted Teams Phone (PSTN) infrastructure, and affected Teams Rooms devices.

July 2022 — Global Teams Outage: A deployment introduced a bug that prevented users from logging in worldwide. The outage lasted approximately 4 hours during business hours and affected an estimated 100+ million users. Root cause: an internal service update removed an authentication token validation step.

January 2023 — WAN Routing Change: A wide-area network routing configuration change disrupted connectivity to multiple Microsoft 365 services including Teams. Chat worked intermittently but calls and meetings were severely impacted for 6+ hours.

September 2020 — Entra ID (Azure AD) Outage: A backend deployment caused authentication failures across all Microsoft 365 services. Teams was completely inaccessible for approximately 5 hours. This was an Entra ID failure, not a Teams failure — but the user experience was "Teams is down."

Enterprise Admin Troubleshooting

If you're a Microsoft 365 admin, you have additional diagnostic tools:

Service Health Dashboard

1. Go to admin.microsoft.com > Health > Service health
2. Filter for "Microsoft Teams"
3. Look for active advisories and incidents
4. Check the "Issue history" tab for recently resolved issues

Microsoft 365 Admin Center — Message Center

Check Message Center for planned changes that might affect Teams functionality. Microsoft posts planned maintenance, feature changes, and policy updates here 7-30 days in advance.

Teams Admin Center Call Quality Dashboard

1. Go to admin.teams.microsoft.com > Analytics & reports > Call quality dashboard
2. Review call quality metrics for your organization
3. Look for patterns: specific users, networks, or times with poor quality

Network Assessment

Run the Microsoft 365 network connectivity test at connectivity.office.com:

• Tests connectivity to Teams service endpoints
• Measures latency, bandwidth, and DNS resolution
• Identifies network path issues and suboptimal routing
• Recommends optimizations specific to your network

Tenant-Level Diagnostics

# PowerShell: Check Teams service health (requires Microsoft.Graph module)
Connect-MgGraph -Scopes "ServiceHealth.Read.All"
Get-MgServiceAnnouncementHealthOverview -Filter "service eq 'Microsoft Teams'"

# Check recent incidents
Get-MgServiceAnnouncementIssue -Filter "service eq 'Microsoft Teams' and status eq 'serviceOperational'"

Teams Phone (PSTN) Specific Issues

If your organization uses Teams as a phone system, PSTN-specific outages have unique characteristics:

Teams Phone architecture:

• Calling Plans (Microsoft PSTN): Microsoft provides the phone numbers and PSTN connectivity. Outages affect all calling to/from external phone numbers.
• Direct Routing: Your organization's SBC connects to Teams. SBC or carrier issues look like Teams outages but aren't.
• Operator Connect: Third-party telco provides PSTN via API. Telco outages cascade into Teams.

Phone-specific troubleshooting:

1. Can you make Teams-to-Teams calls? (Tests Teams calling infrastructure)
2. Can you call external phone numbers? (Tests PSTN connectivity)
3. If internal works but external doesn't → SBC/carrier/Calling Plan issue
4. If neither works → Teams calling infrastructure issue

Monitoring & Early Warning

Automated Teams Health Check

import requests
import time

TEAMS_ENDPOINTS = [
    {"name": "Teams Web", "url": "https://teams.microsoft.com", "expect": [200, 302]},
    {"name": "Teams API", "url": "https://teams.microsoft.com/api/mt/part/emea-03/beta/users/tenants", "expect": [401]},
    {"name": "Presence API", "url": "https://presence.teams.microsoft.com/", "expect": [200, 401, 403]},
    {"name": "Entra ID", "url": "https://login.microsoftonline.com/common/oauth2/v2.0/token", "expect": [400, 405]},
    {"name": "Graph API", "url": "https://graph.microsoft.com/v1.0/", "expect": [401]},
]

def check_teams_health():
    results = []
    for endpoint in TEAMS_ENDPOINTS:
        try:
            resp = requests.get(
                endpoint["url"],
                timeout=10,
                headers={"User-Agent": "TeamsHealthCheck/1.0"},
                allow_redirects=False
            )
            healthy = resp.status_code in endpoint["expect"]
            results.append({
                "name": endpoint["name"],
                "status": resp.status_code,
                "healthy": healthy,
                "latency_ms": round(resp.elapsed.total_seconds() * 1000)
            })
        except requests.exceptions.RequestException as e:
            results.append({
                "name": endpoint["name"],
                "status": "ERROR",
                "healthy": False,
                "error": str(e)
            })
    return results

if __name__ == "__main__":
    for result in check_teams_health():
        status = "✅" if result["healthy"] else "❌"
        latency = f'{result.get("latency_ms", "N/A")}ms'
        print(f'{status} {result["name"]}: {result["status"]} ({latency})')

Proactive Monitoring with API Status Check

Rather than waiting for Microsoft's Service Health Dashboard (which can lag 15-30 minutes behind actual outages), set up proactive monitoring:

1. API Status Check — monitors Teams endpoints in real-time, alerts faster than Microsoft's own dashboard
2. Better Stack — set up custom monitors for your organization's critical Teams endpoints
3. Configure multiple alert channels — don't rely solely on Teams (or email through Exchange) for outage notifications, since both depend on the same Microsoft infrastructure

When Teams Is Down: Communication Alternatives

Tier 1 — Immediate Fallback (< 5 minutes to set up)

• Phone/SMS — old school, always works
• WhatsApp / Signal — most people already have these installed
• Google Meet — browser-based, no install needed, great for emergency meetings

Tier 2 — Temporary Workspace (< 30 minutes)

• Slack — closest feature parity (channels, chat, calls, file sharing)
• Zoom — best for meetings and large calls
• Discord — free, supports voice channels, screen sharing

Tier 3 — Business Continuity

• Cisco Webex — enterprise backup, many large organizations maintain a Webex license specifically for Teams outages
• On-premise communication servers — some organizations maintain on-prem fallback (Mattermost, Rocket.Chat)

Best practice: Establish a "break-glass" communication channel on a non-Microsoft platform before an outage happens. When Teams goes down during a critical incident, the last thing you want is to be setting up alternative communication.

Security During Teams Outages

Protect Your Credentials

During Microsoft Teams outages, phishing attacks spike dramatically. Attackers send emails claiming "Microsoft Teams requires you to verify your account" with links to credential-harvesting pages.

Protection tips:

• Never click "reactivate your Teams account" links in email
• Always navigate to teams.microsoft.com directly
• Use a password manager like 1Password to auto-fill only on legitimate Microsoft domains
• Enable MFA on your Microsoft account (if your organization hasn't already enforced it)
• Report suspicious emails to your IT security team

Data Protection During Outages

• Don't share sensitive information over alternative platforms that haven't been approved by your organization's security team
• If you must use personal devices during an outage, don't download organizational files to them
• When Teams comes back, review your security settings — outages occasionally reset notification or privacy preferences
• Consider using Optery to reduce your personal data exposure, especially if your work email appears in breach databases

Teams vs. Competitors: Reliability Comparison

Platform	2025 SLA	Notable Outages	Avg Resolution	Architecture
Microsoft Teams	99.9%	6-8 major/year	2-4 hours	Azure (Microsoft 365 dependent)
Slack	99.99%	2-3 major/year	1-2 hours	AWS (independent)
Zoom	99.9%	1-2 major/year	1-3 hours	AWS + own data centers
Google Meet	99.9%	2-3 major/year	1-2 hours	Google Cloud (Workspace dependent)
Cisco Webex	99.9%	1-2 major/year	2-4 hours	Cisco data centers

Key takeaway: Teams' reliability is comparable to competitors, but its deep Microsoft 365 integration means it's affected by a broader range of infrastructure issues. Slack and Zoom have fewer dependencies, making their outages more predictable and isolated.

FAQ

Why does Teams work on my phone but not my computer? The Teams mobile app and desktop app use different authentication and caching mechanisms. The most common cause is a corrupted desktop cache — the fix is to clear the Teams cache (see instructions above). If the desktop app shows a white/blank screen after a Windows update, uninstall and reinstall Teams from Microsoft's website.

Why do I see "We're sorry — we've run into an issue" when signing in? This error typically means either Entra ID is having authentication issues (check if other Microsoft 365 services work) or your specific token has expired and can't refresh. Fix: sign out completely, clear browser cookies for microsoft.com and microsoftonline.com, close all browser tabs, and sign in again.

Can my IT admin see if Teams is down for our organization? Yes. The Microsoft 365 Admin Center (admin.microsoft.com > Health > Service health) shows real-time service status specific to your tenant. Admins can also check the Microsoft 365 Service Communications API for programmatic health data. However, this dashboard can lag 15-30 minutes behind actual outages — third-party monitoring tools like API Status Check often detect issues faster.

What's the difference between "degraded" and "down" for Teams? Microsoft uses "Advisory" for minor issues affecting <10% of users, "Incident" for significant disruptions, and "Service Degradation" for performance issues that don't prevent basic functionality. In practice, "degraded" usually means chat works but is slow, calls may drop, and meetings may have quality issues. "Down" means the service is completely unavailable.

Why do Teams notifications stop working randomly? Notification failures are typically caused by: Focus Assist / Do Not Disturb mode in Windows (check Settings > System > Focus), Teams notification settings reset after updates (Settings > Notifications in Teams), browser notification permissions revoked (for web app), or battery optimization killing the mobile app in the background (Android: Settings > Apps > Teams > Battery > Unrestricted).

Is Teams included in Microsoft's compensation policy for outages? Microsoft's SLA guarantees 99.9% monthly uptime for Teams. If uptime drops below 99.9%, enterprise customers can request service credits: 25% credit for <99.9%, 50% for <99%, 100% for <95%. Credits apply to the monthly subscription cost and must be requested within 60 days. Consumer/free accounts have no SLA.