Skip to content

Microsoft 365 outage MO1550821: Safe Links and Defender hit

Microsoft 365 Exchange Defender Purview

Microsoft 365 incident MO1550821 ran from 16:20 UTC on 12 November to 16:10 UTC on 13 November 2026, and Microsoft's preliminary post-incident report of 15 November says "a latent defect caused Windows servers to become overwhelmed and unresponsive". Microsoft 365 admins and SOC teams should review Defender, Purview DLP and Audit for that window, and hunt for fake "Outage" service health emails that, per Microsoft's Security blog of 16 November, hit organisations "across multiple sectors worldwide" from 13 November.

Updated 17 November 2026: Microsoft's full analysis of the outage phishing

Microsoft Security published its analysis on 16 November: "On November 13, 2026, Microsoft Threat Intelligence observed a coordinated, high-volume phishing campaign targeting organizations across multiple sectors worldwide." Microsoft's assessment: "the activity was likely credential phishing; however, the available evidence does not confirm credential capture, malware delivery, or post-compromise activity", and it "has not attributed the campaign to a named threat actor or malware family". For tenants with Defender for Office 365, Microsoft says messages "are currently blocked/quarantined, and we have not observed any indicators of compromise from this attack." New details: display names use a three-character prefix (examples "MSF Outage Notification", "AMZ Service Health"); the example subject is "Outage – aF7vG6", written with an en dash, so a hunt for "Outage -" with a hyphen can miss it (our query below now matches on "Outage"); the buttons read "RESTORE MESSAGES" or "TAKE ACTION"; "no QR codes or non-EML attachments were observed". Microsoft also lists outagefixed[.]sbs and outagerestored[.]sbs as destinations next to reallifeaccounting[.]com, and other subject patterns starting "Strengthen" and "Restore" in its indicator table. Microsoft's steps, in its order: search for and remove the messages; identify users who clicked; for those users reset the password, revoke sessions and refresh tokens, check MFA registrations, sign-ins, OAuth consents, new inbox or forwarding rules and delegate permissions; block or closely monitor the infrastructure ("Avoid broadly blocking shared email-delivery infrastructure based only on this campaign"); remind users to check service health in the Microsoft 365 admin center. Microsoft's own Advanced hunting queries are in the post; use them as published. Next step: the hunt in "How to check" below.

Updated 16 November 2026 (evening): phishing campaign uses this outage

Microsoft Threat Intelligence reports "an active phishing campaign exploiting the Microsoft 365 service disruption on November 12". The emails "impersonate Microsoft 365 service health notifications and reference the legitimate Exchange Online incident EX1550543" and say held messages "will be deleted within 24 hours unless recipients click to restore them". Subjects start with "Outage -" and a six-character code; sender display names end in "Outage Notification" or "Service Health". Sending domains named by Microsoft: moments-notice[.]com, planetmaison[.]com, newbooker[.]com; SendGrid tracking links redirect to reallifeaccounting[.]com. Microsoft says the activity "is consistent with credential phishing, although credential collection and malware delivery have not been confirmed", and SecurityWeek reports Microsoft later said its security products were blocking the campaign. Microsoft's steps: hunt in Advanced hunting (EmailEvents, EmailUrlInfo, UrlClickEvents) or Threat Explorer, check your Safe Links policies, and confirm outages only in the Microsoft 365 admin center, never from a link in an email. The cause of the outage itself is unchanged: Microsoft calls it "a technical issue not related to cyber or AI / agents". Next step: the hunt in "How to check" below.

Updated 16 November 2026: preliminary post-incident report, new cause

Microsoft's preliminary post-incident report for MO1550821 (also listed as EX1550543), dated 15 November 2026, gives the cause as "a latent defect caused Windows servers to become overwhelmed and unresponsive", described as "lock contention inside an internal Windows process" on the Microsoft 365 networking gateway servers. The change that carried the defect started deployment in July 2026; per the report it was triggered after a Teams failover about 15 hours before the outage, with nearly 14% of gateway capacity already out of service. Impact window, per the report: Thursday 12 November 2026, 16:20 UTC, to Friday 13 November 2026, 16:10 UTC. This replaces the cause Microsoft gave on 13 November (previously: "an issue during an earlier network capacity upgrade that surfaced following a recent network change"). The report asks no action of customers and describes an operational defect, not an attack. Microsoft says the final report follows within five business days of full resolution; its list of repair items is dated 20 November 2026. We read the report as reproduced by Office Watch and summarised by 365Fanatic and GBHackers; the original is in your admin center under Health > Service health > MO1550821 (or Post-incident reports). Next step: the review of the window below, now with exact times.

Updated 14 November 2026: the incident is no longer on Microsoft's status page

