Home / Microsoft status / Microsoft Teams outage

Microsoft Teams outage, 12-13 November 2026

Microsoft Teams is one of the Microsoft products hit by the Microsoft 365 outage that began on Thursday 12 November 2026 (Microsoft incident MO1550821). Microsoft's own words for Microsoft Teams: Most of the core functionality including joining calls, meetings, group chats, and channel messages are not impacted. Scenarios that depend on Exchange Online, including Calendar related failures with scheduling, invites, viewing, and meeting edits. Creation of Live or Virtual events fail. Failures with Copilot responses for outlook, calendar, or M365 files, read history, or adding to new chats. Navigating to App chats, adding new contacts or syncing contacts in settings fail. Standard channels are working fine but users may experience the inability to create or delete private or shared channels.

Updated Fri 13 Nov, 07:29 UTC. Part of our full write-up of the Microsoft 365 outage.

Right now_

··· Checking Microsoft Teams live... see the Microsoft Teams status page.

    What Microsoft says about Microsoft Teams

    Most of the core functionality including joining calls, meetings, group chats, and channel messages are not impacted. Scenarios that depend on Exchange Online, including Calendar related failures with scheduling, invites, viewing, and meeting edits. Creation of Live or Virtual events fail. Failures with Copilot responses for outlook, calendar, or M365 files, read history, or adding to new chats. Navigating to App chats, adding new contacts or syncing contacts in settings fail. Standard channels are working fine but users may experience the inability to create or delete private or shared channels.

    Microsoft 365 service health, Microsoft Teams, Fri 13 Nov, 07:29 UTC

    We're pursuing multiple workstreams to pinpoint the source of the issue and ensure the recovery of the affected environment. This issue impacts Outlook.com, OneDrive, OneNote, Microsoft To Do, Teams, and Microsoft 365 for the web although you may also see issues in other Microsoft 365 services.

    Microsoft's consumer status (personal accounts), which names Teams, Fri 13 Nov, 06:24 UTC

    Microsoft's overall status: "Users may be unable to connect to multiple Microsoft 365 services", rated service degradation. Features of the Microsoft 365 services below that interact with Exchange Online and email services are impacted. Elements of those services that do not depend on interaction with Exchange Online remain functional.

    What still works

    What you can do

    What caused it

    Microsoft has not published a root cause yet. In its updates it said a core process on the affected servers was overwhelmed, causing a loss of capacity; it later identified that process as the one handling secure connections, reverted a recent network configuration change and applied a patch to an upstream authentication and routing component. Its latest update: "We're seeing positive results for server stability after applying an upstream authentication/routing configuration component patch to a portion of our infrastructure." On security: "As of now, we are not aware of any malicious activity that is causing this incident." Microsoft has promised a post-incident report.

    Timeline

    Thu, Nov 12
    14:45 UTC
    9:45 a.m. ET

    An earlier, separate Teams incident (TM1550488) hits users in North and South America; Microsoft blames "resource contention" and resolves it at 15:53 UTC. It has not said whether it is linked.

    Thu, Nov 12
    17:39 UTC
    12:39 p.m. ET

    Outlook problem reports start climbing on Downdetector.

    Thu, Nov 12
    17:54 UTC
    12:54 p.m. ET

    Microsoft 365 Status first posts about problems accessing Exchange Online mailboxes through multiple connection methods in the Americas (incident EX1550543).

    Thu, Nov 12
    18:07 UTC
    1:07 p.m. ET

    Microsoft says users in any region may be affected.

    Thu, Nov 12
    18:26 UTC
    1:26 p.m. ET

    Microsoft opens the wider incident MO1550821: users may be unable to connect to multiple Microsoft 365 services.

    Thu, Nov 12
    18:27 UTC
    1:27 p.m. ET

    Over the next hour and a half Microsoft reports elevated load and servers becoming unexpectedly unavailable. It pauses deployments, restarts servers and bypasses a health check component.

    Thu, Nov 12
    22:03 UTC
    5:03 p.m. ET

    Microsoft says a core process on affected servers is becoming overwhelmed, causing capacity loss.

    Thu, Nov 12
    22:58 UTC
    5:58 p.m. ET

    Partial recovery: some servers are back and stable.

    Fri, Nov 13
    00:00 UTC
    7:00 p.m. ET

    Relapse: servers that came back become unresponsive again once they receive traffic.

    Fri, Nov 13
    01:12 UTC
    8:12 p.m. ET

    Microsoft identifies the overwhelmed process as the one handling secure connections and starts reverting a recent network configuration change.

    Fri, Nov 13
    01:48 UTC
    8:48 p.m. ET

    Microsoft reports positive results from server restarts.

    Fri, Nov 13
    02:58 UTC
    9:58 p.m. ET

    Microsoft says its changes are not taking as expected.

    Fri, Nov 13
    03:36 UTC
    10:36 p.m. ET

    Microsoft says there is no indication the outage is the result of malicious activity.

    Fri, Nov 13
    04:12 UTC
    11:12 p.m. ET

    A second partial recovery is not sustained.

    Fri, Nov 13
    04:56 UTC
    11:56 p.m. ET

    Microsoft describes a surge of calls from routing services to backend servers and scales up virtual machines.

    Fri, Nov 13
    06:24 UTC
    1:24 a.m. ET

    Microsoft's consumer status names Outlook.com, OneDrive, OneNote, Microsoft To Do, Teams and Microsoft 365 for the web as affected for personal accounts.

    Fri, Nov 13
    06:54 UTC
    1:54 a.m. ET

    Microsoft reports "marginal success".

    Fri, Nov 13
    07:29 UTC
    2:29 a.m. ET

    Latest update: positive results for server stability after an upstream authentication and routing configuration patch on part of the infrastructure, being extended to more servers. Not resolved, no time given for a fix.

    Other Microsoft products in this outage

    Live status for every Microsoft product: Is Microsoft down? · Is Microsoft Teams down?

    Questions

    Is Microsoft Teams down right now?

    The "Right now" card on this page reads the live status of Microsoft Teams from Microsoft's own service health page every minute. As of Fri 13 Nov, 07:29 UTC, Microsoft rated the incident "Service degradation" and said: Most of the core functionality including joining calls, meetings, group chats, and channel messages are not impacted. Scenarios that depend on Exchange Online, including Calendar related failures with scheduling, invites, viewing, and meeting edits. Creation of Live or Virtual events fail. Failures with Copilot responses for outlook, calendar, or M365 files, read history, or adding to new chats. Navigating to App chats, adding new contacts or syncing contacts in settings fail. Standard channels are working fine but users may experience the inability to create or delete private or shared channels.

    When will Microsoft Teams be fixed?

    Microsoft has not given a time for a full fix. Its latest update said it was seeing positive results for server stability after a patch to an authentication and routing component, and was extending that patch to more servers.

    Is the Microsoft Teams outage a cyberattack?

    Microsoft says: "As of now, we are not aware of any malicious activity that is causing this incident." It has promised a post-incident report with the root cause.

    Is it just me?

    No. This is a Microsoft-wide incident (MO1550821) affecting 22 Microsoft products, listed on this page. Changing settings, reinstalling apps or resetting your password will not fix it.

    Sources

    Is It Up or Down is independent and not affiliated with Microsoft. Microsoft, Outlook, Teams and the other product names are trademarks of Microsoft, used here only to identify the products.