Microsoft 365 users in the Americas were unable to connect to their Exchange Online mailboxes on November 12, 2026, in an outage Microsoft is tracking in the Microsoft 365 admin center as EX1550543, with related information under MO1550821. A Microsoft service-health notice shared publicly by administrators listed the incident start time as 11:17 AM Eastern (8:17 AM Pacific). Microsoft posted publicly just before 1:00 PM Eastern that it was investigating reports of users experiencing issues accessing Exchange Online mailboxes through multiple connection methods in the Americas, and later confirmed the issue may affect Microsoft 365 service connectivity for users in any region.

Timeline: service-health notice start time 11:17 AM Eastern (8:17 AM Pacific), November 12, 2026, per the notice as reported from administrator copies. Downdetector reports spiked just after 12:00 PM Eastern; USA TODAY recorded 22,323 Microsoft 365 reports by 12:55 PM Eastern and just shy of 83,000 Outlook reports just before 1:00 PM Eastern. Microsoft's public investigating post followed just before 1:00 PM Eastern. Reuters recorded more than 130,000 Outlook reports at 1:27 PM Eastern, more than 46,000 Microsoft 365 reports, and about 3,000 Teams reports. In its 1:43 PM Eastern update, Microsoft said a portion of infrastructure is experiencing elevated load across multiple regions, which is likely contributing to the connectivity errors. Microsoft's next update was expected by 3:00 PM Eastern. No restoration had been posted in the sources read at verification time, 1:53 PM Eastern. Separately, earlier the same day, Microsoft posted at 10:40 AM Eastern about issues accessing or using Microsoft Teams functionality in North America and said in that thread that they were resolved around noon Eastern; that Teams item is a separate, already-resolved disruption, not this Exchange Online incident.

Affected services and regions: Exchange Online mailboxes, through Outlook on the web, Messaging API (MAPI), Exchange ActiveSync (EAS), and Representational State Transfer (REST) API, per Microsoft's own service-health wording. Initial scope was the Americas; Microsoft later said the issue may affect Microsoft 365 service connectivity for users in any region. Downdetector users also reported problems with Microsoft 365 generally, Copilot, and Teams; Microsoft has not confirmed those services as in scope for EX1550543, and they are recorded here as user reports only.

Provider's account: Microsoft said it identified connectivity errors occurring on a portion of Exchange Online infrastructure which receives and processes users' access requests, that it collected networking logs to investigate the source of the errors, that it is working to mitigate impact, and that a portion of infrastructure experiencing elevated load across multiple regions is likely contributing to the connectivity errors. No cause beyond that account has been disclosed. No compensation has been stated.

Status: Active at verification time, November 12, 2026, at 1:53 PM Eastern (6:53 PM UTC). Not yet restored in the sources read for this record.

Update, November 12, 2026, 2:23 PM Eastern: Microsoft said at 1:48 PM Eastern (10:48 AM Pacific) that it had begun redistributing connection traffic across its broader worldwide infrastructure to help balance the load. That mitigation step follows Microsoft's 1:43 PM Eastern update that a portion of infrastructure is experiencing elevated load across multiple regions, likely contributing to the connectivity errors. No restoration had been posted in the sources read at this verification time, 2:23 PM Eastern, and Microsoft's next update was still the one expected by 3:00 PM Eastern. No cause beyond Microsoft's account has been disclosed, and no compensation has been stated.

Timeline addition: 1:48 PM Eastern (10:48 AM Pacific), November 12, 2026: Microsoft: "We've begun redistributing connection traffic across our broader worldwide infrastructure to help balance the load."

Downstream effect, recorded as part of this Microsoft incident, not as separate board incidents: Anthropic's Claude status page opened an incident at 12:52 PM Eastern investigating elevated errors affecting its Microsoft 365 connector, and at 1:34 PM Eastern identified an issue with an upstream provider: mail, calendar and search tools failing for most requests, and new connections to the connector may not complete; Claude's API, Console, Code and other core components remained operational, with claude.ai and Claude Cowork listed as Partial Outage for the connector scope. OpenAI's status feed opened a matching incident at 1:29 PM Eastern investigating Microsoft connectors in ChatGPT (Connectors/Apps), where new connections may be broken and tools are not working as expected. Both are downstream effects of this Microsoft outage on connector tools only; neither provider's core service is down on its own account.

Status: Active at verification time, November 12, 2026, at 2:23 PM Eastern (7:23 PM UTC). Not yet restored in the sources read for this update.

Update, November 12, 2026, 2:53 PM Eastern: Microsoft's broader advisory for this incident (tracked under MO1550821 alongside EX1550543) lists the potentially impacted services as Exchange Online, Microsoft Teams, SharePoint Online, Microsoft Copilot 365 and Microsoft Defender XDR; the advisory text was relayed by TPx Communications at 1:48 PM Eastern and quoted in full by Engadget at 2:17 PM Eastern. "Potentially impacted" is Microsoft's own wording: Exchange Online mailbox access remains the confirmed failure, and the other four services are listed by Microsoft as potentially impacted, not confirmed down. In the same advisory Microsoft said it is restarting and repairing impacted portions of the infrastructure to restore capacity, reviewing an unexpected increase in a specific type of service traffic to determine whether it is contributing to the elevated load, and evaluating options to redirect traffic to alternate infrastructure to expedite relief. In a further social post reported by the Clarion Ledger, Microsoft said: "We're aggressively pursuing all pathways to reduce impact. We've paused all deployments, we're moving additional traffic off the affected infrastructure, and we're restarting affected servers to return them to service." TPx's relay put Microsoft's next update at about 12:30 PM Pacific (3:30 PM Eastern), superseding the 3:00 PM Eastern expectation in the earlier coverage. User reports were easing but still very high: Reuters' updated coverage recorded more than 97,000 Downdetector reports for Outlook at 2:07 PM Eastern, down from more than 130,000 at 1:27 PM Eastern, with more than 38,000 Microsoft 365 reports and about 4,500 Teams reports. No restoration had been posted in the sources read at this verification time, 2:53 PM Eastern. No cause beyond Microsoft's account has been disclosed, and no compensation has been stated.

Timeline additions: 1:48 PM Eastern (10:48 AM Pacific), November 12, 2026 — Microsoft advisory relayed by TPx Communications lists potentially impacted services (Exchange Online, Microsoft Teams, SharePoint Online, Microsoft Copilot 365, Microsoft Defender XDR) and states the restart-and-repair mitigation and the traffic-type review; next update expected about 12:30 PM Pacific (3:30 PM Eastern). 2:07 PM Eastern, November 12, 2026 — Downdetector Outlook reports at more than 97,000 per Reuters' updated coverage, down from the 1:27 PM Eastern peak above 130,000; reports easing is not a restoration, and Microsoft had posted no restoration at verification time.

Status: Active at verification time, November 12, 2026, at 2:53 PM Eastern (7:53 PM UTC). Not yet restored in the sources read for this update.

Update, November 12, 2026, 3:23 PM Eastern: Microsoft has revised its account of the cause. In an update quoted by the Detroit Free Press, Microsoft said: "We determined the elevated load isn't driven by an increase in traffic, but by a number of servers being unexpectedly unavailable; straining the remaining infrastructure. We're working to safely return them to service." That wording supersedes the earlier account in this record that Microsoft was reviewing an unexpected increase in a specific type of service traffic: on Microsoft's revised account, traffic did not increase; servers became unexpectedly (intermittently) unavailable, and the remaining infrastructure is carrying their load. TechProlonged, updated at 8:11 PM UTC (3:11 PM Eastern), records the same revision in Microsoft's update read at 2:31 PM Eastern, with engineers still bringing servers back into service and no time given for a fix and no cause named for why the servers dropped out. The Apex Wire, published at 3:01 PM Eastern, recorded that Microsoft said the problem was still being fixed as of 2:40 PM Eastern, with Downdetector Outlook reports at about 92,900 at 1:50 PM Eastern and Microsoft 365 reports at about 37,000 at that time. A relay of Microsoft's 2:40 PM Eastern update by Impress Computers put Microsoft's next update by 4:00 PM Central (5:00 PM Eastern). No restoration had been posted in the sources read at this verification time, 3:23 PM Eastern. No root cause beyond Microsoft's revised account has been disclosed, and no compensation has been stated.

Downstream effect, recorded as part of this Microsoft incident, not as a separate board incident: SparkPost opened an incident at 3:01 PM Eastern (8:01 PM UTC) reporting that since about 12:30 PM Eastern (17:30 UTC) Microsoft's mail servers have been answering a large share of external delivery attempts with temporary errors (including "451 4.7.0 Temporary server error"), affecting Outlook.com, Hotmail, Live, MSN and Office 365 recipients; affected messages are not lost and are queued for retry. This is a sender-side delivery effect of EX1550543, recorded here only.

Timeline additions: November 12, 2026, update read at 2:31 PM Eastern (11:31 AM Pacific) — Microsoft revises its diagnosis: the elevated load is not driven by an increase in traffic, but by a number of servers being unexpectedly unavailable, straining the remaining infrastructure; Microsoft is working to safely return them to service. 2:40 PM Eastern, November 12, 2026 — Microsoft still fixing the problem per The Apex Wire; a relay of that update put the next Microsoft update by 4:00 PM Central (5:00 PM Eastern).

Status: Active at verification time, November 12, 2026, at 3:23 PM Eastern (8:23 PM UTC). Not yet restored in the sources read for this update.

Sources (new for this update): Detroit Free Press, Outlook, Copilot are down. What Microsoft is saying, November 12, 2026, quoting Microsoft's revised-diagnosis post verbatim, TechProlonged, Outlook outage: Microsoft says servers are unexpectedly unavailable, published November 12, 2026 at 18:24 UTC, updated 20:11 UTC, The Apex Wire, Microsoft Outlook Down for 130,000 Users: What Caused the Outage, published November 12, 2026 at 20:01 UTC, Impress Computers, Microsoft Outlook / Exchange Online outage update, November 12, 2026, relaying Microsoft's 1:40 PM CST update and next update by 4:00 PM CST, Pingoru relay of SparkPost incident 12483246, Microsoft outage: delays delivering to Outlook, Hotmail and Office 365, identified November 12, 2026 at 20:01 UTC

Update, November 12, 2026, 3:53 PM Eastern: Microsoft has identified the mechanism behind the servers becoming unavailable. In its incident log entry at 2:43 PM Eastern (11:43 AM Pacific), Microsoft said the affected servers were failing automated health checks, and that this may be related to a recent change to a component involved in processing those checks. Microsoft is testing a configuration change to bypass the problematic component, reported as testing on a limited number of servers first, and is restarting all affected servers and watching them as they come back online. WOM Technology, current as of 3:15 PM Eastern, records that log entry and Microsoft's latest position at that time: testing a configuration change and restarting all affected servers, with the incident not declared resolved. TalkAndroid reports the same Microsoft account in its latest update: testing a configuration change to fix a problem that makes servers fail automated health checks and drop out of service, while restarting all affected servers. BallerAlert, published at 3:20 PM Eastern, records the same development at about 2:45 PM Eastern, with the configuration change tested on a limited number of servers to determine whether bypassing the problematic component could restore service. The Circuitry, reporting Microsoft's public status page at 3:30 PM Eastern, confirms Microsoft 365 business and enterprise services were still listed as degraded at that time, not restored. No restoration had been posted in the sources read at this verification time, 3:53 PM Eastern. No final root cause beyond this health-check mechanism has been disclosed, Microsoft has not attributed the outage to an attack, and no compensation has been stated.

Timeline additions: November 12, 2026, 2:43 PM Eastern (11:43 AM Pacific): Microsoft incident log: affected servers are failing automated health checks, possibly related to a recent change to a component involved in processing those checks; Microsoft is testing a configuration change to bypass the problematic component and restarting all affected servers. 3:30 PM Eastern, November 12, 2026: Microsoft's public status page still lists Microsoft 365 business and enterprise services as degraded per The Circuitry.

Status: Active at verification time, November 12, 2026, at 3:53 PM Eastern (8:53 PM UTC). Not yet restored in the sources read for this update.

Update, November 12, 2026, 4:23 PM Eastern: Microsoft reports progress, not restoration. In a public status update reported at 4:01 PM Eastern (9:01 PM UTC), Microsoft said it has validated an alternative service health check method, which allowed a subset of affected servers to successfully return to service, and that it is now applying this change more broadly. Microsoft is also preparing automated recovery systems to continually detect and restart unresponsive servers, to help maintain service stability as the change rolls out. iPhone in Canada, reporting that 4:01 PM Eastern update, records the same account and adds that Microsoft had not declared the incident resolved in that update, had provided no confirmed restoration time, and set its next update by 5:30 PM Eastern (10:30 PM UTC). Impress Computers, in an update timestamped 3:10 PM Central relaying Microsoft 365 Status (@MSFT365Status), records the identical Microsoft wording: a validated alternative health check method, a subset of servers returned to service, the change being applied more broadly, and automated recovery systems in preparation. No restoration had been posted in the sources read at this verification time, 4:23 PM Eastern. No final root cause beyond the health-check mechanism has been disclosed, Microsoft has not attributed the outage to an attack, and no compensation has been stated.

Timeline additions: November 12, 2026, 4:01 PM Eastern (1:01 PM Pacific): Microsoft public status update: an alternative service health check method has been validated and a subset of affected servers has returned to service; the change is being applied more broadly; automated recovery systems are being prepared to continually detect and restart unresponsive servers; next update expected by 5:30 PM Eastern.

Status: Active at verification time, November 12, 2026, at 4:23 PM Eastern (9:23 PM UTC). Progress reported; not yet restored in the sources read for this update.

Update, November 12, 2026, 5:23 PM Eastern: Microsoft is assessing a rollback of recent configuration updates as a possible way to speed recovery. In a public post at 4:40 PM Eastern (1:40 PM Pacific), Microsoft said: "We're actively restarting and validating the affected servers to return them to service. In parallel, we're assessing whether reverting a small number of recent configuration updates we identified could help accelerate recovery." USA TODAY's live coverage records that 4:40 PM Eastern post and Microsoft's fuller wording: "We're continuing to work through restarting and validating the affected servers to safely return them to service, and we're exploring opportunities to expedite this process." Interesting Engineering quotes the same Microsoft 365 Status post, including the configuration-revert assessment and the incident references EX1550543 and MO1550821. USA TODAY also records user reports easing: Downdetector showed about 49,000 Outlook reports at 4:50 PM Eastern and about 18,800 Microsoft 365 reports just before 5:00 PM Eastern, while Microsoft's service health page still listed multiple services, including Outlook, Teams, SharePoint, Copilot and Defender, as disrupted. This is a new mitigation avenue, not a restoration: Microsoft has not declared the incident resolved, has not attributed the outage to an attack, and no compensation has been stated. The next update previously expected by 5:30 PM Eastern had not been reported in the sources read at this verification time, 5:23 PM Eastern.

