Outlook Mailbox Access Problems in the Americas: Microsoft Investigates Exchange Online Incident EX1550543 — Megathread

Timeline: about 20 minutes from complaints to confirmation​

GV Wire, a Fresno-based outlet, posted timestamped updates as the reports came in. All times are Pacific:

Microsoft's statement said it was investigating reports of users having trouble accessing Exchange Online mailboxes "through multiple connection methods in the Americas." It pointed administrators to incident EX1550543 in the Microsoft 365 admin center.

Microsoft's incident record appears to have existed before the social post. A Microsoft 365 status page run by Earlham College listed EX1550543 under the title "Users may be unable to connect to their mailboxes in Exchange Online through multiple connection methods," timestamped 2026-11-12 17:46 UTC. Daylight saving time ended on November 1, so 17:46 UTC is 9:46 a.m. Pacific. That is four minutes before GV Wire's first snapshot. The same page showed Exchange Online in a serviceDegradation state.

That label matters. Microsoft's own service-health documentation defines "Service degradation" as a confirmed issue that might affect use of a service, for example through slowness or intermittent interruptions. "Service interruption" is the more severe status, used when users can consistently be shown to have lost access. At the point captured by the Earlham page, Microsoft was describing a serious degradation, not a declared full outage. The status could have changed later.

Section summary: User reports grew from about 2,400 to more than 65,000 in roughly 18 minutes. Microsoft's incident record carries a 9:46 a.m. PT timestamp, and the public social acknowledgment came at 10:08 a.m.

"Outlook is down" vs. what Microsoft confirmed​

The headlines said Outlook was down. Microsoft said something narrower:

• Service: Exchange Online, the hosted mailbox service that Outlook connects to. Outlook is just the app people see.
• Symptom: users may be unable to connect to their mailboxes.
• Scope: "Multiple connection methods," which suggests more than one way in was affected. Outlook on the web, the desktop app and mobile could all be candidates.
• Geography: the Americas.

Here's what Microsoft did not confirm in the information available so far:

• A root cause
• How many tenants or users were affected
• Whether Teams, OneDrive, Copilot or the Microsoft Store were part of the same incident. The Downdetector reports for those services are users' perceptions, not Microsoft's diagnosis.
• Whether any mail was delayed or lost
• When service was restored

Downdetector counts are crowdsourced complaints, not a measure of how many people were affected. Some of the 65,000 people who reported Outlook problems may have had unrelated trouble. Others who couldn't work probably didn't report anything. The curve shows how quickly the problem was felt, not how big it was.

Why the "all operational" status was misleading​

The status checker said everything was fine at 9:50 a.m., then became unavailable, and Microsoft's public acknowledgment arrived on social media 18 minutes later. This is a familiar pattern. Public status pages are usually the last thing to change, and they're under the most load when people need them.

This is the main practical lesson for IT staff. Microsoft's guidance on checking Microsoft 365 service health sends administrators to Health > Service health in the Microsoft 365 admin center. That page shows tenant-specific incidents, their status and a feed of updates. Microsoft also says that admins who can't sign in to the admin center should check the public service status page and follow the @MSFT365status account on X, the account that carried today's acknowledgment.

What admins should do during this incident​

• Look up EX1550543 in the admin center under Health > Service health. The issue detail page lists affected services, the status, user impact and the latest updates.
• Check the Scope of impact field. It says whether Microsoft considers your organization affected, which a regional Downdetector map can't tell you.
• Subscribe to updates for this incident. Open it, choose Manage notifications for this issue, and add up to two email addresses. If your Exchange Online mail isn't working, use an address that doesn't depend on it.
• Tell users early. A short message such as "Microsoft has confirmed a mailbox access problem in the Americas, and we're tracking it" will save your helpdesk a lot of calls.
• If your tenant isn't listed, use Report an issue on the Service health page. Microsoft says it compares those reports with data from other organizations to decide whether to open a new incident.

