Outlook Outage EX1550543: What IT Teams Should Do Now
By Chuck Lerch, Founder and CEO, Cyberuptive ·
Microsoft is working an Exchange Online incident, EX1550543, in which users may be unable to connect to their mailboxes through Outlook on the web, MAPI, Exchange ActiveSync, and REST API connections (UptimeRobot incident timeline). Confirm impact in the Microsoft 365 admin center, tell users through a channel that does not depend on Outlook, and do not mass-reset passwords or rebuild profiles unless Microsoft directs it (Microsoft Q&A guidance). Expect outage-themed phishing while users are primed to “fix” their email.
The incident began around 16:17 UTC on Thursday, November 12, 2026, and Microsoft later opened a broader incident, MO1550821, covering Microsoft 365 services (UptimeRobot incident timeline). Reuters, citing Downdetector, reported more than 130,000 Outlook problem reports at 1:27 p.m. ET, along with more than 46,000 reports for Microsoft 365 (Reuters via CNA). This post reflects Microsoft’s public updates through 18:43 UTC. Check the service health dashboard for the current state before acting on anything here.
What are the key takeaways?
- The problem is on Microsoft’s side: connectivity errors on Exchange Online infrastructure that receives and processes users’ access requests (UptimeRobot incident timeline).
- Microsoft reported elevated load across multiple regions and was reviewing an unexpected increase in a specific type of service traffic (Deadline).
- Avoid local “fixes” such as bulk password resets or profile rebuilds unless Microsoft calls for them (Microsoft Q&A guidance).
- Treat any message about the outage, mailbox quota, or reauthentication links as suspect until verified.
- Record the incident IDs, timeline, and business impact now. You will want them for continuity reviews, customer questions, and contract conversations.
What has Microsoft said so far?
Microsoft first said users may be unable to access their mailboxes and listed the affected connection methods: Outlook on the web, MAPI, Exchange ActiveSync (EAS), and REST API (UptimeRobot incident timeline). Its public post on X referenced EX1550543 for admins tracking the issue in the admin center (NBC10 Philadelphia).
By 17:45 UTC, Microsoft said it had identified connectivity errors on a portion of the infrastructure that receives and processes access requests, and that it had collected networking logs (UptimeRobot incident timeline). At 18:19 UTC it reported elevated load across multiple regions, said it was restarting and repairing impacted infrastructure, and said it was evaluating options to redirect traffic to alternate infrastructure (Deadline). Later updates said some US traffic was redirected, that affected servers were intermittently unavailable and adding strain, and that Microsoft was redistributing Outlook connection traffic while reviewing recent changes (UptimeRobot incident timeline).
Reuters also reported that Microsoft had fixed a separate Teams disruption affecting North American users earlier in the day (Reuters via CNA). This also comes three days after two separate Exchange Online issues on November 9, one of which involved Outlook on the web connection terminations in Europe (UptimeRobot).
What should IT teams do while it is ongoing?
- Confirm before troubleshooting. Check Health > Service health for EX1550543 and MO1550821 before opening tickets on individual devices. Microsoft directs admins to the admin center first and to use “Report an issue” only if no incident is listed (Microsoft Q&A guidance).
- Communicate out of band. Send one short status note through Teams (if it is working for you), SMS, your intranet, or a phone tree. Name the incident, say that IT is monitoring, and say what users should not do.
- Freeze bulk changes. Hold off on password resets, MFA re-registrations, profile rebuilds, and client reinstalls tied to this symptom (Microsoft Q&A guidance). They add help desk load without fixing a service-side fault.
- Keep sensitive data in approved channels. Users under deadline pressure may forward work to personal email or consumer file sharing. For organizations handling CUI, PHI, or cardholder data, that workaround can become a reportable problem of its own. Tell staff which alternate channel is approved.
- Use your continuity plan. Identify which processes stop when email stops: invoicing, order intake, ticket notifications, MFA by email, and vendor coordination. Switch to the documented alternates.
Why does an outage raise phishing risk?
Outages give attackers a believable pretext. Expect messages and texts that claim to restore mailbox access, ask users to “re-verify” their Microsoft 365 account, or impersonate the help desk. They work because users already expect something to be wrong. Remind staff that IT will not ask for passwords or MFA codes. Point them to one known-good place for updates. Ask your security operations team to watch for new inbox rules, unusual OAuth consent grants, and sign-ins from unfamiliar locations in the days after service returns.
What should you check once service returns?
- Test mail flow in both directions and review message trace for delayed or deferred messages.
- Confirm mobile devices using Exchange ActiveSync and any applications using REST or Graph-based mail access have resumed syncing.
- Verify that your audit and sign-in logs cover the incident window without gaps. Our guide to Microsoft 365 incident logs covers which records to check.
- Confirm your break-glass accounts still work and that admins could reach them during the outage. See how to test emergency access accounts.
- Save the Microsoft post-incident report when it is published, along with your own timeline of business impact, for SLA review and your next continuity exercise.
If this outage exposed that your only copy of critical mail and files lives inside one tenant, it is a good time to review backup coverage. Our cloud backup tenant review walks through what to check. If you want an outside team on Microsoft 365 configuration and monitoring, see our Microsoft 365 and Azure security service.
Frequently asked questions
Is the November 12 Outlook outage a cyberattack?
Microsoft has not described it as one. Its updates point to connectivity errors on Exchange Online access infrastructure, elevated load across multiple regions, and an unexpected increase in a specific type of service traffic that it was investigating (Deadline) (UptimeRobot incident timeline).
Should we reset passwords or rebuild Outlook profiles?
Not because of this incident alone. Microsoft community guidance for service incidents advises against resetting multiple users’ passwords or rebuilding Outlook profiles unless Microsoft directs it (Microsoft Q&A guidance). Mass changes during a provider outage create help desk load and can mask real account problems.
Where should we check status?
Use Health > Service health in the Microsoft 365 admin center and look for EX1550543 and MO1550821. Microsoft also publishes broad incidents at status.cloud.microsoft for people who cannot reach the admin center (UptimeRobot incident timeline).
Will email sent during the outage be lost?
Do not assume either way. After service stabilizes, test inbound and outbound mail flow, ask key correspondents to confirm receipt of time-sensitive messages, and review message trace for delayed or deferred items before closing your internal ticket.
Need help with Microsoft 365 resilience?
Bring your incident timeline, continuity gaps, and tenant configuration questions to a focused review. Schedule a security review or Call 833-92-CYBER to plan for the next provider outage.