Timeline additions: November 12, 2026, 4:40 PM Eastern (1:40 PM Pacific) — Microsoft public post: it is actively restarting and validating the affected servers to return them to service, and in parallel assessing whether reverting a small number of recent configuration updates it identified could help accelerate recovery; more information under EX1550543 and MO1550821.

Status: Active at verification time, November 12, 2026, at 5:23 PM Eastern (10:23 PM UTC). Recovery work continuing; not yet restored in the sources read for this update.

Update, November 12, 2026, 5:53 PM Eastern: Microsoft says its recovery actions so far have not worked as expected, and it is testing a new recovery approach on an isolated portion of its infrastructure. In its 5:03 PM Eastern incident update, reported on X at 5:09 PM Eastern (2:09 PM Pacific) and on its public service health page at 5:11 PM Eastern (22:11 UTC), Microsoft said: "Our actions taken thus far have not provided the anticipated relief," and that it is "continuing to pursue all available pathways to restore service." Microsoft now says a core process on the affected servers is becoming overwhelmed, which makes the servers stop responding and contributes to the capacity loss. To test a possible fix, Microsoft is fully isolating a portion of its service infrastructure, restarting the affected components and gradually reintroducing traffic before applying the approach more broadly; it is also evaluating whether isolating traffic within each region would let affected regions recover independently. WebProNews, updated at 5:20 PM Eastern, records that 5:03 PM Eastern update and the 5:09 PM Eastern X post; On-Site Technology records the same account from Microsoft's public status page as of 5:11 PM Eastern; Technobezz, published at 22:16 UTC, records the same 22:11 UTC status page update verbatim. Microsoft also expanded the potentially impacted list: it now includes, in addition to Exchange Online, Microsoft Teams, SharePoint Online, Microsoft Copilot 365 and Microsoft Defender XDR, Microsoft Planner, Microsoft To Do, Microsoft Intune, Microsoft Defender for Office 365, several Microsoft Purview services, Power BI exports of sensitivity-labeled reports, and parts of the Microsoft 365 Apps admin center including Cloud Update, Cloud Policy and Inventory. "Potentially impacted" remains Microsoft's wording; Exchange Online mailbox access remains the confirmed failure. This supersedes the progress framing of the 4:01 PM Eastern update: a subset of servers had returned, but Microsoft's own latest account is that its actions have not provided the anticipated relief. Microsoft has not declared the incident resolved, has not named a final root cause, has not attributed the outage to an attack, and no compensation has been stated. Microsoft's next updates are due by 6:00 PM Eastern for EX1550543 and 6:30 PM Eastern for MO1550821.

Timeline additions: November 12, 2026, 5:03 PM Eastern (2:03 PM Pacific) — Microsoft incident update: actions taken thus far have not provided the anticipated relief; a core process on affected servers is becoming overwhelmed and making them stop responding; Microsoft is fully isolating a portion of its infrastructure, restarting affected components and gradually reintroducing traffic to test a recovery approach, and evaluating isolating traffic within each region for independent regional recovery; Microsoft 365 Apps admin center (Cloud Update, Cloud Policy, Inventory) added to the potentially impacted list, which also now includes Planner, To Do, Intune, Defender for Office 365, Purview services and Power BI exports; next updates due by 6:00 PM Eastern (EX1550543) and 6:30 PM Eastern (MO1550821). 5:09 PM Eastern — same update posted by Microsoft 365 Status (@MSFT365Status) on X. 5:11 PM Eastern (22:11 UTC) — Microsoft public service health page updated with the same account, still listing Microsoft 365 business and enterprise as a service degradation.

Status: Active at verification time, November 12, 2026, at 5:53 PM Eastern (10:53 PM UTC). No relief yet on Microsoft's own account; not restored in the sources read for this update.

Sources (new for this update): WebProNews, Microsoft 365 Outage Cuts Off Outlook for Hours; Microsoft Has Not Named a Root Cause, updated November 12, 2026 at 5:20 PM ET, On-Site Technology, Microsoft 365 and Outlook Outage, Nov 12, 2026: Timeline, updated November 12, 2026, status as of 5:11 PM ET, Technobezz, Microsoft 365 Outage Disrupts Teams, Exchange Online and Other Services, published November 12, 2026 at 22:16 UTC, reporting Microsoft's 22:11 UTC status page update

Update, November 12, 2026, 6:23 PM Eastern: Microsoft reports its first limited recovery, while the incident remains open. In its public service health update timestamped 6:06 PM Eastern (23:06 UTC), read live at 6:36 PM Eastern, Microsoft says a portion of the affected servers has been returned to service and is remaining stable so far, traffic and connections have been shifted to alternative pathways wherever possible, and limited recovery has been observed in some regions. Microsoft says it has streamlined its recovery process to return the remaining affected servers faster, and is implementing protective traffic management measures in a specific location to reduce load on the affected infrastructure, expanding those measures to additional locations if results are positive. As capacity is restored, users may experience a gradual recovery as their clients reconnect. This reverses the direction of the 5:03 PM Eastern update, in which Microsoft said its actions had not provided the anticipated relief; it is progress, not a restoration. The potentially impacted list now also includes Universal Print, where users may encounter errors submitting print jobs or using admin features; the rest of the list is unchanged: Exchange Online, Microsoft Teams, SharePoint Online, Microsoft Copilot 365, Microsoft Defender XDR, Planner, To Do, Intune, Defender for Office 365, Purview services, Power BI exports and parts of the Microsoft 365 Apps admin center. "Potentially impacted" remains Microsoft's wording; Exchange Online mailbox access remains the confirmed failure. Impress Computers republishes the same 6:06 PM Eastern Microsoft wording verbatim, including the limited-recovery and protective-traffic-management account, and a Pingoru relay of a provider notice (BitbyBit, 5:35 PM Eastern update, identified 23:00 UTC) likewise records that a portion of affected servers has returned and service is improving for many users, with no estimated resolution time. Microsoft's public page lists Azure separately as having no issues detected at this time. Microsoft has not declared the incident resolved, has not named a final root cause beyond the health-check / overwhelmed core process account, has not attributed the outage to an attack, and no compensation has been stated. Microsoft's next update is due by 7:30 PM Eastern.

Timeline additions: November 12, 2026, 6:06 PM Eastern (3:06 PM Pacific, 23:06 UTC) — Microsoft public service health update: a portion of affected servers returned to service and remaining stable; traffic and connections shifted to alternative pathways; limited recovery observed in some regions; recovery process streamlined; protective traffic management measures being implemented in a specific location, to expand if results are positive; gradual recovery expected as clients reconnect; Universal Print now on the potentially impacted list; next update due by 7:30 PM Eastern. Incident remains a service degradation, not restored.

Status: Active at verification time, November 12, 2026, at 6:36 PM Eastern (11:36 PM UTC). Limited recovery in some regions on Microsoft's own account; not restored.

Sources (new for this update): Microsoft Service Health Status, status.cloud.microsoft, last updated November 12, 2026 at 23:06 UTC, read live 6:24-6:37 PM ET, Impress Computers, Microsoft Outlook / Exchange Online outage update, November 12, 2026, republishing Microsoft's 6:06 PM ET update, Pingoru relay of BitbyBit notice, Microsoft Exchange Outage, 5:35 PM ET update identified November 12, 2026 at 23:00 UTC, FirstCall LLC status, Microsoft 365 Suite outage notice listing Universal Print among potentially impacted services, last update November 12, 2026 at 22:53 UTC

Update, November 12, 2026, 7:53 PM Eastern: Microsoft reports a setback in recovery, and then a revised, wider list of potentially impacted services, while the incident remains open. In its update timestamped 6:59 PM Eastern (11:59 PM UTC), posted on X at 7:06 PM Eastern, Microsoft says the servers it has returned to service at first stay healthy, but can stop responding again once they start receiving traffic. Engineers are studying diagnostic data from those servers with networking and platform specialists to find what triggers that behavior. Building on the protective traffic management already in place, Microsoft is temporarily limiting which types of traffic can reach the affected infrastructure in specific locations, to test whether a particular kind of request is contributing and to restore service step by step. In parallel, it is rebuilding a subset of the affected servers on a previous software configuration, to test whether that keeps them responsive, and will extend that approach if it works. That reverses, in part, the limited-recovery direction of the 6:06 PM Eastern update. In its next public update, timestamped 7:56 PM Eastern (12:56 AM UTC on November 13), read live at 7:58 to 8:01 PM Eastern, Microsoft says it has reviewed known impact scenarios and revised the list of impacted services and features, and is continuing work to isolate the issue affecting server availability, alongside other workstreams. The revised list names 19 services. Newly named since the 6:23 PM Eastern board update are: the Microsoft 365 admin center (some pages may not load), Microsoft 365 apps (recently used files may not display), Microsoft 365 Education (Assignments, Reading Progress and Speaker Progress), Microsoft Fabric (failures exporting reports carrying sensitivity labels, and updating labelled artifacts), Microsoft Graph (API requests reaching Exchange Online mail, calendar and contacts data may time out), and Windows 365 (customers whose Cloud PCs are configured to use Microsoft Purview Customer Key may be unable to connect to those Cloud PCs). The list otherwise stands as before: Exchange Online, Microsoft Teams, SharePoint Online, Microsoft Copilot 365, Microsoft Defender XDR, Planner, To Do, Intune, Defender for Office 365, Purview services, Power BI exports, parts of the Microsoft 365 Apps admin center and Universal Print. Microsoft's revised wording also clarifies that Teams and SharePoint features that depend on Exchange Online are the affected parts, with core Teams messaging and meetings largely functional and direct access to SharePoint files functional, and that Exchange Online email delivery may be delayed. "Potentially impacted" remains Microsoft's wording; Exchange Online mailbox access remains the confirmed failure. WebProNews, updated 7:15 PM Eastern, reports the same 6:59 PM Eastern Microsoft account, including the unresponsive-again behavior, the traffic-type limits, the rebuild on a previous configuration and the Windows 365 addition, and Back End News, published 12:48 AM UTC on November 13, reports the same account in its own coverage. Microsoft's public page lists Azure separately as having no issues detected at this time, and also lists Microsoft 365 for consumers as a service degradation. Microsoft has not declared the incident resolved, has not named a final root cause, has not attributed the outage to an attack, and no compensation has been stated. Microsoft's public page gives its next update by 8:30 PM Eastern; WebProNews gives the Exchange incident's next update by 8:00 PM Eastern.

Timeline additions: November 12, 2026, 6:59 PM Eastern (3:59 PM Pacific, 11:59 PM UTC) — Microsoft update: servers returned to service can become unresponsive again once they begin receiving traffic; diagnostic data being analyzed with networking and platform experts; traffic types temporarily limited in specific locations; a subset of servers being rebuilt on a previous software configuration, to expand if results are positive; Windows 365 Cloud PCs configured with Purview Customer Key now on the potentially impacted list; next Exchange update due by 8:00 PM Eastern on WebProNews' account. November 12, 2026, 7:56 PM Eastern (4:56 PM Pacific, 12:56 AM UTC on November 13) — Microsoft public service health update: known impact scenarios reviewed and the impacted-services list revised to 19 services, now also naming the Microsoft 365 admin center, Microsoft 365 apps, Microsoft 365 Education, Microsoft Fabric and Microsoft Graph; work continuing to isolate the server-availability issue; next update due by 8:30 PM Eastern (1:30 AM UTC). Incident remains a service degradation, not restored.

Status: Active at verification time, November 12, 2026, at 8:01 PM Eastern (1:01 AM UTC on November 13). No restoration posted; recovery has suffered a setback on Microsoft's own account.

Sources (new for this update): Microsoft Service Health Status, status.cloud.microsoft, last updated November 13, 2026 at 12:56 UTC, read live 7:58-8:01 PM ET, WebProNews, Microsoft 365 Outage Cuts Off Outlook for Hours, updated November 12, 2026 at 7:15 PM ET, Back End News, Microsoft 365 outage disrupts Outlook and other work apps, published November 13, 2026 at 12:48 AM UTC, Arbora IT, Outlook and M365 Outage Nov 2026, 7:10 PM ET update republishing Microsoft's update, November 12, 2026, PulsAPI, Microsoft Teams status, checked November 13, 2026 at 12:12 AM UTC

Sources: Reuters, Microsoft 365, Outlook down for thousands of US users, Downdetector shows, November 12, 2026, USA TODAY, Thousands of users reporting issues with Microsoft Outlook, 365, November 12, 2026, WCIA / Nexstar, Is Microsoft Outlook down? Company confirms issues with email accounts, November 12, 2026, Arbora Managed IT, Outlook and M365 Outage Nov 2026, quoting Microsoft's EX1550543 / MO1550821 updates, Swikblog, Microsoft Outlook Outage, reporting the EX1550543 service-health notice and its 11:17 AM start time, USA TODAY, Microsoft outage: live updates, November 12, 2026, TechCrunch, Microsoft's Outlook email hit by new outage, November 12, 2026, Fox 49 / Associated Press syndication, Thousands of Microsoft 365 users report email access problems, updated November 12, 2026, Claude Status, Elevated errors affecting the Microsoft 365 connector, November 12, 2026, Pingoru mirror of OpenAI's official status feed, Elevated errors affecting the Microsoft 365 connector, November 12, 2026, Engadget, Multiple Microsoft 365 services are experiencing an outage, published November 12, 2026 at 2:17 PM ET, quoting Microsoft's status update in full, Pingoru relay of the Microsoft notice via TPx Communications, Microsoft 365 Business and Enterprise outage, identified November 12, 2026 at 18:48 UTC, Clarion Ledger, No email? Thousands across US report Outlook, Microsoft is down, November 12, 2026, quoting Microsoft's paused-deployments post, Reuters, Microsoft 365, Outlook down for thousands of US users, Downdetector shows, November 12, 2026, updated coverage with the 2:07 PM ET Downdetector figures, as syndicated, Gadget Review, Microsoft Outlook hit by global outage, published November 12, 2026 at 2:37 PM ET, Detroit Free Press, Outlook, Copilot are down. What Microsoft is saying, November 12, 2026, TechProlonged, Outlook outage: Microsoft says servers are unexpectedly unavailable, November 12, 2026, The Apex Wire, Microsoft Outlook Down for 130,000 Users, November 12, 2026, Impress Computers, Microsoft Outlook / Exchange Online outage update, November 12, 2026, Pingoru relay of SparkPost incident 12483246, November 12, 2026, WOM Technology, Outlook Outage Nov. 12, 2026, current as of 3:15 PM Eastern, November 12, 2026, TalkAndroid, Microsoft Outlook Outage: Exchange Online Down Worldwide, November 12, 2026, BallerAlert, Microsoft Outlook Outage Disrupts Email, Teams and 365 Nationwide, published November 12, 2026 at 3:20 PM Eastern, The Circuitry, Microsoft 365 is degraded after servers went offline, November 12, 2026, iPhone in Canada, Microsoft 365 Outage Hits Outlook and Teams as Servers Go Offline, November 12, 2026, Impress Computers, Microsoft Outage: Exchange Online Users Report Mailbox Connection Failures, updated November 12, 2026, USA TODAY, Microsoft outage: Live updates as mass issues reported with Outlook, 365, November 12, 2026, Interesting Engineering, Microsoft outage affects 130,000 users as server failures spread, November 12, 2026, WebProNews, Microsoft 365 Outage Cuts Off Outlook for Hours, updated November 12, 2026 at 5:20 PM ET, On-Site Technology, Microsoft 365 and Outlook Outage Nov 12 2026 Timeline, status as of 5:11 PM ET, Technobezz, Microsoft 365 Outage Disrupts Teams, Exchange Online and Other Services, published November 12, 2026 at 22:16 UTC, Microsoft Service Health Status, status.cloud.microsoft, last updated November 12, 2026 at 23:06 UTC, Impress Computers, Microsoft Outlook / Exchange Online outage update, November 12, 2026, Pingoru relay of BitbyBit notice, Microsoft Exchange Outage, November 12, 2026, FirstCall LLC status, Microsoft 365 Suite outage notice, November 12, 2026

