Microsoft 365 Users May Be Unable to Connect, Company Says

A Microsoft 365 outage was still listed as a service degradation on the evening of 12 November 2026, according to a fresh check of Microsoft’s public service health page at 20:19 UTC (20:19 GMT). The page still listed the issue as open. It was last updated at 19:30:36 UTC (19:30:36 GMT), with a further update due by 22:00 UTC (22:00 GMT). The company has not marked the incident resolved.

The status page says: “Users may be unable to connect to multiple Microsoft 365 services.” It lists potentially impacted services as Exchange Online, Microsoft Teams, SharePoint Online, Microsoft Copilot 365 and Microsoft Defender XDR. On Azure, the same page says: “No Azure issues detected at this time.”

The latest post from Microsoft 365 Status on X, at 19:50:31 UTC (19:50:31 GMT), says: “We’re testing a configuration change to address a problem that’s causing servers to fail automated health checks and become unavailable. In parallel, we’ve initiated a restart of all affected servers and are monitoring health as they return to service. More info under EX1550543.”

What Microsoft has said so far

The public status page’s current-status wording, still showing at 20:19 GMT, is: “We’re aggressively pursuing all pathways to reduce impact. As a precaution, we’ve paused all deployments and configuration changes while we review recent changes for any correlation to this event. We’ve determined that the elevated load isn’t driven by an overall increase in traffic, but by a large number of servers being unexpectedly unavailable, which is shifting load onto the remaining infrastructure. We’re investigating what’s causing these servers to become unavailable while we work to safely return them to service.”

It also says the issue “may affect users attempting to access the affected Microsoft 365 services.” TSN is adding no cause beyond that wording.

The X account’s thread under incidents EX1550543 and MO1550821 started earlier in the afternoon. At 17:54:26 UTC (17:54:26 GMT), Microsoft said it was investigating issues accessing Exchange Online mailboxes through multiple connection methods in the Americas. At 18:07:33 UTC (18:07:33 GMT), it said the issue may affect Microsoft 365 service connectivity for users in any region, with more information under EX1550543.

At 18:35:36 UTC (18:35:36 GMT), the company said “a portion of infrastructure is experiencing elevated load across multiple regions, which is likely contributing to the connectivity errors,” and pointed to EX1550543 and MO1550821. At 18:48:50 UTC (18:48:50 GMT), it said it had “begun redistributing connection traffic across our broader worldwide infrastructure to help balance the load.” At 19:12:31 UTC (19:12:31 GMT), it said it had paused all deployments, was moving additional traffic off the affected infrastructure, and was restarting affected servers. At 19:31:21 UTC (19:31:21 GMT), close to the status-page timestamp, it said the elevated load “isn’t driven by an increase in traffic, but by a number of servers being unexpectedly unavailable; straining the remaining infrastructure.”

Those posts describe unavailable servers, health-check failures, a configuration-change test and restarts. They make no mention of an attack, and this article infers none.

A separate Teams incident was already resolved

A different incident, TM1550488, should not be folded into the same event. At 15:40:09 UTC (15:40:09 GMT), @MSFT365Status said it was investigating issues when accessing or using Microsoft Teams functionality in North America, under TM1550488. At 17:09:30 UTC (17:09:30 GMT), the same account said: “Our mitigative actions have successfully restored service health and functionality. Customer impact is now fully resolved. Additional information can be found under TM1550488 in the Microsoft 365 admin center.”

That Teams incident was therefore declared fully resolved more than 40 minutes before Microsoft opened the later Exchange Online investigation under EX1550543. The company has not presented TM1550488 as the cause of the still-open degradation.

Microsoft 365 itself is the product at issue. TSN has also covered other recent Microsoft cloud and Copilot developments, including external key control and sovereign cloud, the Copilot agent harness opening to developers via Foundry, and Volkswagen’s Microsoft Copilot rollout. Those posts are about product and cloud-control news, not about this outage, but they are the nearest recent TSN accounts of the same Microsoft 365 services now listed as potentially impacted.

Analysis

The useful status fact, as of 20:19 GMT, is that the incident is still open. Microsoft’s public page still shows a service degradation, last updated at 19:30:36 GMT, and the company’s own X account was still describing tests, restarts and health-check failures at 19:50:31 GMT. A next official update is scheduled by 22:00 GMT. Until Microsoft says otherwise, this should be treated as an ongoing incident, not a past one.

The company’s own account should also be left as it is. Microsoft has said a large number of servers became unexpectedly unavailable, that this shifted load onto the remaining infrastructure, and that the elevated load is not coming from an overall increase in traffic. Later, it said servers were failing automated health checks, that a configuration change was being tested, and that a restart of affected servers had begun. Those sentences are as far as the evidence from Microsoft goes. No other cause is being added here.

The earlier Teams incident, TM1550488, is a warning against collapsing the day into a single story. Microsoft declared that North America Teams issue fully resolved at 17:09:30 GMT, under a different incident ID, before the Exchange Online and wider Microsoft 365 connectivity issue was first posted at 17:54:26 GMT. Readers checking the admin centre should look at EX1550543 and MO1550821 for the open event, and should not treat the resolved TM1550488 notice as a close-out of the later degradation.

Sources

• Microsoft service health status, checked at 20:19 UTC (20:19 GMT) on 12 November 2026. Last updated 19:30:36 UTC (19:30:36 GMT); next update by 22:00 UTC (22:00 GMT).
• Microsoft 365 Status on X, 19:50:31 UTC (19:50:31 GMT), 12 November 2026, EX1550543.
• Microsoft 365 Status on X, 17:54:26 UTC (17:54:26 GMT), 12 November 2026, opening EX1550543.
• Microsoft 365 Status on X, 17:09:30 UTC (17:09:30 GMT), 12 November 2026, TM1550488 declared fully resolved.

Related stories

• Microsoft Makes External Key Control GA as Sovereign Cloud Expands is the nearest recent TSN account of Microsoft’s wider cloud-control work, though it is not about this outage.
• Microsoft Opens Its Copilot Agent Harness to Developers via Foundry
• Volkswagen Gives Microsoft Copilot to More Than 330,000 Staff, Microsoft Says