How to Clear a Microsoft 365 Outage Without the Phish

Nighttime data-hall aisle with cable bundles and distant amber lights

IT managers clearing a Microsoft 365 outage should confirm status in the admin center, hunt mail citing EX1550543, and drain delayed mail without a restore click. Expert Insights reported that Microsoft’s preliminary post-incident report, published November 16, traces the outage to a July gateway defect, a routine Teams failover, and reduced capacity. SecurityWeek reported Microsoft’s Friday statement that the failure was a technical issue, not a cyberattack, while attackers already cited that incident ID in phishing mail.

Updated November 16, 2026

Key Takeaways

  • Confirm EX1550543 in the Microsoft 365 admin center.
  • Some Nov. 13 messages threatened deletion within 24 hours.
  • Mail was not lost; the timeout was extended to 48 hours.
  • More than 80 percent of gateway servers were unresponsive.

What should you verify first after a Microsoft 365 outage?

Check the Microsoft 365 admin center for MO1550821 and EX1550543. SecurityWeek reported the Exchange Online incident was marked resolved on November 13. Charles Lamanna, executive vice president of Copilot, Agents and Platform, posted an abridged root-cause account on X and urged customers to use the admin center.

Office Watch reproduced a preliminary report dated November 15. Impact ran from 4:20 p.m. UTC on November 12 to 4:10 p.m. UTC on November 13. Most users could not open mailboxes, and delivery was delayed. Microsoft said, “This was a technical issue not related to cyber or AI / agents.”

Neither the defect nor the fix applies to broader Windows deployments. Do not hunt this bug on user devices.

How do you separate status from outage-themed phishing?

Microsoft Threat Intelligence observed a campaign posing as Microsoft 365 service health notices and citing EX1550543. In some messages detected on November 13, recipients were falsely told held mail would be deleted within 24 hours unless they clicked a link. Expert Insights reported Microsoft extended the email timeout to 48 hours on November 13, and Office Watch reported email was not lost.

Check Admin center Phishing mail
Channel Microsoft 365 admin center, EX1550543 and MO1550821 Email posing as a service health notice
Claim Technical issue; EX1550543 marked resolved November 13 Some messages: held mail deleted within 24 hours unless the user clicks
Label Details in the admin center; abridged account also on X Subject starts with “Outage -” and a six-character code
Sender Not an email Display name ends in “Outage Notification” or “Service Health”

Recipient-specific SendGrid tracking links redirected to reallifeaccounting.com. Similar messages targeted organizations across several US sectors. Microsoft said the activity is “consistent with credential phishing, although credential collection and malware delivery have not been confirmed,” and later reported its security products were blocking the campaign.

  1. Search for subjects that start with “Outage -” and a six-character code, and for EX1550543 outside the admin center.
  2. Flag display names that end in “Outage Notification” or “Service Health.”
  3. Inspect moments-notice.com, planetmaison.com, newbooker.com, and redirects to reallifeaccounting.com.
  4. Confirm the incident in the admin center. Do not use a mailed restore link.

How do you drain delayed mail without a restore click?

There is nothing to fix on a PC, Mac, or phone. The bug was in a Windows fix made only for gateway servers.

  • Expect delayed inbound mail, not bounces. On November 13 Microsoft extended the timeout to 48 hours so delayed mail would be preserved.
  • Check the desktop Outlook Outbox. Outgoing messages should have stayed there until the connection returned.
  • Outlook mobile apps may have failed to send Thursday or Friday messages.
  • If important Thursday or Friday mail has not been acknowledged, check with the recipient.
  • If a mailbox is still unreachable, recheck EX1550543. Expert Insights reported that on November 14 remaining impacted customers and regions were restored.

Which shared-gateway dependencies should you map next?

About 15 hours before impact, Teams failed over to the primary gateway shared with Exchange Online. Microsoft said that failover is part of normal operations; it raised load and changed traffic patterns. Nearly 14 percent of capacity was already out and, alone, had no impact.

With the July lock-contention defect, automatic rerouting spread the same load until more than 80 percent of gateway servers were unresponsive in under two hours. A separate issue Microsoft did not describe kept bulkheads from containing the cascade.

Teams, OneDrive, SharePoint, and Office apps could leave that gateway and recovered earlier. Teams chats and meetings worked for most of the outage. Exchange Online could not, and Microsoft did not say why.

The Hindu BusinessLine reported email-support disruptions at IndiGo, Air India, and Akasa Air; flight operations were not reported affected, and Air India temporarily rerouted email. Map mailbox access and the Exchange-backed parts of Copilot, Teams, SharePoint, OneDrive, Defender, and Purview. The same dependency question sits behind acquisition-era systems that widen blast radius.

Lamanna said a fuller review would follow later this week. Office Watch said longer-term fixes are due by November 20, 2026. Until that review, keep the dependency list current and confirm status in the admin center.

Frequently asked questions

Was the Microsoft 365 outage a cyberattack?

Microsoft said on Friday it was a technical issue not related to cyber or AI / agents. Attackers later sent phishing that cited the real incident ID.

Where should admins confirm Microsoft 365 status?

In the Microsoft 365 admin center under EX1550543 and MO1550821. Microsoft advised verifying incidents directly there, and Lamanna posted an abridged account on X.

Was email deleted during the outage?

No. Office Watch reported email was not lost, and Microsoft extended the delivery timeout to 48 hours on November 13.

What did the outage phishing emails claim?

Some November 13 messages falsely said held mail would be deleted within 24 hours unless the recipient clicked a link. Subjects began with “Outage -” and a six-character code.

Notice an error?

Help us improve our content by reporting any issues you find.