Update append for /outages/microsoft-exchange-online-outage-november-12-2026 — 2026-11-12 8:23 PM ET sweep

Append to the live incident page (corrections/updates are appended, never silently edited in, per board method).

House style: date on the page remains 12-11-2026 12:00, taxonomy Outages. This is an UPDATE to the active incident, not a new page.

Apply AFTER bundle 2026-11-12-1953.

Update, November 12, 2026, 8:23 PM Eastern: Microsoft remains in service degradation with no restoration, and its 8:06 PM Eastern update (1:06 AM UTC on November 13, read live 8:24-8:30 PM Eastern) narrows the mechanism and adds two parallel recovery actions. Microsoft says its investigation found that a process on the affected servers responsible for establishing secure connections becomes overwhelmed, causing the servers to stop processing requests. It is preparing a configuration change intended to address that behavior across all affected servers, validating it first on a subset of servers before applying it more broadly alongside restarts of the affected infrastructure. In parallel, it has begun reverting a recent network configuration change that correlates with the start of impact, and is monitoring whether that contributes to recovery. The temporary traffic limitations described in the 6:59 PM Eastern update are now in effect in specific locations; Microsoft is monitoring whether servers there remain stable while handling a narrower set of connections, after which it will gradually reintroduce additional traffic. The potentially impacted list remains 19 services, unchanged from the 7:56 PM Eastern revision. Microsoft's public page continues to list Microsoft 365 (Business or Enterprise) and Microsoft consumer products as service degradation, and Azure as having no issues detected. The consumer incident was last updated 7:36 PM Eastern, with its next update by 11:30 PM Eastern. Tx Cyber Net's Outage Watch, which mirrors provider status feeds, shows the same Microsoft update timestamped 7:06 PM Central (8:06 PM Eastern) with the same secure-connection process finding, confirming the update independently of the live page read. Microsoft has not declared the incident resolved, has not stated compensation, and its next Business/Enterprise update is now due by 9:00 PM Eastern (2:00 AM UTC), later than the 8:30 PM Eastern time in effect at the last check. As of the 8:29 PM Eastern check, Microsoft's @MSFT365Status thread on X had posted the 7:56 PM Eastern revision (about 8:02-8:03 PM Eastern) but had not yet posted the 8:06 PM Eastern current-status text.

Timeline additions: November 12, 2026, 8:06 PM Eastern (5:06 PM Pacific, 1:06 AM UTC on November 13) — Microsoft public service health update: a process responsible for establishing secure connections becomes overwhelmed and servers stop processing requests; a configuration change to address that behavior is being prepared and validated on a subset of servers before broader rollout alongside restarts; a recent network configuration change correlating with the start of impact is being reverted in parallel; temporary traffic limitations are now in effect in specific locations, with stability monitoring before gradual traffic reintroduction; potentially impacted list remains 19 services; next update due by 9:00 PM Eastern (2:00 AM UTC). Incident remains a service degradation, not restored.

Status: Active at verification time, November 12, 2026, at 8:30 PM Eastern (1:30 AM UTC on November 13). No restoration posted.

Sources (new for this update): Microsoft Service Health Status, status.cloud.microsoft, last updated November 13, 2026 at 1:06 AM UTC, read live 8:24-8:30 PM ET, Tx Cyber Net, Outage Watch, Microsoft 365 last update 7:06 PM CT November 12, 2026, Microsoft 365 Status on X, thread for EX1550543, checked 8:27-8:29 PM ET

Update append for /outages/microsoft-exchange-online-outage-november-12-2026 — 2026-11-12 8:53 PM ET sweep

Append to the live incident page (corrections/updates are appended, never silently edited in, per board method).

House style: date on the page remains 12-11-2026 12:00, taxonomy Outages. This is an UPDATE to the active incident, not a new page.

Apply AFTER bundle 2026-11-12-2023.

Update, November 12, 2026, 8:53 PM Eastern: Microsoft remains in service degradation with no restoration, and its 8:50 PM Eastern update (1:50 AM UTC on November 13, read live 8:54-8:58 PM Eastern) reports the first positive restart results of the evening. Microsoft says it is seeing positive results with its efforts to restart affected infrastructure, it is actively monitoring the performance of the restarted infrastructure to verify stability, which will support improved availability, and remediation actions will be expanded as it confirms stability with the changes applied. The potentially impacted list remains 19 services, unchanged from the 7:56 PM Eastern revision. Microsoft's public page continues to list Microsoft 365 (Business or Enterprise) and Microsoft consumer products as service degradation, and Azure as having no issues detected; the separate Azure status page likewise shows no active events. The consumer incident was last updated 7:36 PM Eastern, with its next update by 11:30 PM Eastern. What Is Down, which mirrors provider status feeds, shows the same Microsoft current status verbatim in a crawl at 1:59 AM UTC (8:59 PM Eastern), including the same next-update time, confirming the update independently of the live page read; Mashable's live coverage (latest update 8:07 PM Eastern) likewise confirms Outlook, SharePoint Online, Teams, Copilot and Microsoft 365 continuing to have issues, with Azure operational. Microsoft has not declared the incident resolved, has not stated compensation, and its next Business/Enterprise update is now due by 10:00 PM Eastern (3:00 AM UTC), superseding the 9:00 PM Eastern time in effect at the last check.

Timeline additions: November 12, 2026, 8:50 PM Eastern (5:50 PM Pacific, 1:50 AM UTC on November 13) — Microsoft public service health update: positive results seen from efforts to restart affected infrastructure; performance of the restarted infrastructure being actively monitored to verify stability, which will support improved availability; remediation actions will be expanded as stability with the changes applied is confirmed; potentially impacted list remains 19 services; next update due by 10:00 PM Eastern (3:00 AM UTC). Incident remains a service degradation, not restored.

Status: Active at verification time, November 12, 2026, at 8:58 PM Eastern (1:58 AM UTC on November 13). No restoration posted.

Sources (new for this update): Microsoft Service Health Status, status.cloud.microsoft/m365, last updated November 13, 2026 at 1:50 AM UTC, read live 8:54-8:58 PM ET, Azure Status, azure.status.microsoft, no active events, read live about 8:56 PM ET, What Is Down, Microsoft 365 incident mirror, crawled November 13, 2026 at 1:59 AM UTC, Mashable, Microsoft outage: Microsoft 365, Teams, Outlook, Copilot all impacted, latest update November 12, 2026 at 8:07 PM ET

Update append for /outages/microsoft-exchange-online-outage-november-12-2026 — 2026-11-12 9:23 PM ET sweep

Append to the live incident page (corrections/updates are appended, never silently edited in, per board method).

House style: date on the page remains 12-11-2026 12:00, taxonomy Outages. This is an UPDATE to the active incident, not a new page.

Apply AFTER bundle 2026-11-12-2053.

Update, November 12, 2026, 9:23 PM Eastern: Microsoft remains in service degradation with no restoration, and its 9:14 PM Eastern update (2:14 AM UTC on November 13, read live 9:23-9:26 PM Eastern) moves the recovery account from restart results to capacity work. In paraphrase, Microsoft says it is applying infrastructure capacity improvements where possible to help support traffic in regions coming online, and that it is continuing to monitor the results of the changes applied so it can identify strategic actions that can help improve service health across all affected regions. The potentially impacted list remains 19 services, unchanged: Exchange Online, Microsoft 365 admin center, Microsoft 365 apps, Microsoft 365 Apps Admin Center, Microsoft 365 Education, Microsoft Copilot 365, Microsoft Defender for Office 365, Microsoft Defender XDR, Microsoft Fabric, Microsoft Graph, Microsoft Intune, Microsoft Planner, Microsoft Purview, Microsoft Teams, Microsoft To Do, Power BI, SharePoint Online, Universal Print, and Windows 365. Microsoft's public page continues to list Microsoft 365 (Business or Enterprise) and Microsoft consumer products as service degradation, with user impact stated as users may be unable to connect to multiple Microsoft 365 services, and Azure as having no issues detected. UptimeRobot's incident record for November 12 (sourced from IsDown) lists the Microsoft 365 outage as ongoing with no resolution posted, corroborating the still-active status; its latest cited Microsoft updates are the 8:45 and 8:48 PM Eastern restart items, so it does not yet reflect the 9:14 PM Eastern capacity wording, and that lag is stated here openly. Microsoft has not declared the incident resolved and has not stated compensation, and its next update remains due by 10:00 PM Eastern (3:00 AM UTC), the same deadline as at the last check.

Timeline additions: November 12, 2026, 9:14 PM Eastern (6:14 PM Pacific, 2:14 AM UTC on November 13) — Microsoft public service health update: infrastructure capacity improvements being applied where possible to help support traffic in regions coming online; results of changes applied continue to be monitored to identify strategic actions that can help improve service health across all affected regions; potentially impacted list remains 19 services; next update due by 10:00 PM Eastern (3:00 AM UTC). Incident remains a service degradation, not restored.

Status: Active at verification time, November 12, 2026, at 9:26 PM Eastern (2:26 AM UTC on November 13). No restoration posted.

Sources (new for this update): Microsoft Service Health Status, status.cloud.microsoft/m365, last updated November 13, 2026 at 2:14 AM UTC, read live 9:23-9:26 PM ET, UptimeRobot (IsDown), Microsoft 365 outage on 2026-11-12, incident ongoing, naming MO1550821

Update append for /outages/microsoft-exchange-online-outage-november-12-2026 — 2026-11-12 10:23 PM ET sweep

Append to the live incident page (corrections/updates are appended, never silently edited in, per board method).

House style: date on the page remains 12-11-2026 12:00, taxonomy Outages. This is an UPDATE to the active incident, not a new page.

Apply AFTER bundle 2026-11-12-2123 (which was APPLIED LIVE by Sam per the outage-watch log).

Update, November 12, 2026, 10:23 PM Eastern: Microsoft remains in service degradation with no restoration, and its 10:07 PM Eastern update (3:07 AM UTC on November 13, read live 10:24-10:25 PM Eastern) reports a setback in the capacity work described at 9:14 PM Eastern. In paraphrase, Microsoft says it monitored the changes applied to improve serviceability and confirmed that a change is not taking as expected, and that it is now identifying alternate workstreams that can be applied to increase capacity in the face of sustained traffic management imbalances. The scope remains users attempting to access affected Microsoft 365 services from multiple regions globally. The potentially impacted list remains 19 services, unchanged: Exchange Online, Microsoft 365 admin center, Microsoft 365 apps, Microsoft 365 Apps Admin Center, Microsoft 365 Education, Microsoft Copilot 365, Microsoft Defender for Office 365, Microsoft Defender XDR, Microsoft Fabric, Microsoft Graph, Microsoft Intune, Microsoft Planner, Microsoft Purview, Microsoft Teams, Microsoft To Do, Power BI, SharePoint Online, Universal Print, and Windows 365. Microsoft's public page continues to list Microsoft 365 (Business or Enterprise) and Microsoft consumer products as service degradation, with the headline that users may be unable to connect to multiple Microsoft 365 services, and Azure as having no issues detected, with no active Azure events. Downdetector for Microsoft 365, read at 10:25 PM Eastern, still showed user reports indicating problems, with Exchange the most reported problem and user comments at 10:17-10:23 PM Eastern still reporting being offline or unable to load services, corroborating the still-active status; Downdetector is a user-report source and does not mirror Microsoft's 10:07 PM Eastern wording, and that distinction is stated here openly. Microsoft has not declared the incident resolved and has not stated compensation, and its next update is now due by 10:30 PM Eastern (3:30 AM UTC).

Timeline additions: November 12, 2026, 10:07 PM Eastern (7:07 PM Pacific, 3:07 AM UTC on November 13) — Microsoft public service health update: changes applied to improve serviceability monitored and confirmed not taking as expected; alternate workstreams being identified to increase capacity amid sustained traffic management imbalances; potentially impacted list remains 19 services; next update due by 10:30 PM Eastern (3:30 AM UTC). Incident remains a service degradation, not restored.

Status: Active at verification time, November 12, 2026, at 10:25 PM Eastern (3:25 AM UTC on November 13). No restoration posted.

Sources (new for this update): Microsoft Service Health Status, status.cloud.microsoft/m365, last updated November 13, 2026 at 3:07 AM UTC, read live 10:24-10:25 PM ET, Azure Status, azure.status.microsoft, no active events, read live 10:25 PM ET, Downdetector, Microsoft 365 status, user reports show problems, read 10:25 PM ET

Update append for /outages/microsoft-exchange-online-outage-november-12-2026 — 2026-11-12 10:53 PM ET sweep

Append to the live incident page (corrections/updates are appended, never silently edited in, per board method).

House style: date on the page remains 12-11-2026 12:00, taxonomy Outages. This is an UPDATE to the active incident, not a new page.

Apply AFTER bundle 2026-11-12-2223 (which was APPLIED LIVE by Sam per the outage-watch log).

