DEV Community

Ahsan Luqman
Ahsan Luqman

Posted on

How the Microsoft 365 Outage Phishing Campaign Works

By Ahsan

The Microsoft 365 outage phishing campaign is a credential phishing campaign that impersonated Microsoft 365 service health notifications during the Microsoft 365 service disruption of November 2026. Microsoft Threat Intelligence reported the campaign on 14 November 2026, one day after the first messages were detected on 13 November. The messages cited the genuine Exchange Online incident EX1550543, used a subject line that began with the word "Outage" followed by a six-character code, and linked to a sign-in page through SendGrid click-tracking links that redirected to reallifeaccounting.com. Microsoft identified three sender domains, moments-notice.com, planetmaison.com and newbooker.com, and stated that the campaign targeted organisations across multiple sectors in the United States. Microsoft described the activity as consistent with credential phishing and stated that credential collection and malware delivery had not been confirmed.

The outage

On 12 November 2026, a Microsoft 365 service disruption began, affecting Exchange Online, Outlook, Teams and other cloud services. Microsoft stated that there was no indication that malicious activity had caused the failure. On 13 November, Microsoft traced the cause to an issue during an earlier network capacity upgrade and described the failure as a technical problem not related to cyber or AI agents. Early on 14 November, Microsoft stated that service had been restored to the remaining impacted customers and regions. Microsoft assigned two incident references to the disruption: EX1550543 for the Exchange Online incident and MO1550821 for the wider Microsoft 365 disruption.

The lure

The messages imitated the layout of Microsoft 365 service health notifications. The subject line began with the word "Outage" followed by a six-character code, and the sender display name combined the recipient organisation's own name with "Outage Notification" or "Service Health". The body of the message stated that four messages had been held during the outage and would be deleted within 24 hours unless the recipient clicked a "RESTORE MESSAGES" button. The message quoted the incident identifier EX1550543, which matches the identifier Microsoft assigned to the genuine Exchange Online incident. Field Effect, a security firm, reported that the button led to a page built to collect sign-in details.

The incident identifier appeared in news reporting of the outage and in the Microsoft Threat Intelligence warning, and copying it required no access to Microsoft systems. The display name carried the recipient organisation's own name, which placed a familiar name in the sender field while the address behind it belonged to one of the three sender domains. The 24-hour deletion claim set a deadline on the message, and Microsoft announced no such retention policy in its warning. The held-messages claim also matched the experience of recipients, because mail sent during the disruption did arrive late.

The redirect chain

Microsoft identified three sender domains for the campaign: moments-notice.com, planetmaison.com and newbooker.com. The links in the messages were recipient-specific SendGrid click-tracking links, which rewrite the destination address to a tracking address that records the click and then redirects to the final page. The tracking links redirected to reallifeaccounting.com, with the path /themelist0.html observed in the warning. The address shown in the message therefore belonged to SendGrid's tracking service, while the page that collected the sign-in details sat on a different domain. Microsoft did not publish confirmed SPF, DKIM or DMARC verdicts for the campaign.

Detection

Field Effect detected the messages on 13 November 2026 through its email screening service and reported that the same text had appeared at other organisations. Microsoft Threat Intelligence published its warning on 14 November at 06:32:58 UTC. Microsoft recommended the use of Defender for Office 365 Threat Explorer and Defender XDR advanced hunting to investigate the messages, using the EmailEvents, EmailUrlInfo and UrlClickEvents tables. The warning stated that the campaign had targeted organisations across multiple sectors in the United States and gave no count of recipients, clicks or compromised accounts. Microsoft also stated that credential collection and malware delivery had not been confirmed.

Exposure and aliases

A phishing message that arrives at an alias used for a single service identifies that service as the holder of the exposed address, because the alias exists only in that service's records. AliasFleet provides a separate alias for each service, and an alias that begins to receive phishing mail can be paused, rotated or deactivated, which stops further mail to that address. The alias does not change the password on the Microsoft 365 account, and the sign-in page in this campaign asked for that password, so the alias limits the exposure of the address without changing the security of the account itself. The campaign targeted organisations across multiple sectors in the United States, and the messages reached recipients at work addresses held by those organisations. A work address that is also the Microsoft 365 sign-in address carries both roles at once, and a separate alias for each external service keeps the address that unlocks the account apart from the addresses handed to those services.

Top comments (0)