MO1550821 was not on Microsoft's public status page. When checked at 05:43 and 08:21 UTC on 14 November, the page's feed had one item only, "Microsoft Admin Center" with the status "Available"; MO1550821 is not in it. We have not found Microsoft's own "resolved" wording on a public page, and the post-incident report is still pending; check Service health > MO1550821 in your admin center for the final status in your tenant. Next step: the review in "How to verify" below.

Updated 13 November 2026: Microsoft names the cause; broad recovery, not yet resolved

Microsoft's status page, updated at 17:57 UTC on 13 November, still shows "Service degradation" but says: "We are seeing broad recovery and stability across our services. This was a technical issue not related to cyber or AI / agents." Cause, in Microsoft's words: "The incident was introduced by an issue during an earlier network capacity upgrade that surfaced following a recent network change." Microsoft says it has "addressed the underlying issue" and continues "to restore service to remaining customers and regions", with "a full post-incident report" to follow. The Defender for Office 365 line has changed: Microsoft now lists "delays or failures in policy evaluation and governance action enforcement" for experiences "that rely on Purview DLP/Information Protection signals" (previously: failures in Safe Links, Safe Attachments, Quarantine and Threat Explorer; those lines are no longer on the page). Next update from Microsoft: "Friday, November 13, 2026, at 8:00 PM UTC". For your review after resolution: keep DLP, auto-labelling and Audit gaps for 12 and 13 November on the list, and check that Defender for Office 365 policy actions (quarantine, DLP enforcement) applied in that window.

Runbook card

What changes: a Microsoft 365 service degradation from 12 November 2026, 16:20 UTC, to 13 November 2026, 16:10 UTC, caused by "a latent defect" on Microsoft's gateway servers per the preliminary post-incident report of 15 November (previously: not listed on the public status page on 14 November; "broad recovery" on 13 November). On 13 November Microsoft listed the Defender portal, Purview (DLP, auto-labelling, Audit, eDiscovery), Defender for Office 365 policy evaluation that relies on Purview DLP signals, and intermittent Intune enrolment, check-in and compliance impact (previously also Safe Links, Safe Attachments, Quarantine and Threat Explorer failures).
Who: Microsoft 365 admins, SOC teams and help desks; since 16 November also anyone who received an "Outage" email citing EX1550543 (a campaign Microsoft saw from 13 November "across multiple sectors worldwide").
By when: now: the review of the window 12 November 16:20 UTC to 13 November 16:10 UTC. Status: preliminary post-incident report of 15 November 2026; final report expected within five business days of resolution (previously not on the public status page on 14 November; "broad recovery" at 17:57 UTC on 13 November).
Do this: During the incident: 1. Follow status.cloud.microsoft, because admin center pages may not load. 2. Hunt from your SIEM copy of Defender and Exchange logs while the Defender portal and Threat Explorer are unreliable. 3. Do not mass-release quarantine or bypass Safe Links or DLP policies to get mail moving. 4. Now: hunt for the fake "Outage" notices (sender domains and query in "How to check"); for anyone who clicked, reset the password, revoke sessions and check inbox rules and OAuth consents, as Microsoft advises; tell users that service health notices never come by email with a restore link, review alerts, DLP and Audit for the incident window, confirm the final status under Service health > MO1550821, and read Microsoft's Post-Incident Report when it is published.
Check: status.cloud.microsoft > Microsoft 365 (Business or Enterprise) > Show details; in the admin center (if it loads): Health > Service health > MO1550821.
Source: Microsoft Security blog, 16 November 2026 (phishing campaign, read 17 November); Microsoft's preliminary post-incident report of 15 November 2026 (as reproduced by Office Watch, read 16 November) and Microsoft's status page (status.cloud.microsoft), read 13 and 14 November 2026.

What Microsoft says

On 13 November, Microsoft's public status page showed Microsoft 365 (Business or Enterprise) in "Service degradation" and explained that it posts there "because Microsoft 365 administrators may be unable to access the admin center to get Service health information". The incident id MO1550821 is the one Microsoft's Microsoft 365 Status account points admins to in the admin center.

According to the status page on 13 November, "Features of the Microsoft 365 services below that interact with Exchange Online and email services are impacted. Elements of those services that do not depend on interaction with Exchange Online remain functional." The security-relevant lines, quoted:

  • Exchange Online: "Users may be unable to access their mailbox using Outlook on the web, Outlook desktop (MAPI), Exchange ActiveSync (EAS), or REST-based connections, and email delivery may be delayed."
  • Defender for Office 365: "Failures may occur for scenarios including access to Safe Links, Safe Attachments, protection and submission policies, and attempts to view Quarantine, Threat Explorer, and Email remediation events." Also "delays may occur for Tenant Allow / Block list changes, unified Role-Based Access Control, reporting, message traces, content extraction, and outbound protection", and "Users clicking on wrapped/rewritten URLs typically processed by Safe Links will result in a failure to navigate, as Safe Links fails to process it."
  • Defender XDR: "Users may be unable to load Microsoft Defender portal pages or solution tabs."
  • Purview: Authorization, "auto-labeling", "Data Loss Prevention (DLP) across Microsoft 365 services", Communication Compliance, label policies, RBAC and Data Classification "are impacted"; "Audit searches, protected content creation, eDiscovery tasks such as search and export, Data Classification and On Demand Scan features may also be impacted." Users "may be unable to open or load Microsoft Purview portal pages or protected content."
  • Intune: "Scenarios including device enrollment, device check-in, and device compliance policies may have been intermittently impacted."
  • Microsoft 365 admin center: "Admins may be unable to load some admin center pages."