Update, November 12, 2026, 10:53 PM Eastern: Microsoft remains in service degradation with no restoration, and its 10:37 PM Eastern update (3:37 AM UTC on November 13, read live 10:53-10:56 PM Eastern) shifts the investigation from the failed capacity change described at 10:07 PM Eastern to traffic-flow and routing review. In paraphrase, Microsoft says that as part of its investigation into the sustained traffic management imbalances, it is reviewing traffic flows and the affected infrastructure to identify opportunities to optimize routing, including verifying the reasons for service failures so it can develop specific actions to improve stability. The scope remains users attempting to access affected Microsoft 365 services. The potentially impacted list remains 19 services, unchanged: Exchange Online, Microsoft 365 admin center, Microsoft 365 apps, Microsoft 365 Apps Admin Center, Microsoft 365 Education, Microsoft Copilot 365, Microsoft Defender for Office 365, Microsoft Defender XDR, Microsoft Fabric, Microsoft Graph, Microsoft Intune, Microsoft Planner, Microsoft Purview, Microsoft Teams, Microsoft To Do, Power BI, SharePoint Online, Universal Print, and Windows 365. Microsoft's public page continues to list Microsoft 365 and Microsoft consumer products as service degradation, with the headline that users may be unable to connect to multiple Microsoft 365 services, and Azure as having no issues detected at this time. Downdetector for Microsoft 365, read at about 10:55 PM Eastern, still showed user reports indicating problems, with Exchange the most reported problem at 64 percent and user comments at 10:45-10:54 PM Eastern still reporting services not working, corroborating the still-active status; Downdetector is a user-report source and does not mirror Microsoft's 10:37 PM Eastern wording, and that distinction is stated here openly. Microsoft has not declared the incident resolved and has not stated compensation, and its next update is now due by 11:30 PM Eastern (4:30 AM UTC).

Timeline additions: November 12, 2026, 10:37 PM Eastern (7:37 PM Pacific, 3:37 AM UTC on November 13) — Microsoft public service health update: traffic flows and affected infrastructure being reviewed to identify opportunities to optimize routing as part of the investigation into sustained traffic management imbalances; reasons for service failures being verified to develop specific stability actions; potentially impacted list remains 19 services; next update due by 11:30 PM Eastern (4:30 AM UTC). Incident remains a service degradation, not restored.

Status: Active at verification time, November 12, 2026, at 10:56 PM Eastern (3:56 AM UTC on November 13). No restoration posted.

Sources (new for this update): Microsoft Service Health Status, status.cloud.microsoft/m365, last updated November 13, 2026 at 3:37 AM UTC, read live 10:53-10:56 PM ET, Downdetector, Microsoft 365 status, user reports show problems, read about 10:55 PM ET, Storyboard18, Microsoft 365 outage disrupts Outlook access across multiple regions, published November 13, 2026 at 10:45 PM ET, summarizing earlier Microsoft updates and still-active impact

Update append for /outages/microsoft-exchange-online-outage-november-12-2026 — 2026-11-12 11:23 PM ET sweep

Append to the live incident page (corrections/updates are appended, never silently edited in, per board method).

House style: date on the page remains 12-11-2026 12:00, taxonomy Outages. This is an UPDATE to the active incident, not a new page.

Apply AFTER bundle 2026-11-12-2253 (which was APPLIED LIVE by Sam per the outage-watch log).

Update, November 12, 2026, 11:23 PM Eastern: Microsoft remains in service degradation with no restoration, and its 11:22 PM Eastern update (4:22 AM UTC on November 13, read live 11:24-11:25 PM Eastern) reports partial recovery that is not sustained. In paraphrase, Microsoft says it is continuing work to improve server stability and traffic flow, including adjusting traffic protocols, redistributing traffic, and applying strategic traffic blocking measures; it is observing partial recovery in regions where those adjustments have been applied, but those actions are not resulting in sustained recovery, so it is reviewing what additional actions it can take to improve overall infrastructure stability. The scope remains users attempting to access affected Microsoft 365 services. The potentially impacted list remains 19 services, unchanged: Exchange Online, Microsoft 365 admin center, Microsoft 365 apps, Microsoft 365 Apps Admin Center, Microsoft 365 Education, Microsoft Copilot 365, Microsoft Defender for Office 365, Microsoft Defender XDR, Microsoft Fabric, Microsoft Graph, Microsoft Intune, Microsoft Planner, Microsoft Purview, Microsoft Teams, Microsoft To Do, Power BI, SharePoint Online, Universal Print, and Windows 365. Microsoft's public page continues to list Microsoft 365 and Microsoft consumer products as service degradation, with the headline that users may be unable to connect to multiple Microsoft 365 services, and Azure as having no issues detected at this time, with no active Azure events on the Azure status page. Downdetector for Microsoft 365, read at about 11:24-11:25 PM Eastern, still showed user reports indicating problems, with a chart peak of 45,864 reports in the last 24 hours, Exchange the most reported problem at 64 percent, and user comments at 11:17 PM Eastern still reporting service down in California and at 11:21 PM Eastern reporting some services coming back, corroborating still-active impact with mixed recovery signs; Downdetector is a user-report source and does not mirror Microsoft's 11:22 PM Eastern wording, and that distinction is stated here openly. Microsoft has not declared the incident resolved and has not stated compensation, and its next update is now due by 12:00 AM Eastern on November 13 (5:00 AM UTC).

Timeline additions: November 12, 2026, 11:22 PM Eastern (8:22 PM Pacific, 4:22 AM UTC on November 13) — Microsoft public service health update: work continuing to improve server stability and traffic flow, including adjusting traffic protocols, redistributing traffic and applying strategic traffic blocking; partial recovery observed in regions where adjustments were applied, but not sustained recovery; additional actions being reviewed to improve overall infrastructure stability; potentially impacted list remains 19 services; next update due by 12:00 AM Eastern on November 13 (5:00 AM UTC). Incident remains a service degradation, not restored.

Status: Active at verification time, November 12, 2026, at 11:25 PM Eastern (4:25 AM UTC on November 13). No restoration posted.

Sources (new for this update): Microsoft Service Health Status, status.cloud.microsoft/m365, last updated November 13, 2026 at 4:22 AM UTC, read live 11:24 PM ET, Azure Status, azure.status.microsoft, no active events, read live about 11:25 PM ET, Downdetector, Microsoft 365 status, user reports show problems, read about 11:24-11:25 PM ET

Update, November 13, 2026, 12:23 AM Eastern: Microsoft remains in service degradation with no restoration, and its 11:57 PM Eastern update on November 12 (4:57 AM UTC on November 13, read live 12:24-12:26 AM Eastern) identifies a new traffic problem created in part by its own rebalancing. In paraphrase, Microsoft says that as mitigation actions were applied it observed a surge in outbound call volume from its routing services toward its backend servers, because the backend outbound service cannot properly route to the backend machines, and that heightened volume is continuing in connection with traffic rebalancing taken throughout the event. It says it is working on multiple workstreams to pinpoint the underlying cause of that traffic influx, is scaling up virtual machines to increase capacity and reduce load, and is querying for machines in a bad state to force a sync of its recent network change, which may improve availability, but machines stuck in a bad state are preventing those changes from syncing as expected. It will continue monitoring the effectiveness of changes applied. The scope remains users attempting to access affected Microsoft 365 services. The potentially impacted list remains 19 services, unchanged: Exchange Online, Microsoft 365 admin center, Microsoft 365 apps, Microsoft 365 Apps Admin Center, Microsoft 365 Education, Microsoft Copilot 365, Microsoft Defender for Office 365, Microsoft Defender XDR, Microsoft Fabric, Microsoft Graph, Microsoft Intune, Microsoft Planner, Microsoft Purview, Microsoft Teams, Microsoft To Do, Power BI, SharePoint Online, Universal Print, and Windows 365. Microsoft's public page continues to list Microsoft 365 and Microsoft consumer products as service degradation, with the headline that users may be unable to connect to multiple Microsoft 365 services, and Azure as having no issues detected at this time, with no active Azure events on the Azure status page. Downdetector for Microsoft 365, read at about 12:25 AM Eastern, still showed user reports indicating problems, with a chart peak of 45,864 reports in the last 24 hours and Exchange the most reported problem at 64 percent, and comments at 12:12-12:20 AM Eastern were mixed, some users reporting mail sending again and others still not working, corroborating still-active impact with at most anecdotal partial recovery; Downdetector is a user-report source and does not mirror Microsoft's 11:57 PM Eastern wording, and that distinction is stated here openly. Microsoft has not declared the incident resolved and has not stated compensation, and its next update is now due by 1:00 AM Eastern on November 13 (6:00 AM UTC).

Timeline additions: November 12, 2026, 11:57 PM Eastern (8:57 PM Pacific, 4:57 AM UTC on November 13) — Microsoft public service health update: surge in outbound call volume from routing services to backend servers observed as mitigation was applied, linked to traffic rebalancing; multiple workstreams to pinpoint the cause; virtual machines being scaled up to increase capacity; machines in a bad state being queried for a forced sync of the recent network change, with stuck machines preventing sync as expected; effectiveness of changes being monitored; potentially impacted list remains 19 services; next update due by 1:00 AM Eastern on November 13 (6:00 AM UTC). Incident remains a service degradation, not restored.

Status: Active at verification time, November 13, 2026, at 12:26 AM Eastern (5:26 AM UTC). No restoration posted.

Sources (new for this update): Microsoft Service Health Status, status.cloud.microsoft, last updated November 13, 2026 at 4:57 AM UTC, read live 12:24-12:26 AM ET, Azure Status, azure.status.microsoft, no active events, read live 12:25 AM ET, Downdetector, Microsoft 365 status, user reports show problems, read about 12:25 AM ET

Update, November 13, 2026, 12:53 AM Eastern: Microsoft remains in service degradation with no restoration, and its 12:46 AM Eastern update on November 13 (5:46 AM UTC, read live 12:54-12:56 AM Eastern) shifts from the specific rebalancing and sync problems described at 11:57 PM Eastern to a broader recovery posture. In paraphrase, Microsoft says it is pursuing multiple workstreams to pinpoint the underlying cause of the traffic influx and to advance recoverability of the backend servers; it is taking a measured approach to identify and repair affected infrastructure so it can confirm the developed changes were applied, and it is tracking results to verify the servers show the anticipated recovery and performance. It also states it is not aware of any malicious activity causing the incident, that it will treat the incident with urgency and priority until full resolution, and that once it is mitigated it will provide full root-cause details, defense-in-depth repair items and more in a Post-Incident Report. No recovery percentage or estimated time to resolution is given, and the 12:46 AM Eastern text no longer mentions the surge in outbound call volume from routing services, traffic rebalancing, virtual machine scale-up, or bad-state machines blocking the forced sync of the recent network change. The scope remains users attempting to access affected Microsoft 365 services. The potentially impacted list remains 19 services, unchanged: Exchange Online, Microsoft 365 admin center, Microsoft 365 apps, Microsoft 365 Apps Admin Center, Microsoft 365 Education, Microsoft Copilot 365, Microsoft Defender for Office 365, Microsoft Defender XDR, Microsoft Fabric, Microsoft Graph, Microsoft Intune, Microsoft Planner, Microsoft Purview, Microsoft Teams, Microsoft To Do, Power BI, SharePoint Online, Universal Print, and Windows 365. Microsoft's public page continues to list Microsoft 365 and Microsoft consumer products as service degradation, with the headline that users may be unable to connect to multiple Microsoft 365 services, and Azure as having no issues detected at this time, with no active Azure events on the Azure status page. Downdetector for Microsoft 365, read at about 12:54-12:57 AM Eastern, still showed user reports indicating problems, with a chart peak of 45,301 reports in the last 24 hours and Exchange the most reported problem at 64 percent, and comments at 12:18-12:20 AM Eastern were mixed, one user reporting Outlook fixed and sending again while others reported service still not working and sync still impaired, corroborating still-active impact with at most anecdotal partial recovery; Downdetector for Outlook, read in the same window, also still showed problems, with a chart peak of 129,476 reports in the last 24 hours and comments at 12:49-12:53 AM Eastern still reporting impaired access. Downdetector is a user-report source and does not mirror Microsoft's 12:46 AM Eastern wording, and that distinction is stated here openly. Microsoft has not declared the incident resolved and has not stated compensation, and its next update is now due by 2:00 AM Eastern on November 13 (7:00 AM UTC).

Timeline additions: November 13, 2026, 12:46 AM Eastern (9:46 PM Pacific on November 12, 5:46 AM UTC) — Microsoft public service health update: multiple workstreams being pursued to pinpoint the underlying cause of the traffic influx and advance recoverability of backend servers; measured approach to identify and repair affected infrastructure so developed changes can be confirmed as applied; results being tracked to verify servers show anticipated recovery and performance; Microsoft states it is not aware of any malicious activity causing the incident and will provide full root-cause details and defense-in-depth repair items in a Post-Incident Report once mitigated; potentially impacted list remains 19 services; next update due by 2:00 AM Eastern on November 13 (7:00 AM UTC). Incident remains a service degradation, not restored.

Status: Active at verification time, November 13, 2026, at 12:57 AM Eastern (5:57 AM UTC). No restoration posted.

Sources (new for this update): Microsoft Service Health Status, status.cloud.microsoft, last updated November 13, 2026 at 5:46 AM UTC, read live 12:54-12:56 AM ET, Azure Status, azure.status.microsoft, no active events, read live 12:54 AM ET, Downdetector, Microsoft 365 status, user reports show problems, read about 12:54-12:57 AM ET, Downdetector, Outlook status, user reports show problems, read about 12:54-12:57 AM ET

Update, November 13, 2026, 1:23 AM Eastern: Microsoft remains in service degradation with no restoration, and its 1:17 AM Eastern update on November 13 (6:17 AM UTC, read live 1:24-1:25 AM Eastern) adds new traffic-control detail to the recovery work. In paraphrase, Microsoft says that, to advance recoverability of its frontend servers, it is evaluating traffic controls that can be applied to increase capacity and stability, including traffic optimization actions such as traffic throttling, protocol adjustments, and failover routing intended to improve stability in active regions; in parallel it is expanding internal testing to track activity within a contained environment to improve traffic monitoring and issue detection capabilities. It restates that it is not aware of any malicious activity causing the incident, that it will treat the incident with urgency and priority until full resolution, and that once mitigated it will provide full root-cause details, defense-in-depth repair items and more in a Post-Incident Report. No recovery percentage or estimated time to resolution is given. The scope remains users attempting to access affected Microsoft 365 services. The potentially impacted list remains 19 services, unchanged: Exchange Online, Microsoft 365 admin center, Microsoft 365 apps, Microsoft 365 Apps Admin Center, Microsoft 365 Education, Microsoft Copilot 365, Microsoft Defender for Office 365, Microsoft Defender XDR, Microsoft Fabric, Microsoft Graph, Microsoft Intune, Microsoft Planner, Microsoft Purview, Microsoft Teams, Microsoft To Do, Power BI, SharePoint Online, Universal Print, and Windows 365. Microsoft's public page continues to list Microsoft 365 and Microsoft consumer products as service degradation, with the headline that users may be unable to connect to multiple Microsoft 365 services, and Azure as having no issues detected at this time, with no active Azure events on the Azure status page. Downdetector for Microsoft 365, read at about 1:25 AM Eastern, still showed user reports indicating problems, with a chart peak of 45,864 reports in the last 24 hours and Exchange the most reported problem at 64 percent, and its latest comments at 1:00-1:04 AM Eastern were joking or sympathetic in tone rather than recovery reports, with the most recent substantive still-down comment at 12:20 AM Eastern; Downdetector for Outlook, read in the same window, also still showed problems, with a chart peak of 128,392 reports in the last 24 hours and comments at 1:23-1:25 AM Eastern still reporting Outlook down. Downdetector is a user-report source and does not mirror Microsoft's 1:17 AM Eastern wording, and that distinction is stated here openly. Microsoft has not declared the incident resolved and has not stated compensation, and its next update remains due by 2:00 AM Eastern on November 13 (7:00 AM UTC).

