The short version
- The outage. On 12 November access to Exchange Online mailboxes and Outlook was disrupted, and Microsoft says the cause was a network change following a capacity upgrade, not an attack. The Exchange Online incident, tracked as EX1550543, was marked resolved on 13 November.
- Phishing that followed. Microsoft Threat Intelligence saw emails posing as Microsoft 365 service health notices and citing the genuine incident identifier EX1550543. Some messages detected on 13 November told recipients that mail held during the outage would be deleted within 24 hours unless they clicked a link.
- Unconfirmed impact. Microsoft said the activity was consistent with credential phishing, but that credential collection and malware delivery had not been confirmed. It later reported that its security products were blocking the campaign.
- Microsoft's advice. Security teams are told to examine suspicious emails and links, investigate user clicks and review their Safe Links policies, and to verify service incidents directly through the Microsoft 365 admin centre.
- Scope. Organisations and government agencies in several countries reported interruptions to email and other operations, and Microsoft flagged possible effects on Teams, SharePoint Online and Microsoft 365 Copilot. Similar phishing messages went to organisations across several US sectors.
Timeline
| Date | Event |
|---|---|
| 12 Nov | A Microsoft 365 outage disrupts access to Exchange Online mailboxes and Outlook, with possible effects on Teams, SharePoint Online and Microsoft 365 Copilot. |
| 13 Nov | Microsoft Threat Intelligence detects phishing messages citing the incident identifier EX1550543, some warning that held email will be deleted within 24 hours. |
| 13 Nov | The Exchange Online incident EX1550543 is marked resolved. |
| 16 Nov | Microsoft's explanation of the outage and warning about the phishing campaign are reported publicly. |
The outage and its cause
Microsoft stated that the 12 November disruption was a technical issue unrelated to cyber or to AI and agents. It traced the failure to an earlier network capacity upgrade, with a subsequent network change exposing the problem. The company said it fixed the underlying issue and brought services back in stages to keep them stable, and marked the Exchange Online incident, EX1550543, resolved on 13 November.
The outage affected access to Exchange Online mailboxes and Outlook, and Microsoft said Teams, SharePoint Online and Microsoft 365 Copilot may also have been affected. Organisations and government agencies in several countries reported interruptions to email and other operations.
The phishing campaign
Microsoft Threat Intelligence said it observed a campaign exploiting the disruption. The messages posed as Microsoft 365 service health notices and referred to EX1550543, the real incident identifier. In some messages detected on 13 November, recipients were falsely told that email held during the outage would be deleted within 24 hours unless they clicked a link to restore it. Subject lines began with the word Outage followed by a six-character code.
Microsoft named three domains used to send the emails: moments-notice[.]com, planetmaison[.]com and newbooker[.]com. Recipient-specific SendGrid tracking links redirected to reallifeaccounting[.]com. Similar messages targeted organisations across several US sectors.
Microsoft described the activity as consistent with credential phishing, while stating that credential collection and malware delivery had not been confirmed. It later reported that its security products were blocking the campaign.
What is not known yet
- Who sent the phishing emails and from where the campaign was operated.
- How many organisations or recipients received the messages, and whether anyone entered credentials.
- Whether any credentials were in fact collected, or malware delivered.
- Whether the campaign has stopped; Microsoft says its products block it but does not say whether sending has ended.
- Which US sectors received the similar messages Microsoft referred to.
What to do
If you run Microsoft 365
- Check reported service incidents directly in the Microsoft 365 admin centre rather than trusting an emailed notice.
- Review your Safe Links policies.
- Investigate any user who clicked a link in a message that cited the incident identifier.
For everyone else
- Treat urgent deletion or restore warnings sent during an outage as unverified and reach the service through an address you already know.
- Do not enter credentials after following a link in a message about an outage.
Update log
- First published.
Sources
New incident reports by email
One email a week with the reports published since the last one.