CyberKit

Threat intel / Techniques and trends

Fake Microsoft 365 outage notices push users to a "Restore Messages" link

Phishing emails pose as Microsoft 365 service-health notices, claim mail was held during an outage, and send recipients to a non-Microsoft page to restore it.

Medium severity. Active. Moderate confidence. First reported 13 Nov 2026, last activity 13 Nov 2026. Briefing updated 18 Nov 2026.

AI-written summaries of public reporting, each checked against at least two sources from different publishers. Check the sources before you act. Last refreshed 2026-11-18 14:09 UTC. How this is made.

What is not settled: The facts come from Microsoft's November 16 post, read through a summarizing fetch rather than line by line. Mimecast's post was seen only as a search excerpt, and it matches the lure, the button labels and the sender pattern, so it corroborates the campaign and adds no facts here. One search excerpt says Microsoft reported the campaign on November 14. The post itself is dated November 16 and gives November 13 as the observation date, so this briefing uses those. Microsoft names no sector, region, actor or victim count. The indicator tables are not reproduced here. CISA's catalog was not needed for this item, since no CVE is named.

In plain words

What happened

Attackers sent emails that look like Microsoft 365 notices. The emails say some messages were held during a service problem and will be deleted within 24 hours unless the person acts. The button leads to a page that is not run by Microsoft.

Who is behind it

Microsoft does not name a group or a tracking name for this campaign.

What they want

Microsoft does not state a goal. It assesses the campaign as most likely credential phishing, with the aim of getting people to type in their sign-in details.

What they did

Microsoft saw emails with a link and a button labelled "RESTORE MESSAGES" or "TAKE ACTION". Each link carried a tracking address for the recipient and redirected to a destination outside Microsoft. Microsoft found no malware attached or delivered.

Who is at risk

Anyone with a Microsoft 365 mailbox, across several industries. Microsoft did not name a sector or region.

What to do

  • Tell staff that Microsoft posts outage updates on the Service health page in the Microsoft 365 admin center, and does not ask people to click to restore mail.
  • Search mail for the sender domains, subject lines and display names Microsoft lists, then quarantine matching messages.
  • Find anyone who clicked, and check their sign-in logs for new or unusual access.
  • Reset passwords, revoke sessions and review MFA methods, inbox rules and OAuth grants for any account that may have been entered.
The technical version, for hunting and patching

What happened

Microsoft describes a high-volume campaign of phishing emails that imitate Microsoft 365 service-health notices. The emails use randomized subjects that begin with "Outage" and display names with an organization-style prefix followed by "Outage Notification" or "Service Health". One sample cites an Exchange Online incident on November 12 and says four messages were held.

Who is behind it

No actor is named and no tracking name is given. Microsoft did not attribute the campaign to a named threat actor or malware family.

What they want

Microsoft's assessment is likely credential phishing. It did not confirm credential capture, malware delivery or post-compromise activity.

What they did

Microsoft observed spearphishing links (T1566.002) presented as a user action (T1204.001), with recipient-specific tracking URLs that redirect to a non-Microsoft destination. The sender domains share a cluster. No QR codes, non-EML attachments, or executable, archive or document payloads were seen. Microsoft maps the campaign to masquerading (T1036).

Who is at risk

Mailboxes protected by MFA that is not phishing-resistant, and accounts where an adversary-in-the-middle page could capture a session. Microsoft notes that shared email-delivery infrastructure can cause false positives, so block only the campaign's own destination.

What to do

  • Use the indicator tables in Microsoft's post, and check them against mail telemetry before blocking. Shared delivery infrastructure can cause false positives.
  • Require phishing-resistant MFA, and enable Safe Links, Safe Attachments and zero-hour auto purge.
  • Run user-reporting and attack-simulation training that covers service-health lures.
  • For any suspected account, check suspicious sign-ins, OAuth grants, forwarding rules and delegate permissions before closing the case.

ATT&CK techniques

Sectors: Multiple. Regions: Global.

Open next

Sources

Revision history

  • 2026-11-18: First published.

Newer: SCKit abuses ScreenConnect to reach MSP customer machines. Older: GSocket keeps attackers on compromised Linux servers after patching.