Timeline additions: November 13, 2026, 1:17 AM Eastern (10:17 PM Pacific on November 12, 6:17 AM UTC) — Microsoft public service health update: traffic controls being evaluated to increase capacity and stability of frontend servers, including traffic throttling, protocol adjustments, and failover routing for active regions; internal testing being expanded in a contained environment to improve traffic monitoring and issue detection; Microsoft restates it is not aware of any malicious activity causing the incident and will provide full root-cause details and defense-in-depth repair items in a Post-Incident Report once mitigated; potentially impacted list remains 19 services; next update due by 2:00 AM Eastern on November 13 (7:00 AM UTC). Incident remains a service degradation, not restored.

Status: Active at verification time, November 13, 2026, at 1:25 AM Eastern (6:25 AM UTC). No restoration posted.

Sources (new for this update): Microsoft Service Health Status, status.cloud.microsoft, last updated November 13, 2026 at 6:17 AM UTC, read live 1:24-1:25 AM ET, Azure Status, azure.status.microsoft, no active events, read live 1:25 AM ET, Downdetector, Microsoft 365 status, user reports show problems, read about 1:25 AM ET, Downdetector, Outlook status, user reports show problems, read about 1:25 AM ET

Update, November 13, 2026, 2:23 AM Eastern: Microsoft remains in service degradation with no restoration, and its latest updates on November 13 (1:54 AM Eastern for MO1550821 and 1:56 AM Eastern for EX1550543, 6:54 and 6:56 AM UTC, read live 2:23-2:28 AM Eastern) report only marginal progress. In paraphrase, Microsoft says it is continuing to monitor activity across regions to evaluate server status and determine what actions can improve capacity, including reviewing server performance and confirming that developed patches have been applied and are working as intended after infrastructure reboots are completed; it says it has observed marginal success at this point, and in parallel it is expanding capacity through the use of virtual machines. It restates that it is not aware of any malicious activity causing the incident, that it will treat the incident with urgency and priority until full resolution, and that once mitigated it will provide full root-cause details, defense-in-depth repair items and more in a Post-Incident Report. No recovery percentage or estimated time to resolution is given. The potentially impacted list in the MO1550821 advisory has grown from 19 to 20 services, with Microsoft Power Apps back on the list (Microsoft notes a make.powerapps.com workaround for sign-in problems): Exchange Online, Microsoft 365 admin center, Microsoft 365 apps, Microsoft 365 Apps Admin Center, Microsoft 365 Education, Microsoft Copilot 365, Microsoft Defender for Office 365, Microsoft Defender XDR, Microsoft Fabric, Microsoft Graph, Microsoft Intune, Microsoft Planner, Microsoft Power Apps, Microsoft Purview, Microsoft Teams, Microsoft To Do, Power BI, SharePoint Online, Universal Print, and Windows 365. The other per-service workaround notes are unchanged. Microsoft's public page continues to show service degradation with the headline that users may be unable to connect to multiple Microsoft 365 services, last updated 6:57 AM UTC, and Azure as having no issues detected at this time, with no active Azure events on the Azure status page. Downdetector for Microsoft 365, read at about 2:26 AM Eastern, still showed user reports indicating problems, with a chart peak of 45,864 reports in the last 24 hours and Exchange the most reported problem at 64 percent, and its newest comments at about 2:08-2:09 AM Eastern were still asking how long the downtime would last; Downdetector for Outlook, read in the same window, also still showed problems, with a chart peak of 128,392 reports in the last 24 hours and comments at about 2:11 AM Eastern still reporting Outlook down. Downdetector is a user-report source and does not mirror Microsoft's 1:54-1:56 AM Eastern wording, and that distinction is stated here openly. No reputable news report in the last hour reported restoration. Microsoft has not declared the incident resolved and has not stated compensation, and its next update is due by 2:30 AM Eastern on November 13 (7:30 AM UTC) for both incidents. Two header timestamps are noted openly: the official public page shows last updated 6:57:32 AM UTC, shortly after the mirror timeline timestamps, with no additional substantive entry; and the MO1550821 mirror header shows 7:02 AM UTC with no timeline message at that time, so 6:54 AM UTC is treated as its latest substantive entry.

Timeline additions: November 13, 2026, 1:54 AM Eastern (10:54 PM Pacific on November 12, 6:54 AM UTC) — Microsoft MO1550821 update, and 1:56 AM Eastern (6:56 AM UTC) — Microsoft EX1550543 update: monitoring across regions to evaluate server status and capacity actions; server performance being reviewed; developed patches confirmed applied and working as intended after infrastructure reboots; marginal success observed; capacity being expanded through virtual machines; Microsoft restates it is not aware of any malicious activity causing the incident and will provide full root-cause details and defense-in-depth repair items in a Post-Incident Report once mitigated; potentially impacted list grows to 20 services with Microsoft Power Apps back on it; next update due by 2:30 AM Eastern on November 13 (7:30 AM UTC). Incident remains a service degradation, not restored.

Status: Active at verification time, November 13, 2026, at 2:27 AM Eastern (7:27 AM UTC). No restoration posted.

Sources (new for this update): Microsoft 365 Service Health Status, status.cloud.microsoft, last updated November 13, 2026 at 6:57 AM UTC, read live 2:23-2:28 AM ET, Cloud Admin Hub mirror of Microsoft Service Communications API, EX1550543, last Microsoft update November 13, 2026 at 6:56 AM UTC, Cloud Admin Hub mirror of Microsoft Service Communications API, MO1550821, latest substantive entry November 13, 2026 at 6:54 AM UTC, Azure Status, azure.status.microsoft, no active events, read live about 2:26 AM ET, Downdetector, Microsoft 365 status, user reports show problems, read about 2:26 AM ET, Downdetector, Outlook status, user reports show problems, read about 2:26 AM ET

Update, November 13, 2026, 2:53 AM Eastern: Microsoft remains in service degradation with no restoration, and its latest updates on November 13 (2:24 AM Eastern for MO1550821 and 2:25 AM Eastern for EX1550543, 7:24 and 7:25 AM UTC, read live 2:54-2:56 AM Eastern) report positive results for server stability after a patch. In paraphrase, Microsoft says it is seeing positive results for server stability after applying an upstream authentication and routing configuration component patch to a portion of its infrastructure, it will continue to monitor progress, and it is working to expand the patch to servers supporting active regions coming online. It restates that it is not aware of any malicious activity causing the incident, and that once mitigated it will provide full root-cause details, defense-in-depth repair items and more in a Post-Incident Report. No recovery percentage or estimated time to resolution is given. The potentially impacted list in the MO1550821 advisory is unchanged at 20 services: Exchange Online, Microsoft 365 admin center, Microsoft 365 apps, Microsoft 365 Apps Admin Center, Microsoft 365 Education, Microsoft Copilot 365, Microsoft Defender for Office 365, Microsoft Defender XDR, Microsoft Fabric, Microsoft Graph, Microsoft Intune, Microsoft Planner, Microsoft Power Apps, Microsoft Purview, Microsoft Teams, Microsoft To Do, Power BI, SharePoint Online, Universal Print, and Windows 365. Microsoft's public page continues to show service degradation with the headline that users may be unable to connect to multiple Microsoft 365 services, last updated 7:29 AM UTC, and Azure as having no issues detected at this time, with no active Azure events on the Azure status page. Downdetector for Microsoft 365, read at about 2:54 AM Eastern, still showed user reports indicating problems, with a chart peak of 47,252 reports in the last 24 hours and Exchange the most reported problem at 64 percent, and newest comments at about 2:44 AM Eastern still reporting service down; Downdetector for Outlook, read at about 2:55 AM Eastern, also still showed problems, with a chart peak of 129,519 reports in the last 24 hours and no newest comment reporting restoration. Downdetector is a user-report source and does not mirror Microsoft's 2:24-2:25 AM Eastern wording, and that distinction is stated here openly. No reputable news report in the last hour reported restoration. Microsoft has not declared the incident resolved and has not stated compensation, and its next update is due by 3:30 AM Eastern on November 13 (8:30 AM UTC) for both incidents. A header timestamp is noted openly: the official public page shows last updated 7:29:09 AM UTC, after the mirror timeline timestamps of 7:24 and 7:25 AM UTC, with no additional substantive timeline entry treated separately.

Timeline additions: November 13, 2026, 2:24 AM Eastern (11:24 PM Pacific on November 12, 7:24 AM UTC) — Microsoft MO1550821 update, and 2:25 AM Eastern (7:25 AM UTC) — Microsoft EX1550543 update: positive results for server stability after applying an upstream authentication/routing configuration component patch to a portion of infrastructure; monitoring continuing; patch being expanded to servers supporting active regions coming online; Microsoft restates it is not aware of any malicious activity causing the incident and will provide full root-cause details and defense-in-depth repair items in a Post-Incident Report once mitigated; potentially impacted list unchanged at 20 services; next update due by 3:30 AM Eastern on November 13 (8:30 AM UTC). Incident remains a service degradation, not restored.

Status: Active at verification time, November 13, 2026, at 2:55 AM Eastern (7:55 AM UTC). No restoration posted.

Sources (new for this update): Microsoft 365 Service Health Status, status.cloud.microsoft, last updated November 13, 2026 at 7:29 AM UTC, read live 2:54 AM ET, Cloud Admin Hub mirror of Microsoft Service Communications API, EX1550543, last Microsoft update November 13, 2026 at 7:25 AM UTC, Cloud Admin Hub mirror of Microsoft Service Communications API, MO1550821, last Microsoft update November 13, 2026 at 7:24 AM UTC, Azure Status, azure.status.microsoft, no active events, read live about 2:54 AM ET, Downdetector, Microsoft 365 status, user reports show problems, read about 2:54 AM ET, Downdetector, Outlook status, user reports show problems, read about 2:55 AM ET

Update, November 13, 2026, 4:23 AM Eastern: Microsoft remains in service degradation with no restoration, and its latest update on November 13 (4:14 AM Eastern, 9:14 AM UTC, read live 4:24 AM Eastern) reports early signs of stabilization. In paraphrase, Microsoft says recovery efforts are ongoing across impacted infrastructure, it is seeing early signs of stabilization but service capacity has not yet returned to normal levels and health remains variable as traffic is carefully reintroduced, its primary mitigation path continues to focus on service stability and controlled recovery, engineering teams are cycling affected infrastructure through traffic drain, restart, remediation, and staged return-to-service while monitoring closely, it is evaluating additional mitigation options to improve recovery speed and consistency, network and traffic-management actions remain in progress, and it continues to prioritize backlog and queue health to preserve delayed mail during recovery. As part of that effort, Microsoft is extending the email timeout window to 48 hours to help protect delayed messages while service recovery continues. It restates that it is not aware of any malicious activity causing the incident, and that it will share a full Post-Incident Report with root cause and defense-in-depth actions after recovery is complete. The potentially impacted list is unchanged at 20 services: Exchange Online, Microsoft 365 admin center, Microsoft 365 apps, Microsoft 365 Apps Admin Center, Microsoft 365 Education, Microsoft Copilot 365, Microsoft Defender for Office 365, Microsoft Defender XDR, Microsoft Fabric, Microsoft Graph, Microsoft Intune, Microsoft Planner, Microsoft Power Apps, Microsoft Purview, Microsoft Teams, Microsoft To Do, Power BI, SharePoint Online, Universal Print, and Windows 365. Microsoft's public page continues to show service degradation with the headline that users may be unable to connect to multiple Microsoft 365 services, and Azure as having no issues detected at this time, with no active Azure events on the Azure status page. Downdetector for Microsoft 365, read at about 4:24 AM Eastern, still showed user reports indicating problems, with a chart peak of 45,864 reports in the last 24 hours and Exchange the most reported problem at 64 percent, and newest comments at about 4:01 to 4:09 AM Eastern still reporting service down; Downdetector for Outlook, read at about 4:24 AM Eastern, also still showed problems, with a chart peak of 128,392 reports in the last 24 hours and no restoration reports visible. No reputable news report since the 3:53 AM Eastern check reported restoration; Forbes (published 3:48 AM Eastern, updated 4:07 AM Eastern) and India Today via MSN (about 3:57 AM Eastern) both still described the outage as active and both predate the 4:14 AM Eastern Microsoft update. Microsoft has not declared the incident resolved and has not stated compensation, and its next update is due by 5:00 AM Eastern on November 13 (10:00 AM UTC).

Timeline additions: November 13, 2026, 4:14 AM Eastern (1:14 AM Pacific, 9:14 AM UTC) — Microsoft update: early signs of stabilization reported, but service capacity not yet returned to normal levels and health variable as traffic is carefully reintroduced; mitigation continues through traffic drain, restart, remediation, and staged return-to-service, with additional mitigation options being evaluated; email timeout window extended to 48 hours to help protect delayed messages; Microsoft restates it is not aware of any malicious activity causing the incident and will provide a Post-Incident Report after recovery; potentially impacted list unchanged at 20 services; next update due by 5:00 AM Eastern on November 13 (10:00 AM UTC). Incident remains a service degradation, not restored.

Status: Active at verification time, November 13, 2026, at 4:24 AM Eastern (9:24 AM UTC). No restoration posted.

Sources (new for this update): Microsoft 365 Service Health Status, status.cloud.microsoft, last updated November 13, 2026 at 9:14 AM UTC, read live 4:24 AM ET, Microsoft Admin Center Status RSS feed, msit.status.cloud.microsoft, newest item November 13, 2026 at 9:14 AM UTC, read live 4:25 AM ET, Azure Status, azure.status.microsoft, no active events, read live about 4:24 AM ET, Downdetector, Microsoft 365 status, user reports show problems, read about 4:24 AM ET, Downdetector, Outlook status, user reports show problems, read about 4:24 AM ET

