Microsoft Warns of Phishing Campaign Exploiting Microsoft 365 Outage

A coordinated campaign masquerades as Microsoft 365 service notifications and urges recipients to restore allegedly held emails.

Microsoft 365 phishing exploits a real service outage as bait to obtain corporate login credentials. On November 13, Microsoft Threat Intelligence detected a coordinated, high-volume campaign targeting organizations across multiple industries worldwide.

The messages appear to be Microsoft 365 service status notifications. They claim that some emails were held during the outage and will be deleted within 24 hours. The goal is to create time pressure and persuade users to open the attached link.

Microsoft 365 phishing directs users outside corporate services

The emails contain buttons or links labeled “RESTORE MESSAGES” and “TAKE ACTION.” According to Microsoft, they lead through tracking URLs to a domain that does not belong to Microsoft. The activity was assessed as a likely phishing and credential theft attempt.

The company also said it has no evidence so far that passwords were obtained, malware was delivered, or user accounts were subsequently taken over. It did not attribute the campaign to any specific actor or known group.

What is confirmed, therefore, is the delivery of the phishing messages themselves—not successful compromise of recipients. It is also unknown whether any user entered credentials on the fraudulent page.

A real incident as credible bait

The attackers relied on users being familiar with recent problems affecting Exchange Online and Microsoft 365 services. Using a current, real-world event may increase the credibility of the messages, even among people accustomed to common phishing attempts.

The campaign’s connection to the outage lies in the bait used. According to secondary reporting, Microsoft did not link the outage itself to a cyberattack.

What organizations and users should check

Microsoft says Microsoft Defender and Defender for Office 365 block these messages and associated malicious domains or move them to quarantine. Organizations should verify that these protections are active and check whether suspicious messages appeared in quarantine or email logs.

  • Do not open links in unexpected service notifications, and check service status directly in the official administration portal.
  • Check the link’s destination; legitimate Microsoft service processes should not redirect users to an outside domain through a tracking link.
  • Report suspicious messages to the internal security team or flag them in the corporate email client.
  • If a user entered a password on a similar page, the organization should handle the situation according to its procedure for suspected account compromise.

Further developments will depend on whether Microsoft or incident-response companies confirm account theft, business email compromise (BEC) scams, or other consequences of the campaign. Organizations should also monitor new sender domains, expansion of the infrastructure used, and any warnings from national cybersecurity authorities.

Sources

  • Microsoft Security Blog – Confirms when the campaign was observed, the lures and domains used, the likely goal of stealing login credentials, the lack of confirmed malware or compromise, and available mitigations.
  • SecurityWeek – Independently summarizes the abuse of the real EX1550543 incident in phishing messages and states that the outage was not a cyberattack.

Verified and updated: November 17, 2026 06:21

Sharing