Is Microsoft Teams down?

Understanding Microsoft Teams availability

Microsoft Teams can be partly available while a particular function is failing. The site may open even when sign-in, messaging, calls, meetings, notifications, or updates are affected. A blank page, failed connection, or repeated reconnecting can also come from the browser, Teams client, device, or network rather than a Microsoft-wide incident.

A broader Teams disruption is more likely when the same function fails for multiple users on different devices or networks. If the problem affects only one user, organization, team, meeting, or client, an account, permission, application, or local connectivity issue is more likely.

For Microsoft service-side information, check the Microsoft 365 service status portal.

Troubleshooting Microsoft Teams problems

Check for a wider Microsoft 365 incident

1. Open the Microsoft 365 service status portal.
2. Look for an incident affecting Teams or a related Microsoft 365 service.
3. Ask another Teams user, preferably on a different network or device, whether the same function is failing.

Matching failures across several users and networks are more consistent with a service-side incident. If Microsoft reports an incident, note the incident details and monitor the update rather than repeatedly changing local settings.

Compare the Teams client and device

If Teams fails on only one device:

• Try Teams in the browser if the desktop or mobile app fails, or try the app if the website fails.
• Restart the affected Teams client and device.
• Check whether every team and chat is affected or only one conversation, channel, meeting, or feature.
• Confirm that the device has internet access and that its date and time are correct.

A failure confined to one client or device is more likely to involve local application state, the browser, or the device than a general Teams outage.

Check browser-specific problems

If Teams works in the app but not in the browser, try a private window or another supported browser. Temporarily disable extensions that affect scripts, privacy, or sign-in, then reload Teams. If a private window works, stored site data or an extension is a likely cause.

Separate sign-in, account, and permission issues

If the Teams page loads but sign-in fails, confirm that you are using the intended work or school account and record the exact message shown. Compare sign-in in the web and installed versions. If the problem affects only one user, organization, team, meeting, or permission set, contact that organization’s Microsoft 365 administrator.

Test the network for reconnecting or slow loading

For slow loading, repeated reconnecting, or a connection that cannot be established, test another network. A different result on another connection points toward the original Wi-Fi, VPN, proxy, firewall, DNS, or network policy. If Teams fails on multiple devices and networks, check the official service status before changing network configuration.

When only calls, meetings, or messaging fail

If sign-in works but calls, meetings, or messages are affected, identify the exact function and test it in both the web and installed versions. Try another chat, team, or meeting where possible. A feature-specific or organization-specific problem does not necessarily mean that all of Microsoft Teams is unavailable.

Integrations and automation

If an external integration or automation fails while ordinary Teams access works, investigate that integration’s authentication, permissions, configuration, and own service status separately. If both the integration and Teams client fail across users and networks, check Microsoft’s service status first.