Update, November 13, 2026, 5:23 AM Eastern: Microsoft remains in service degradation with no restoration, and its latest update on November 13 (5:01 AM Eastern, 10:01 AM UTC, read live 5:23 to 5:24 AM Eastern) reports that recovery has progressed in phases with incremental improvement in several workloads. In paraphrase, Microsoft says recovery actions are ongoing and have progressed in phases across affected Microsoft 365 infrastructure, global telemetry and customer reports show incremental improvement in several workloads, however service health remains variable and capacity has not yet fully returned to baseline, network and traffic-management actions remain active, and to protect email during recovery it is continuing to prioritize queue and backlog processing, with the email timeout window extended to 48 hours to preserve delayed messages. Microsoft states that at this time it has no evidence of malicious activity associated with this incident, that it will continue to treat this with urgency until full mitigation, and that it will share a full Post-Incident Report with root cause and defense-in-depth actions after mitigation is complete. The potentially impacted list is unchanged at 20 services: Exchange Online, Microsoft 365 admin center, Microsoft 365 apps, Microsoft 365 Apps Admin Center, Microsoft 365 Education, Microsoft Copilot 365, Microsoft Defender for Office 365, Microsoft Defender XDR, Microsoft Fabric, Microsoft Graph, Microsoft Intune, Microsoft Planner, Microsoft Power Apps, Microsoft Purview, Microsoft Teams, Microsoft To Do, Power BI, SharePoint Online, Universal Print, and Windows 365. Microsoft's public page continues to show service degradation with the headline that users may be unable to connect to multiple Microsoft 365 services, and Azure as having no issues detected at this time. Downdetector for Microsoft 365, read at about 5:24 AM Eastern, still showed user reports indicating problems, with a chart peak of 45,864 reports in the last 24 hours, Exchange the most reported problem at 64 percent, and a comment at 5:04 AM Eastern still reporting being unable to log in to Outlook in the Tampa, FL area; Downdetector for Outlook, read at about 5:24 AM Eastern, also still showed problems, with a chart peak of 128,392 reports in the last 24 hours and no restoration reports. Microsoft has not declared the incident resolved and has not stated compensation, and its next update is due by 6:00 AM Eastern on November 13 (11:00 AM UTC).

Timeline additions: November 13, 2026, 5:01 AM Eastern (2:01 AM Pacific, 10:01 AM UTC) — Microsoft update: recovery actions have progressed in phases, incremental improvement in several workloads per global telemetry and customer reports, but service health remains variable and capacity has not yet fully returned to baseline; network and traffic-management actions remain active; queue and backlog processing prioritized and email timeout window extended to 48 hours to preserve delayed messages; Microsoft states it has no evidence of malicious activity associated with this incident and will share a full Post-Incident Report after mitigation; potentially impacted list unchanged at 20 services; next update due by 6:00 AM Eastern on November 13 (11:00 AM UTC). Incident remains a service degradation, not restored.

Status: Active at verification time, November 13, 2026, at 5:24 AM Eastern (10:24 AM UTC). No restoration posted.

Sources (new for this update): Microsoft 365 Service Health Status, status.cloud.microsoft, last updated November 13, 2026 at 10:01 AM UTC, read live 5:23 to 5:24 AM ET, Downdetector, Microsoft 365 status, user reports show problems, read about 5:24 AM ET, Downdetector, Outlook status, user reports show problems, read about 5:24 AM ET

Update, November 13, 2026, 6:23 AM Eastern: Microsoft remains in service degradation with no restoration, and its latest business update on November 13 (6:04 AM Eastern, 11:04 AM UTC, read live 6:25 to 6:27 AM Eastern) reports further recovery progress, now tied specifically to Asia Pacific. In paraphrase, Microsoft says recovery actions have been completed across portions of the affected infrastructure in the Asia Pacific region, traffic is being gradually restored there, and it is seeing improvements in key customer scenarios including mailbox access and delayed email processing, while some users may continue to experience intermittent issues. Its focus is now on extending those recovery actions across affected infrastructure in other regions, while continuing stabilization efforts and adding supporting capacity to improve service consistency. Reducing email queues and backlogs remains a priority, and the extended 48-hour email timeout window remains in place to help protect delayed messages as delivery catches up. Microsoft states it has no evidence of malicious activity associated with this incident, will continue to treat it with urgency until full mitigation, and will share a full Post-Incident Report after mitigation. The potentially impacted list is unchanged at 20 services: Exchange Online, Microsoft 365 admin center, Microsoft 365 apps, Microsoft 365 Apps Admin Center, Microsoft 365 Education, Microsoft Copilot 365, Microsoft Defender for Office 365, Microsoft Defender XDR, Microsoft Fabric, Microsoft Graph, Microsoft Intune, Microsoft Planner, Microsoft Power Apps, Microsoft Purview, Microsoft Teams, Microsoft To Do, Power BI, SharePoint Online, Universal Print, and Windows 365. Microsoft's public page continues to show service degradation with the headline that users may be unable to connect to multiple Microsoft 365 services, and Azure as having no issues detected at this time; the separate Azure status page likewise shows no active events. A separate consumer-products update at 6:21 AM Eastern (11:21 AM UTC) also remains service degradation, covering Outlook.com, OneDrive, OneNote, Microsoft To Do, Teams, and Microsoft 365 for the web, with its next update by 7:30 AM Eastern. Downdetector for Microsoft 365, read at about 6:25 AM Eastern, still showed user reports indicating problems, with a chart peak of 45,864 reports in the last 24 hours, Exchange the most reported problem at 64 percent, and newest comments at 6:23 to 6:24 AM Eastern still reporting the service down in London and the UAE; Downdetector for Outlook, read at about 6:26 AM Eastern, also still showed problems, with a chart peak of 128,392 reports in the last 24 hours and newest comments at 6:24 to 6:25 AM Eastern still reporting Outlook down, with one Indiana report of a brief overnight return followed by a renewed outage, which is not a restoration. No reputable news source reported restoration; Moneycontrol's November 13 coverage records the outage continuing into Friday with earlier fixes not taking as expected. Microsoft has not declared the incident resolved and has not stated compensation, and its next business update is due by 7:00 AM Eastern on November 13 (12:00 PM UTC).

Timeline additions: November 13, 2026, 6:04 AM Eastern (3:04 AM Pacific, 11:04 AM UTC) — Microsoft business update: additional progress toward recovery, recovery actions completed across portions of affected infrastructure in Asia Pacific, traffic gradually restored with improvements in mailbox access and delayed email processing, intermittent issues may continue, focus extending recovery actions to other regions while continuing stabilization and adding supporting capacity, email queue and backlog reduction remains a priority with the 48-hour email timeout window in place, no evidence of malicious activity, Post-Incident Report promised after mitigation; potentially impacted list unchanged at 20 services; next update due by 7:00 AM Eastern on November 13 (12:00 PM UTC). November 13, 2026, 6:21 AM Eastern (11:21 AM UTC) — Microsoft consumer update: service degradation continues for Outlook.com and related consumer services; next consumer update by 7:30 AM Eastern. Incident remains a service degradation, not restored.

Status: Active at verification time, November 13, 2026, at 6:27 AM Eastern (11:27 AM UTC). No restoration posted.

Sources (new for this update): Microsoft 365 Service Health Status, status.cloud.microsoft, last updated November 13, 2026 at 11:04 AM UTC, read live 6:25 to 6:27 AM ET, Azure Status, azure.status.microsoft, no active events, read live about 6:25 AM ET, Downdetector, Microsoft 365 status, user reports show problems, read about 6:25 AM ET, Downdetector, Outlook status, user reports show problems, read about 6:26 AM ET, Moneycontrol, Microsoft outage: Fixes fail to work 'as expected'; Outlook, Teams, Copilot services remain affected, November 13, 2026

Update, November 13, 2026, 7:23 AM Eastern: Microsoft remains in service degradation with no restoration, and its latest business update on November 13 (7:00 AM Eastern, 12:00 PM UTC, read live 7:23 to 7:26 AM Eastern) reports encouraging recovery progress, now led by Europe. In paraphrase, Microsoft says service availability and email delivery performance are improving across a growing portion of the affected Microsoft 365 infrastructure in Europe, Japan remains comparatively more stable, and North America is also improving, while some users may still experience intermittent issues as recovery actions continue. It is focused on addressing the remaining areas of disruption and improving service consistency across affected regions. Reducing email queues and backlogs remains a priority, and the extended 48-hour email timeout window remains in place to help protect delayed messages as delivery catches up. Microsoft states it has no evidence of malicious activity associated with this incident, will continue to treat it with urgency until full mitigation, and will share a full Post-Incident Report with root cause and defense-in-depth actions after mitigation. No capacity figures were given in this update. The potentially impacted list is unchanged at 20 services: Exchange Online, Microsoft 365 admin center, Microsoft 365 apps, Microsoft 365 Apps Admin Center, Microsoft 365 Education, Microsoft Copilot 365, Microsoft Defender for Office 365, Microsoft Defender XDR, Microsoft Fabric, Microsoft Graph, Microsoft Intune, Microsoft Planner, Microsoft Power Apps, Microsoft Purview, Microsoft Teams, Microsoft To Do, Power BI, SharePoint Online, Universal Print, and Windows 365. Microsoft's public page continues to show service degradation for Microsoft 365 business and consumer products, and Azure as having no issues detected at this time. A separate consumer-products update at 6:55 AM Eastern (11:55 AM UTC) also remains service degradation, covering Outlook.com, OneDrive, OneNote, Microsoft To Do, Teams, and Microsoft 365 for the web, with its next update by 9:30 AM Eastern; the individual consumer products are each listed operational while the consumer aggregate remains degraded. Downdetector for Microsoft 365, read at about 7:25 AM Eastern, still showed user reports indicating problems, with a chart peak of 45,864 reports in the last 24 hours and Exchange the most reported problem at 64 percent; Downdetector for Outlook also still showed problems, with a chart peak of 128,392 reports in the last 24 hours. Newest Downdetector comments at 7:02 to 7:24 AM Eastern are mixed: many users report email working again (including Tampa Bay, St. Louis, Jacksonville, South Georgia, Ohio, Baltimore, Connecticut, Florida, Spain and India), while others are still down (including Sao Paulo, Indonesia, and northeastern Pennsylvania) and Copilot is still reported down by some — a partial, piecemeal recovery, not a restoration. No reputable news source reported restoration: Reuters, updated about 7:18 AM Eastern November 13, reported Outlook, Teams and Copilot still down on Friday with the outage lasting more than 12 hours, and NBC News, updated 6:56 AM Eastern, reported Microsoft still working Friday morning and citing the about 7:00 AM update's encouraging recovery progress in paraphrase. Microsoft has not declared the incident resolved and has not stated compensation, and its next business update is due by 8:00 AM Eastern on November 13 (1:00 PM UTC).

Timeline additions: November 13, 2026, 7:00 AM Eastern (4:00 AM Pacific, 12:00 PM UTC) — Microsoft business update: encouraging recovery progress in Europe with service availability and email delivery improving across a growing portion of affected infrastructure, Japan comparatively more stable, North America also improving, intermittent issues may continue, focus on remaining areas of disruption and service consistency, email queue and backlog reduction a priority with the 48-hour email timeout window in place, no evidence of malicious activity, Post-Incident Report promised after mitigation; potentially impacted list unchanged at 20 services; next update due by 8:00 AM Eastern on November 13 (1:00 PM UTC). November 13, 2026, 6:55 AM Eastern (11:55 AM UTC) — Microsoft consumer update: service degradation continues for Outlook.com and related consumer services; next consumer update by 9:30 AM Eastern. Incident remains a service degradation, not restored.

Status: Active at verification time, November 13, 2026, at 7:26 AM Eastern (12:26 PM UTC). No restoration posted.

Sources (new for this update): Microsoft 365 Service Health Status, status.cloud.microsoft, last updated November 13, 2026 at 12:00 PM UTC, read live 7:23 to 7:26 AM ET, Downdetector, Microsoft 365 status, user reports show problems, read about 7:25 AM ET, Downdetector, Outlook status, user reports show problems, read about 7:25 AM ET, Reuters: Microsoft outage hits Outlook, Teams and Copilot worldwide, November 12, 2026, updated November 13, 2026, NBC News: Microsoft services hit by major outage across the world, November 12, 2026, updated November 13, 2026

Update, November 13, 2026, 8:23 AM Eastern: Microsoft remains in service degradation with no restoration, and its latest business update on November 13 (7:58 AM Eastern, 12:58 PM UTC, read live 8:24 to 8:25 AM Eastern) reports continued recovery progress across affected regions. In paraphrase, Microsoft says broader improvements are now observed in North America and sustained improvements continue across much of Europe, with encouraging recovery signals in Asia Pacific, although some users may continue to experience intermittent access issues or delayed email delivery as mitigation progresses across the remaining affected infrastructure. Its focus remains on stabilizing recovered infrastructure, completing mitigation in the remaining impacted areas, and reducing delayed email queues and backlogs, while closely monitoring service consistency and validating recovery across different connection methods as it works toward full mitigation. Microsoft states it has no evidence of malicious activity associated with this incident, will continue to treat it with urgency until full mitigation, and will share a full Post-Incident Report with root cause and defense-in-depth actions after mitigation. The potentially impacted list is unchanged at 20 services: Exchange Online, Microsoft 365 admin center, Microsoft 365 apps, Microsoft 365 Apps Admin Center, Microsoft 365 Education, Microsoft Copilot 365, Microsoft Defender for Office 365, Microsoft Defender XDR, Microsoft Fabric, Microsoft Graph, Microsoft Intune, Microsoft Planner, Microsoft Power Apps, Microsoft Purview, Microsoft Teams, Microsoft To Do, Power BI, SharePoint Online, Universal Print, and Windows 365. Microsoft's public page continues to show service degradation for Microsoft 365 business products, and Azure as having no issues detected at this time; the Azure status page itself shows no active events. The consumer-products aggregate also remains service degradation, with no new consumer update this sweep: its latest update remains 6:55 AM Eastern (11:55 AM UTC), covering Outlook.com, OneDrive, OneNote, Microsoft To Do, Teams, and Microsoft 365 for the web, with its next update by 9:30 AM Eastern; the individual consumer products are each listed operational while the consumer aggregate remains degraded. Independent reporting corroborates recovery without restoration: Harava News, published 12:48 PM UTC on November 13, reported Microsoft began restoring services after an outage of more than 12 hours with early signs of recovery but some users still able to have problems and no full return to normal confirmed, and ITDeskUK, last updated 12:32 PM GMT, reported recovery progressing across Europe with some disruption remaining and full restoration not yet confirmed. Microsoft has not declared the incident resolved and has not stated compensation, and its next business update is due by 9:00 AM Eastern on November 13 (2:00 PM UTC).