The Microsoft 365 Admin mobile app can also show service health with push notifications, which helps if a desk-bound browser session is part of the problem.

What end users should (and shouldn't) do​

When Outlook fails, people tend to start fixing things themselves: rebuilding profiles, reinstalling the app, changing passwords. During a confirmed service-side incident, those steps are unlikely to help and can create more problems once service comes back.

• Don't reset your password or remove and re-add your account because of this incident. Microsoft has described a problem connecting to mailboxes in Exchange Online, not a problem with credentials or local clients.
• Don't assume a different app will work. Microsoft said "multiple connection methods" were affected, so switching from Outlook on the web to desktop or mobile isn't a confirmed workaround.
• Do check with your IT team or the incident ID before troubleshooting, and save urgent messages as drafts or in another document until access returns.
• Do expect recovery to be gradual. In previous Exchange Online incidents, service came back unevenly across users and features.

Context: the second major Outlook disruption in about 10 weeks​

This incident follows a larger one at the end of the summer. On August 31, TechCrunch reported that Microsoft confirmed a widespread, multi-hour outage affecting Outlook users, leading to email delays and failures, authentication issues, and other problems. That incident started in Exchange Online, but Microsoft later said the authentication component was impacting other services beyond Exchange.

It lasted more than a day. TechCrunch reported the next morning that Microsoft's efforts to fix what is now a multi-day outage affecting customers' access to Outlook email and other Microsoft 365 services are entering day two, and that the affected services eventually included SharePoint, Copilot, Teams, Purview, Defender XDR, the Microsoft 365 Admin Center, and Universal Print. Even as mail flow recovered, search functionality remained degraded.

There's no evidence that today's incident has the same cause as the August event, and it would be wrong to assume one. They are separate incidents with separate IDs. Still, the comparison is useful in two ways:

• Complaints about other services don't settle the scope. In August, related impact on other services was confirmed hours into the incident. Today's Downdetector reports for Teams and OneDrive could become part of EX1550543, or they could just be people blaming the nearest Microsoft product. Wait for Microsoft to update the incident before deciding.
• Service restored isn't the end. As August showed, getting back into mailboxes can be followed by a period where search, sync or delivery queues are still catching up.

The bigger picture​

Microsoft 365 concentrates email, chat, files and AI tools on shared infrastructure. That makes it convenient to manage, but a problem in one layer can look to users like an outage of several products. Organizations can't do much to prevent a regional Exchange Online incident. They can control how prepared they are: whether admins check tenant-scoped service health instead of social media, whether service-health alerts go to an address outside the affected system, and whether there's a backup channel ready before email becomes unreachable.

Bottom line: As of Microsoft's latest public statement, EX1550543 is an active investigation into Exchange Online mailbox access in the Americas, listed as service degradation. The root cause, the number of people affected and the recovery time have not been published. Admins should track the incident ID in Service health. Users should hold off on local fixes until Microsoft reports that service is restored.

Update: Microsoft expands incident scope to all regions (November 12, 2026)​

Microsoft now says the connectivity issue may affect Microsoft 365 users in any region, according to an update reported by Mashable at 1:45 p.m. Eastern on November 12. That supersedes its initial description of Exchange Online mailbox access problems in the Americas.

Microsoft also said elevated load on a portion of its infrastructure across multiple regions is likely contributing to the connectivity errors. That is a suspected contributing factor, not a confirmed root cause. The broader warning does not establish that every Microsoft 365 service or region is affected.

Mashable reported that Outlook complaints on Downdetector had exceeded 130,000 by 1:12 p.m. Eastern. That figure represents reports, not a count of affected users.

For administrators outside the Americas, the expanded scope means the incident may also be relevant to their organizations. Microsoft directs admins to incident EX1550543 in the Microsoft 365 admin center for further information. Users experiencing connectivity problems should check with their IT teams before making local changes.

Update: Microsoft investigates mailbox infrastructure errors (November 12, 2026)​

According to Windows Report, Microsoft has identified connectivity errors in part of the Exchange Online infrastructure that receives and processes mailbox access requests. The company is collecting network logs to investigate the source of those errors and determine its next steps.

Windows Report also says Microsoft has acknowledged that some administrators may be unable to access the Microsoft 365 admin center. For those affected, Microsoft is providing updates through an alternative link shared on its official status account.

The report lists Outlook on the web, MAPI, Exchange ActiveSync and the REST API as potentially affected connection methods. That does not establish that every method has failed for every user.

For IT teams, the reported admin-center access issue means the usual route to incident EX1550543 may itself be unavailable. Administrators who cannot reach it can check Microsoft’s official status account for the alternative update link. The infrastructure errors are still under investigation; the report does not establish a confirmed root cause or restoration time.

Update: Report says Teams also experienced interruptions (November 12, 2026)​

According to How-To Geek, Microsoft said Teams and Microsoft 365 also experienced service interruptions during the Outlook disruption. That is a broader claim than the earlier user complaints about Teams, which Microsoft had not confirmed in the information previously available.

The report does not specify which Teams functions were affected, how widespread the interruption was, or whether it shared the same cause as the Exchange Online connectivity errors. Administrators should therefore avoid treating the report as confirmation that Teams problems were part of incident EX1550543.

For IT teams, the reported interruption is a reason to check for Teams-specific service-health updates and user impact as well as the Exchange incident. The report does not establish a restoration time or a confirmed root cause for the mailbox problem.

Update: Microsoft redistributes traffic and pauses deployments (November 12, 2026)​

According to iTnews, Microsoft has completed an initial redistribution of connection traffic across its worldwide infrastructure and is moving more traffic away from affected systems. The company is also restarting affected servers and has paused all deployments while working to reduce the impact.

iTnews reports that Microsoft is investigating whether the elevated traffic reflects a genuine increase in requests or a change in how traffic is being routed. That leaves the underlying cause unresolved.

The outlet also reports that Microsoft’s status page lists SharePoint Online, Microsoft 365 Copilot and Microsoft Defender XDR, as well as Teams, as potentially affected. Those listings indicate possible impact, not that every user or function is disrupted.

For administrators, the traffic redistribution and server restarts are mitigation steps, not confirmation that service has recovered. Teams should continue monitoring service health for their organizations and check the potentially affected services separately.

Update: Microsoft tests configuration change for failing servers (November 12, 2026)​

According to Mashable, Microsoft said at 2:50 p.m. Eastern on November 12 that it was testing a configuration change to address a problem causing servers to fail automated health checks and become unavailable.

That is a new line of mitigation alongside the traffic moves and server restarts already reported. The test does not establish that the change will resolve the disruption, that the failed health checks are the underlying cause, or that service has recovered.

Mashable also reported that Microsoft’s service-health page identified business and enterprise Microsoft 365 customers, rather than users of Microsoft’s consumer products, as affected by the current issues. That distinction narrows the reported customer scope, though it does not mean every business or enterprise tenant is affected.

For IT teams, the configuration test is a reason to watch for further service-health updates before declaring the incident resolved. Administrators should continue checking the impact on their own organizations and services; the report does not provide a recovery time.

Update: Microsoft rules out increased traffic as the source of elevated load (November 12, 2026)​

According to ZDNET, Microsoft said at 2:31 p.m. Eastern that elevated load was not caused by an increase in traffic. Instead, the company said a number of servers had become unexpectedly unavailable, placing additional strain on the remaining infrastructure.

That narrows the investigation described earlier: Microsoft had been examining whether the load reflected more requests or a change in traffic routing. The reported finding does not explain why the servers became unavailable or establish a complete root cause.

ZDNET also reported that Microsoft’s public status page, which had not loaded for the outlet at 2:21 p.m., was accessible again at 3:05 p.m. Its availability does not by itself mean the affected services have recovered.

For administrators, Microsoft’s reported update points to incident EX1550543 and Microsoft 365 incident MO1550821 in the admin center. Microsoft is working to return the unavailable servers to service; the update did not give a restoration time.

Update: OpenAI and Anthropic report Microsoft connector problems (November 12, 2026)​

According to The Independent, OpenAI is investigating a Microsoft connector issue that may prevent new connections from working and cause tools to malfunction. Anthropic said it had identified an issue with an upstream provider affecting its Microsoft 365 connector.

The Independent reports that the connector problems extended from the wider Microsoft disruption. The report does not establish that both issues share the same cause as incident EX1550543 or say when the connectors will be restored.

For organizations using these AI integrations, the reported impact extends beyond accessing mailboxes in Outlook: connected tools may also be unreliable. IT teams should check the providers’ status updates as well as Microsoft’s service-health notices before troubleshooting connector configurations or declaring the integrations recovered.

Update: Additional details (November 12, 2026)​

According to BleepingComputer, Microsoft’s advisory for the broader Microsoft 365 incident, MO1550821, says it began at 1:26 p.m. Eastern. The advisory says customers may be unable to connect to services including Exchange Online, Teams, SharePoint Online, Microsoft 365 Copilot and Microsoft Defender XDR.

BleepingComputer also reports that a separate Teams messaging incident, TM1550488, ran from 9:45 to 10:53 a.m. Eastern and has been resolved. Microsoft has not said whether it is related to the ongoing Microsoft 365 disruption.

Update: Alternative health checks return some servers to service (November 12, 2026)​

According to iPhone in Canada, Microsoft said at 4:01 p.m. Eastern on November 12 that an alternative health-check method had allowed a subset of affected servers to return to service. The company was applying the change more broadly but had not declared the incident resolved or provided a restoration time.

The outlet reports that Microsoft is investigating a component involved in processing automated server health checks and a small number of configuration updates as potential contributors. Neither has been confirmed as the cause. Microsoft also said it had taken steps to prevent additional servers from being removed from service while testing a targeted change to bypass the suspected component.

According to iPhone in Canada, Microsoft is preparing an automated process to detect and restart unresponsive servers while the change rolls out. For administrators, the return of some servers is a sign of progress, not confirmation that Outlook or other affected services have recovered for their organizations. Microsoft’s next public update was due by 5:30 p.m. Eastern.

Update: Microsoft investigates processor usage on affected servers (November 12, 2026)​

According to Forbes Australia, Microsoft is investigating a spike in processor usage on the affected servers. The outlet also reports that Microsoft has found no recent change that aligns with the start of the outage.

Those findings do not establish what caused the servers to fail their health checks. For IT teams, they are additional diagnostic details rather than evidence that service has recovered or that local troubleshooting is needed.

Update: Guelph and Wellington County report municipal service delays (November 12, 2026)​

According to Guelph News, the Microsoft 365 disruption is affecting municipal operations in the City of Guelph and Wellington County, Ontario, with email among the most visibly affected services.

The City of Guelph said it was monitoring the situation and working around the outage. It advised people to call 519-822-1260 if needed, but said its TTY service was down.

Wellington County said Microsoft service disruptions could delay its response times and apologized for the inconvenience. Neither municipality’s statement, as reported by Guelph News, specified when normal service would resume.

For residents, the immediate practical impact is that email replies from the city or county may take longer than usual. Guelph’s phone line is an alternative for those who need to reach the city, although callers who rely on TTY should note the reported interruption.

For IT teams, the municipal reports provide examples of the disruption’s effect on public-facing operations, but they do not establish its full impact across local government services.

Update: Additional details (November 12, 2026)​

Microsoft’s incident updates, mirrored on the University of Pennsylvania’s Microsoft 365 status page, said earlier mitigation actions had not provided the expected relief. A core process on affected servers was becoming overwhelmed, causing them to stop responding.

The mirrored record also gives a preliminary cause for the separate, resolved Teams messaging incident: resource contention in the underlying infrastructure. It says the incident affected users whose Teams services were hosted in or routed through North and South America. Microsoft has not said it was linked to the Exchange disruption.