The page also lists, among others, Copilot, Teams (calendar and scheduling scenarios), SharePoint Online external sharing, Planner, To Do, Power Apps, Power BI, Universal Print and Windows 365 (tenants using Purview Customer Key).

Status as of 07:29 UTC on 13 November (see the updates at the top for the later status and the phishing campaign that followed), in Microsoft's words: "We're seeing positive results for server stability after applying an upstream authentication/routing configuration component patch to a portion of our infrastructure." Microsoft adds: "As of now, we are not aware of any malicious activity that is causing this incident", and says a Post-Incident Report with the root cause will follow once it is mitigated. At that time Microsoft gave its next update as "Friday, November 13, 2026, at 8:30 AM UTC".

What is not known

  • The final root cause analysis. The 15 November report is preliminary; Microsoft's final report and full list of repair items are still to come (repair list dated 20 November 2026).
  • Whether the phishing campaign collected credentials or delivered malware. Microsoft says "the available evidence does not confirm credential capture, malware delivery, or post-compromise activity" (16 November).
  • Whether any mail that should have been blocked by Safe Links or Safe Attachments was delivered during the window. Microsoft has not said; that is what the review of the incident window is for.

How to check

Read-only. Where the admin center or Defender portal does not load, these checks may also fail; the status page is the fallback.

# Service health for MO1550821 through Microsoft Graph (read-only scope)
Connect-MgGraph -Scopes ServiceHealth.Read.All
Get-MgServiceAnnouncementIssue -ServiceHealthIssueId MO1550821 |
  Select-Object Id, Title, Status, StartDateTime, LastModifiedDateTime

Hunt for the outage-themed phishing in Defender Advanced hunting (read-only query; domains from Microsoft Threat Intelligence; Microsoft's own queries are in its 16 November post). The subject filter matches "Outage" with any dash, because Microsoft's example uses an en dash ("Outage – aF7vG6").

let badDomains = dynamic(["moments-notice.com", "planetmaison.com", "newbooker.com"]);
EmailEvents
| where Timestamp > datetime(2026-11-12)
| where SenderFromDomain in~ (badDomains) or Subject startswith "Outage"
| project Timestamp, NetworkMessageId, RecipientEmailAddress, SenderFromAddress, Subject, DeliveryAction, DeliveryLocation
| join kind=leftouter (UrlClickEvents | where Timestamp > datetime(2026-11-12)
    | project NetworkMessageId, ClickTime = Timestamp, Url, ActionType, IsClickedThrough) on NetworkMessageId

Also search UrlClickEvents and EmailUrlInfo for reallifeaccounting.com, outagefixed.sbs and outagerestored.sbs. The startswith "Outage" filter also returns real mail with that word; read the sender before acting. Any recipient who clicked through: follow Microsoft's steps (reset the password, revoke sessions and refresh tokens, review MFA registrations, sign-ins, inbox and forwarding rules and OAuth consents). In Threat Explorer, the same filter is Sender domain or Subject.

In your SIEM, keep the Defender and Exchange tables you already export (for example EmailEvents, UrlClickEvents, AlertInfo in Microsoft Sentinel) as the working view of the window from 12 November, rather than the Defender portal. Expect gaps or late events for this window, because Microsoft lists reporting delays.

How to verify

Now that the public status page no longer lists MO1550821, check its final status in your admin center (Health > Service health), then confirm that Safe Links clicks resolve again, that Tenant Allow/Block changes made during the incident have applied, and that quarantine releases you attempted during the incident completed. Then compare alerts, DLP matches and Audit records for 12 November 16:20 UTC to 13 November 16:10 UTC with a normal day. We will add an "Updated" note here when Microsoft publishes the final post-incident report.

Impact and rollback

Nothing above changes a tenant. The changes to avoid during the incident are the ones that weaken protection to get mail moving: turning off Safe Links or Safe Attachments policies, broad Tenant Allow entries or mass quarantine releases. If you make one, write it down so it can be reversed.

Related: our Microsoft 365 hardening kit (the baseline to re-check after the incident), Exchange Online protection kit (Safe Links and Safe Attachments policies), dated actions on Microsoft 365 security deadlines and more Email & collaboration news.

Sources

Last reviewed: 17 November 2026. Runbook Lab is not affiliated with Microsoft.