Timeline additions: November 13, 2026, 7:58 AM Eastern (12:58 PM UTC) — Microsoft business update: continued recovery progress, broader improvements in North America, sustained improvements across much of Europe, encouraging recovery signals in Asia Pacific, intermittent access issues or delayed email delivery may continue, focus on stabilizing recovered infrastructure, completing mitigation in remaining areas, and reducing delayed email queues and backlogs, monitoring service consistency and validating recovery across connection methods, no evidence of malicious activity, Post-Incident Report promised after mitigation; potentially impacted list unchanged at 20 services; next update due by 9:00 AM Eastern on November 13 (2:00 PM UTC). Incident remains a service degradation, not restored.

Status: Active at verification time, November 13, 2026, at 8:25 AM Eastern (1:25 PM UTC). No restoration posted.

Sources (new for this update): Microsoft 365 Service Health Status, status.cloud.microsoft, last updated November 13, 2026 at 12:58 PM UTC, read live 8:24 to 8:25 AM ET, Azure Status, azure.status.microsoft, no active events, read live about 8:25 AM ET, Harava News: Microsoft Begins Restoring Services After More Than 12-Hour Global Outage, November 13, 2026, ITDeskUK: Microsoft 365 Outage, last updated November 13, 2026, 12:32 GMT

Update, November 13, 2026, 9:23 AM Eastern: Microsoft remains in service degradation with no restoration, and its latest business update on November 13 (9:00 AM Eastern, 2:00 PM UTC, read live 9:24 to 9:27 AM Eastern) reports continuing improvements in service availability, with email queues significantly reduced and approaching normal levels. Some users may still experience intermittent access issues or delayed email delivery as recovery continues. Microsoft says it has implemented additional mitigation measures and is restoring the remaining affected infrastructure while investigating residual service issues, closely monitoring service health and validating recovery across affected connection methods to ensure sustained stability. Microsoft states it has no evidence of malicious activity associated with this incident, will continue to treat it with urgency until full mitigation, and will share a full Post-Incident Report with root cause and defense-in-depth actions after mitigation. The potentially impacted list is unchanged at 20 services: Exchange Online, Microsoft 365 admin center, Microsoft 365 apps, Microsoft 365 Apps Admin Center, Microsoft 365 Education, Microsoft Copilot 365, Microsoft Defender for Office 365, Microsoft Defender XDR, Microsoft Fabric, Microsoft Graph, Microsoft Intune, Microsoft Planner, Microsoft Power Apps, Microsoft Purview, Microsoft Teams, Microsoft To Do, Power BI, SharePoint Online, Universal Print, and Windows 365. The consumer Microsoft 365 aggregate also remains service degradation, last updated 9:10 AM Eastern (2:10 PM UTC), with the other consumer products listed operational. Azure shows no issues detected. Independent reporting corroborates a continuing outage without restoration: Reuters described a more than 12-hour outage disrupting businesses and governments globally, and CNET reported Downdetector still showing about 32,000 reports in its latest coverage against a peak of about 130,000. Microsoft has not declared the incident resolved and has not stated compensation, and its next business update is due by 10:00 AM Eastern on November 13 (3:00 PM UTC).

Timeline additions: November 13, 2026, 9:00 AM Eastern (2:00 PM UTC) — Microsoft business update: continuing improvements in service availability, email queues significantly reduced and approaching normal levels, intermittent access issues or delayed email delivery may continue, additional mitigation implemented, remaining affected infrastructure being restored, residual issues being investigated, monitoring and validating recovery, no evidence of malicious activity, Post-Incident Report promised; potentially impacted list unchanged at 20 services; next update due by 10:00 AM Eastern on November 13 (3:00 PM UTC). Incident remains a service degradation, not restored.

Status: Active at verification time, November 13, 2026, at 9:27 AM Eastern (2:27 PM UTC). No restoration posted.

Sources (new for this update): Microsoft 365 Service Health Status, status.cloud.microsoft, last updated November 13, 2026 at 2:00 PM UTC, Azure Status, Reuters coverage of the Microsoft outage, November 2026, CNET: Is Microsoft Outlook Still Down?, November 13, 2026

Update, November 13, 2026, 9:53 AM Eastern: Microsoft remains in service degradation with no restoration, and its latest business update on November 13 (9:56 AM Eastern, 2:56 PM UTC, read live 9:55 AM and re-checked 10:02 to 10:05 AM Eastern) reports sustained improvements in service availability as recovery progresses across affected Microsoft 365 services. Service functionality continues to improve, although some users may still experience intermittent connectivity issues or delayed email delivery. Microsoft says its efforts are increasingly focused on resolving the remaining issues and restoring consistent service for all affected users, and that it is validating recovery across different connection methods and monitoring service stability to confirm that improvements are sustained. Microsoft states it has no evidence of malicious activity associated with this incident, will continue to treat this with urgency until full mitigation, and will share a full Post-Incident Report with root cause and defense-in-depth actions after mitigation. The potentially impacted list is unchanged at 20 services: Exchange Online, Microsoft 365 admin center, Microsoft 365 apps, Microsoft 365 Apps Admin Center, Microsoft 365 Education, Microsoft Copilot 365, Microsoft Defender for Office 365, Microsoft Defender XDR, Microsoft Fabric, Microsoft Graph, Microsoft Intune, Microsoft Planner, Microsoft Power Apps, Microsoft Purview, Microsoft Teams, Microsoft To Do, Power BI, SharePoint Online, Universal Print, and Windows 365. The consumer Microsoft 365 aggregate also remains service degradation, last updated 9:10 AM Eastern (2:10 PM UTC), next consumer update due by 11:30 AM Eastern. Azure shows no issues detected. Independent reporting corroborates a continuing outage without restoration: Downdetector listed Microsoft 365 issues continuing with Outlook and email mainly affected and knock-on problems in Teams and Copilot, and Reuters and AP headlines in search described Microsoft 365 services still down on Friday, November 13. Microsoft has not declared the incident resolved and has not stated compensation, and its next business update is due by 11:00 AM Eastern on November 13 (4:00 PM UTC).

Timeline additions: November 13, 2026, 9:56 AM Eastern (2:56 PM UTC) — Microsoft business update: sustained improvements in service availability as recovery progresses, functionality continues to improve, intermittent connectivity issues or delayed email delivery may continue, focus increasingly on resolving remaining issues and restoring consistent service, validating recovery across connection methods and monitoring stability, no evidence of malicious activity, Post-Incident Report promised; potentially impacted list unchanged at 20 services; next update due by 11:00 AM Eastern on November 13 (4:00 PM UTC). Incident remains a service degradation, not restored.

Status: Active at verification time, November 13, 2026, at 10:05 AM Eastern (3:05 PM UTC). No restoration posted.

Sources (new for this update): Microsoft 365 Service Health Status, status.cloud.microsoft, last updated November 13, 2026 at 2:56 PM UTC, Azure Status, Downdetector Microsoft 365, November 13, 2026

Update, November 13, 2026, 10:53 AM Eastern: Microsoft remains in service degradation with no restoration, and its latest business update on November 13 (10:56 AM Eastern, 3:56 PM UTC, read live 11:02 AM Eastern) says it remains focused on addressing residual impact and ensuring reliable service restoration, continues to assess recovery across various connection methods, and is closely monitoring service health to verify sustained stability. Microsoft states it has no evidence of malicious activity associated with this incident, will continue to treat this with urgency until full mitigation, and will share a full Post-Incident Report with root cause and defense-in-depth actions after mitigation. The potentially impacted list is unchanged at 20 services: Exchange Online, Microsoft 365 admin center, Microsoft 365 apps, Microsoft 365 Apps Admin Center, Microsoft 365 Education, Microsoft Copilot 365, Microsoft Defender for Office 365, Microsoft Defender XDR, Microsoft Fabric, Microsoft Graph, Microsoft Intune, Microsoft Planner, Microsoft Power Apps, Microsoft Purview, Microsoft Teams, Microsoft To Do, Power BI, SharePoint Online, Universal Print, and Windows 365. The consumer Microsoft 365 aggregate also remains service degradation, last updated 9:10 AM Eastern (2:10 PM UTC), next consumer update due by 11:30 AM Eastern. Azure shows no issues detected. Independent reporting corroborates a continuing outage without restoration: Downdetector carried a banner that Microsoft 365 issues continue with Outlook and email mainly affected and knock-on problems in Teams and Copilot, and USA Today / Naples News coverage on November 13 described the outage as still ongoing on Friday. Microsoft has not declared the incident resolved and has not stated compensation, and its next business update is due by 1:00 PM Eastern on November 13 (6:00 PM UTC).

Timeline additions: November 13, 2026, 10:56 AM Eastern (3:56 PM UTC) — Microsoft business update: remains focused on addressing residual impact and ensuring reliable service restoration, assessing recovery across connection methods, monitoring service health to verify sustained stability, no evidence of malicious activity, Post-Incident Report promised; potentially impacted list unchanged at 20 services; next update due by 1:00 PM Eastern on November 13 (6:00 PM UTC). Incident remains a service degradation, not restored.

Status: Active at verification time, November 13, 2026, at 11:04 AM Eastern (4:04 PM UTC). No restoration posted.

Sources (new for this update): Microsoft 365 Service Health Status, status.cloud.microsoft, last updated November 13, 2026 at 3:56 PM UTC, Azure Status, Downdetector Microsoft 365, November 13, 2026

Update, November 13, 2026, 11:53 AM Eastern: Microsoft remains in service degradation with no restoration. The business side is unchanged from its last update (11:07 AM Eastern, 4:07 PM UTC), which remains focused on residual impact, recovery assessed across connection methods, and monitoring for sustained stability, with the next business update due by 1:00 PM Eastern. The new update in this sweep is on the consumer side: at 11:24 AM Eastern (4:24 PM UTC, read live 11:54 AM to 12:03 PM Eastern) Microsoft's consumer Microsoft 365 update said it is observing signs of sustained recovery throughout the affected environment, its investigation into the underlying root cause is ongoing, and it is continuing to monitor the impacted services to verify service health levels remain stable. Microsoft names the consumer impact as Outlook.com, OneDrive, OneNote, Microsoft To Do, Teams, and Microsoft 365 for the web, although issues may also appear in other Microsoft 365 services; the consumer aggregate remains service degradation even though the listed consumer products individually show Operational. The potentially impacted business list is unchanged at 20 services. Azure shows no issues detected. Independent reporting corroborates a continuing outage without restoration: Downdetector carried a banner that Microsoft 365 issues continue with Outlook and email mainly affected and knock-on problems in Teams, Copilot and other apps, and both Anthropic and OpenAI report signs of recovery for their Microsoft 365 connectors while noting Microsoft's incident remains open. Microsoft has not declared the incident resolved and has not stated compensation, and its next consumer update is due by 1:30 PM Eastern on November 13 (6:30 PM UTC).

Timeline additions: November 13, 2026, 11:24 AM Eastern (4:24 PM UTC) — Microsoft consumer update: signs of sustained recovery throughout the affected environment, root-cause investigation ongoing, monitoring impacted services to verify service health levels remain stable; consumer impact named as Outlook.com, OneDrive, OneNote, Microsoft To Do, Teams, and Microsoft 365 for the web; next consumer update due by 1:30 PM Eastern on November 13 (6:30 PM UTC). Business side unchanged, next business update due by 1:00 PM Eastern. Incident remains a service degradation, not restored.

Status: Active at verification time, November 13, 2026, at 12:03 PM Eastern (5:03 PM UTC). No restoration posted.

Sources (new for this update): Microsoft 365 Service Health Status, status.cloud.microsoft, consumer update last updated November 13, 2026 at 4:24 PM UTC, Azure Status, Downdetector Microsoft 365, November 13, 2026

Update, November 13, 2026, 2:23 PM Eastern: Microsoft has now stated the cause of the incident. In its business update on November 13 (12:57 PM Eastern, 5:57 PM UTC), Microsoft said it is seeing broad recovery and stability across its services, and stated: this was a technical issue not related to cyber or AI/agents; the incident was introduced by an issue during an earlier network capacity upgrade that surfaced following a recent network change; Microsoft has addressed the underlying issue and continues to restore service to remaining customers and regions, restoring gradually while validating stability at each stage. The incident remains in Service degradation with no restoration declared, the potentially impacted list is unchanged at 20 services, and the next business update is expected by 3:00 PM Eastern. Microsoft's consumer update at 1:57 PM Eastern (6:57 PM UTC) carried the same account, with consumer impact unchanged (Outlook.com, OneDrive, OneNote, Microsoft To Do, Teams, and Microsoft 365 for the web) and the next consumer update expected by 4:00 PM Eastern. Microsoft will provide a full Post-Incident Report once its review is complete. The same statement was carried the same afternoon by USA Today, GeekWire, MacRumors and other outlets reporting Microsoft's apology post.

Timeline additions: November 13, 2026, 12:57 PM Eastern (5:57 PM UTC) — Microsoft business update: broad recovery and stability; cause stated as a technical issue introduced during an earlier network capacity upgrade, surfaced following a recent network change, not related to cyber or AI/agents; underlying issue addressed; gradual restoration continuing. November 13, 2026, 1:57 PM Eastern (6:57 PM UTC) — consumer update carrying the same account.

Status: Active at verification time, November 13, 2026, at 2:39 PM Eastern (7:39 PM UTC). No restoration posted.

Sources (new for this update): Microsoft service health status, USA Today live updates, November 13, 2026, GeekWire, November 13, 2026, MacRumors, November 13, 2026

Update, November 13, 2026, 3:23 PM Eastern: Microsoft remains in service degradation with no restoration, but its account has shifted from broad recovery to the mechanics of catching up. In its business update at 3:02 PM Eastern (8:02 PM UTC), Microsoft said that as its infrastructure stabilizes it is still draining queued messages and rebalancing traffic, so customers may see improved sign-in and access while delivery and processing continue to catch up. Microsoft said it does not have an estimated time for full recovery yet, and that service access can recover before mail flow fully normalizes. Its consumer update at 3:03 PM Eastern carried the same account. The business impacted list is unchanged at 20 services, including Exchange Online, Teams, SharePoint Online, Microsoft Copilot 365, Microsoft Defender XDR, Microsoft Intune, Purview and Power BI. Consumer impact is unchanged: Outlook.com, OneDrive, OneNote, Microsoft To Do, Teams, and Microsoft 365 for the web. Azure shows no issues. Independent reporting corroborates a continuing outage without restoration: Downdetector still shows Microsoft 365 user reports indicating problems (24-hour peak 25,148 reports, Exchange the most reported problem at 62 percent), with a sitewide banner noting the issues continue, mainly affecting Outlook and email with knock-on problems in Teams, Copilot and other apps. Microsoft has not declared the incident resolved and has not stated compensation. Its next update is due by 7:00 PM Eastern on November 13.

Timeline additions: November 13, 2026, 3:02 PM Eastern (8:02 PM UTC) — Microsoft business update: infrastructure stabilizing, queued messages still draining, traffic being rebalanced, sign-in/access may improve while delivery and processing catch up, no ETA for full recovery, service access can recover before mail flow fully normalizes; impacted list unchanged at 20 services; next update due by 7:00 PM Eastern on November 13 (12:00 AM UTC November 14). November 13, 2026, 3:03 PM Eastern (8:03 PM UTC) — Microsoft consumer update carries the same account; consumer impact unchanged; next update due by 7:00 PM Eastern. Incident remains a service degradation, not restored.

Status: Active at verification time, November 13, 2026, at 3:28 PM Eastern (8:28 PM UTC). No restoration posted.

Sources (new for this update): Microsoft 365 Service Health Status, status.cloud.microsoft, business update last updated November 13, 2026 at 8:02 PM UTC and consumer update at 8:03 PM UTC, Downdetector Microsoft 365, November 13, 2026

Update, November 13, 2026, 5:23 PM Eastern: Microsoft remains in service degradation with no restoration, but now reports sustained recovery. In its business update at 5:00 PM Eastern (10:00 PM UTC), Microsoft said it continues to observe sustained service recovery across the previously affected environments. Due to the severity and scope of the event, Microsoft said it will continue monitoring the service for an extended period to ensure no additional mitigative actions are required, and in parallel it will continue monitoring the backlog of email messages accrued during the event before considering the issue resolved. Microsoft said it is addressing all impact scenarios and believes the majority of impact scenarios have been addressed. Its consumer update is unchanged at 3:03 PM Eastern; the consumer next update, due by 4:30 PM Eastern, had not posted at verification time. The business impacted list is unchanged at 20 services, including Exchange Online, Teams, SharePoint Online, Microsoft Copilot, Microsoft Purview, Microsoft Fabric, Power BI and Power Apps. Azure shows no issues. Independent reporting corroborates a continuing outage without restoration: Downdetector still shows Microsoft 365 user reports indicating problems (24-hour peak 15,537 reports, Exchange the most reported problem at 61 percent) and Outlook reports still indicating problems (24-hour peak 38,724 reports), with a sitewide banner noting the issues continue, mainly affecting Outlook and email with knock-on problems in Teams, Copilot and other apps. Microsoft has not declared the incident resolved and has not stated compensation. Its next business update is due by 9:30 PM Eastern on November 13.

Timeline additions: November 13, 2026, 5:00 PM Eastern (10:00 PM UTC) — Microsoft business update: sustained service recovery observed across previously affected environments, extended monitoring due to severity and scope, email backlog accrued during the event still being monitored before considering the issue resolved, majority of impact scenarios believed addressed; impacted list unchanged at 20 services; next update due by 9:30 PM Eastern on November 13 (2:30 AM UTC November 14). Consumer update unchanged at 3:03 PM Eastern and overdue at verification. Incident remains a service degradation, not restored.

Status: Active at verification time, November 13, 2026, at 5:29 PM Eastern (10:29 PM UTC). No restoration posted.

Sources: Microsoft 365 Service Health Status, status.cloud.microsoft, business update last updated November 13, 2026 at 10:00 PM UTC, Downdetector Microsoft 365, November 13, 2026

Update, November 13, 2026, 7:53 PM Eastern: Microsoft remains in service degradation with no restoration. In its consumer update at 7:39 PM Eastern (12:39 AM UTC November 14), Microsoft said it is observing sustained recovery of impacted services across the previously affected environments, it is monitoring service health for an extended period to ensure no further action is needed to fully remediate the issue, and in parallel it is monitoring the backlog of email messages accumulated during the impact period to verify all are processed before the issue is considered remediated. User impact is unchanged: users may be unable to access or perform several actions in Microsoft 365 services. The business update is unchanged at 5:00 PM Eastern, with the same sustained-recovery account, extended monitoring, email-backlog monitoring, and a statement that the majority of impact scenarios have been addressed. The business impacted list is unchanged at 20 services. Azure shows no issues. Independent reporting corroborates a continuing outage without restoration: Downdetector still shows Microsoft 365 user reports indicating problems (24-hour peak 10,641 reports, Exchange the most reported problem at 61 percent) and Outlook reports still indicating problems (24-hour peak 31,573 reports), with reports falling sharply from the peak. Microsoft has not declared the incident resolved and has not stated compensation. Its next consumer update is due by 9:00 PM Eastern and its next business update by 9:30 PM Eastern on November 13.

Timeline additions: November 13, 2026, 7:39 PM Eastern (12:39 AM UTC November 14) — Microsoft consumer update: sustained recovery observed, extended monitoring of service health, email backlog accumulated during impact still being monitored to verify all messages process before the issue is considered remediated; user impact unchanged; next consumer update due by 9:00 PM Eastern November 13 (2:00 AM UTC November 14). Business update unchanged at 5:00 PM Eastern; next business update due by 9:30 PM Eastern. Incident remains a service degradation, not restored.

Status: Active at verification time, November 13, 2026, at 7:57 PM Eastern. No restoration posted.

Sources: Microsoft 365 Service Health Status, status.cloud.microsoft, consumer update last updated November 14, 2026 at 12:39 AM UTC, Downdetector Microsoft 365, November 13, 2026

Update, November 13, 2026, 8:53 PM Eastern: Microsoft remains in service degradation with no restoration. In its consumer update at 8:51 PM Eastern (1:51 AM UTC November 14), Microsoft said it is continuing to observe sustained recovery of impacted services across the previously affected environments, it is continuing to monitor service health metrics to ensure no further actions are required to fully remediate the issue, and it is monitoring the backlog of email messages to verify all are processed before the issue is considered remediated. User impact is unchanged: users may be unable to access or perform several actions in Microsoft 365 services. The business update is unchanged at 5:00 PM Eastern, with the same sustained-recovery account, extended monitoring, email-backlog monitoring, and a statement that the majority of impact scenarios have been addressed. The business impacted list is unchanged at 20 services. Azure shows no issues. Independent reporting corroborates a continuing outage without restoration: Downdetector still shows Microsoft 365 user reports indicating problems (24-hour peak 9,813 reports, Exchange the most reported problem at 60 percent) and Outlook reports still indicating problems (24-hour peak 29,038 reports). Microsoft has not declared the incident resolved and has not stated compensation. Its next consumer update is due by 11:00 PM Eastern November 13 and its next business update by 9:30 PM Eastern on November 13.

Timeline additions: November 13, 2026, 8:51 PM Eastern (1:51 AM UTC November 14) — Microsoft consumer update: sustained recovery continuing across previously affected environments, service health metrics monitoring to ensure no further actions are required to fully remediate, email backlog still being monitored to verify all messages are processed before the issue is considered remediated; user impact unchanged; next consumer update due by 11:00 PM Eastern November 13 (4:00 AM UTC November 14). Business update unchanged at 5:00 PM Eastern; next business update due by 9:30 PM Eastern. Incident remains a service degradation, not restored.

Status: Active at verification time, November 13, 2026, at 8:56 PM Eastern. No restoration posted.

Sources: Microsoft 365 Service Health Status, status.cloud.microsoft, consumer update last updated November 14, 2026 at 1:51 AM UTC, Downdetector Microsoft 365, November 13, 2026

Update, November 13, 2026, 10:23 PM Eastern: Microsoft remains in service degradation with no restoration. In its consumer update at 10:18 PM Eastern (3:18 AM UTC November 14), Microsoft said it is continuing to observe sustained recovery of impacted services across the previously affected environments, it is continuing to monitor service health metrics to ensure no further actions are required to fully remediate the issue, and it is monitoring the backlog of email messages to verify all are processed before the issue is considered remediated. User impact is unchanged: users may be unable to access or perform several actions in Microsoft 365 services. The business update is unchanged at 5:00 PM Eastern, and the next business update, due by 9:30 PM Eastern, had not posted at verification time. The business impacted list is unchanged at 20 services. Azure shows no issues. Independent reporting corroborates a continuing outage without restoration: Downdetector still shows Microsoft 365 user reports indicating problems (24-hour peak 9,374 reports, Exchange the most reported problem at 59 percent) and Outlook reports still indicating problems (24-hour peak 22,379 reports). Microsoft has not declared the incident resolved and has not stated compensation. Its next consumer update is due by 11:00 PM Eastern November 13.

Timeline additions: November 13, 2026, 10:18 PM Eastern (3:18 AM UTC November 14) — Microsoft consumer update: sustained recovery continuing across previously affected environments, service health metrics monitoring to ensure no further actions are required to fully remediate, email backlog still being monitored to verify all messages are processed before the issue is considered remediated; user impact unchanged; next consumer update due by 11:00 PM Eastern November 13 (4:00 AM UTC November 14). Business update unchanged at 5:00 PM Eastern; next business update due by 9:30 PM Eastern is overdue. Incident remains a service degradation, not restored.

Status: Active at verification time, November 13, 2026, at 10:26 PM Eastern. No restoration posted.

Sources: Microsoft 365 Service Health Status, status.cloud.microsoft, consumer update last updated November 14, 2026 at 3:18 AM UTC, Downdetector Microsoft 365, November 13, 2026

Update, November 13, 2026, 10:53 PM Eastern: Microsoft has restored the consumer side of this incident, while the business side remains in service degradation with no restoration. On its official status page, Microsoft 365 (Consumer) now shows Service restored, and its final consumer update says the services across the previously affected environments have fully recovered and the backlog of email messages has been processed, thus the issue is remediated. Microsoft lists the consumer incident start as Thursday, November 12, 2026 at 10:05 AM UTC and its end as Friday, November 13, 2026 at 4:10 PM UTC (11:10 AM Eastern), and says this is the final update for the event. The consumer section of the page shows no posted timestamp for that final update; it was first visible at 10:54 PM Eastern, after the 10:18 PM Eastern consumer update that was still reporting recovery in progress, so it posted between those two checks. Consumer user impact is now stated in the past tense: users may have been unable to access or perform several actions in Microsoft 365 services. The business update is unchanged at 5:00 PM Eastern (10:00 PM UTC), still reporting sustained recovery, extended monitoring, and email backlog monitoring before the issue is considered resolved, and its next update, due by 9:30 PM Eastern, had not posted at verification time. The business impacted list is unchanged at 20 services. Azure shows no issues. Downdetector still shows Microsoft 365 and Outlook user reports indicating problems (24-hour peaks 7,773 and 20,211 reports respectively, Exchange the most reported Microsoft 365 problem at 59 percent), with volumes tapering sharply through the evening, consistent with the still-open business incident rather than a fresh spike. Microsoft has not declared the business incident resolved and has not stated compensation.

Timeline additions: November 13, 2026, between 10:18 PM and 10:54 PM Eastern — Microsoft consumer final update first visible: Microsoft 365 (Consumer) Service restored, services fully recovered, email backlog processed, issue remediated, final update for the event; consumer incident end time listed as November 13, 2026, 4:10 PM UTC (11:10 AM Eastern); no posted timestamp shown on the consumer section. Business update unchanged at 5:00 PM Eastern; next business update due by 9:30 PM Eastern is overdue. Incident remains Active overall on the business side, not fully restored.

Status: Partially restored at verification time, November 13, 2026, at 10:56 PM Eastern — consumer restored / remediated, business still Active, Service degradation, no full restoration posted.

Sources: Microsoft 365 Service Health Status, status.cloud.microsoft, consumer final update first visible November 13, 2026 at 10:54 PM ET, business last updated November 13, 2026 at 10:00 PM UTC, Downdetector Microsoft 365, November 13, 2026

Update, November 14, 2026, 12:53 AM Eastern: Microsoft has restored the business side of this incident, completing the restoration. Microsoft 365 / Exchange Online (EX1550543 / MO1550821) is now Service restored / Resolved. The Exchange Online final update posted at 11:15 PM Eastern on November 13, 2026 (4:15 AM UTC November 14), and the Microsoft 365 suite final update posted at 11:17 PM Eastern on November 13 (4:17 AM UTC November 14). Microsoft lists the incident start as Thursday, November 12, 2026 at 10:05 AM UTC and its end as Friday, November 13, 2026 at 4:10 PM UTC (11:10 AM Eastern). An intermediate business update at 9:17 PM Eastern on November 13 reported continued recovery across previously affected environments, continued monitoring, and continued processing of the email backlog, with most impact scenarios believed addressed and work continuing on the remainder. In its final account, Microsoft states this was a technical issue not related to cyber or AI/agents, introduced by an issue during an earlier network capacity upgrade that surfaced following a recent network change, that it has addressed the underlying issue, and that services were restored gradually with stability validated at each stage. Microsoft will provide a preliminary Post-Incident Report within two business days and a final Post-Incident Report within five business days. The impacted list remains 20 services whose features interact with Exchange Online and email services; elements not depending on Exchange Online remained functional. Exchange connection methods affected were Outlook on the web, MAPI, EAS and REST, with possible on-premises mail-flow impact to and from Exchange Online. The consumer side was already restored and remediated, with the same end time. Azure shows no issues. Downdetector still showed elevated Microsoft 365 and Outlook user reports at verification (24-hour peaks 7,571 and 19,258 respectively), consistent with residual and lingering reports rather than a new Microsoft-declared incident. No compensation has been stated.

Timeline additions: November 13, 2026, 9:17 PM Eastern (2:17 AM UTC November 14) — Microsoft business update: continued recovery, monitoring, email-backlog processing, most impact scenarios believed addressed, next update by 11:30 PM Eastern. November 13, 2026, 11:15 PM Eastern (4:15 AM UTC November 14) — EX1550543 final update: Service restored. November 13, 2026, 11:17 PM Eastern (4:17 AM UTC November 14) — MO1550821 final update: Service restored; incident end time listed as November 13, 2026, 4:10 PM UTC (11:10 AM Eastern).

Status: Restored at verification time, November 14, 2026, at about 12:54 AM Eastern. Active incidents on the board: 0.

Sources: Microsoft 365 Service Health Status, status.cloud.microsoft, final business updates November 13, 2026 at 11:15 PM and 11:17 PM ET, Downdetector Microsoft 365, November 14, 2026, Downdetector Outlook, November 14, 2026