Outage phishing: a service-health notice that asks you to restore mail.
Search the mail. Name who clicked. Reset any account that may have typed a password. Read this against every mailbox that signs into Dynamics 365.
On 13 November 2026 Microsoft Threat Intelligence saw a high-volume phishing campaign across many industries. The messages pretend to be a Microsoft 365 outage notice and say held mail will be deleted within 24 hours. The likely aim is a password. Search the mail, name who clicked, and reset any account that may have typed a password.
High volume, many industries, worldwide. Built around a fake Microsoft 365 outage.
A link only. Microsoft found no malware in the samples and named no threat actor.
A 24-hour deletion deadline, and a button that leaves Microsoft.
A fake service-health notice.
Microsoft analysed the lures sent on 13 November and published the findings on 16 November. Software Dynamics has not examined the samples. The description below is Microsoft's.
| Spielfeld | What Microsoft observed |
|---|---|
| Subject | Outage, then six random letters or digits, for example Outage - aF7vG6. Two further patterns use the same trick: Strengthen - Security, and Restore -- 4 messages, each with a random token. |
| Display name | Three characters in the style of an organisation code, then Outage Notification or Service Health. |
| Sender domains | moments-notice[.]com, planetmaison[.]com and newbooker[.]com, plus bounce subdomains. |
| The claim | A purported Exchange Online incident on 12 November. Four messages held, to be deleted within 24 hours unless the recipient acts. |
| The button | RESTORE MESSAGES or TAKE ACTION. The link is unique to the recipient and records the click. |
| The landing | reallifeaccounting[.]com, including /themelist0.html in multiple samples. Some messages continue to outagefixed[.]sbs or outagerestored[.]sbs. |
| Absent | QR codes, attachments other than the message itself, and any executable, archive or document payload in the samples Microsoft reviewed. |
How far the evidence goes. The samples stop before the final page. They do not show a password field, a submitted password, malware or activity after a compromise. Where Microsoft Defender for Office 365 is on, Microsoft is blocking and quarantining these messages, and reports no indicator of compromise from this attack. Mail that landed before the block, and mail in a tenant without that product, still needs a search.
What a captured identity can reach.
Credential capture is Microsoft's assessment, and it was not witnessed in the evidence. The table below is what a captured Microsoft 365 identity can reach on an estate we implement. It is analysis, not a record of an incident.
| The account reaches | What changes in the business |
|---|---|
| The mailbox | A reply to a supplier, a forged invoice, or a second wave of the same lure sent internally. |
| Inbox rules | Forwarding, or a rule that hides bank-detail and payment conversations from the real owner. |
| OAuth consent | An application that keeps access after the password is changed. |
| Files | Contracts, bank letters and payroll files in SharePoint, OneDrive and Teams. |
| Dynamics 365 | A vendor bank account, a payment journal, a security role, or an approval that looks routine. |
One Entra account, two front doors. The person who reads finance mail usually signs into Finance and Operations or Business Central with the same Entra ID account. A captured Microsoft 365 password is a path to the mailbox and, where multifactor authentication is weak or already satisfied, a path into the ledger. Treat a click by a payments, vendor-master or administrator account as a finance event. Read these accounts first: accounts payable, vendor master, treasury, payroll, and anyone who can assign a security role in Finance and Operations or Business Central.
Refuse the link.
A genuine Microsoft 365 service-health notice is confirmed in the Microsoft 365 admin centre. Recovery of held mail is not sent through a website outside Microsoft.
RESTORE MESSAGES and TAKE ACTION in this lure leave Microsoft. The tracking link records the click.
Open Service health in the Microsoft 365 admin centre. A real Exchange Online incident is published there.
Use the Outlook Report button. If you clicked or typed a password, tell the service desk the same day and include the time.
Microsoft has warned of phishing email that pretends to be a Microsoft 365 outage notice. It says messages were held during a disruption and will be deleted within 24 hours, and it asks you to click Restore messages. Microsoft publishes service health in the admin centre. An email that sends you elsewhere to recover mail is not that notice. Do not click the button. Do not type your password. Report the message in Outlook. If you already clicked or typed a password, tell IT today and include the time.
If you already clicked. A click with nothing typed: report the message and the time, keep using the mailbox, and IT will watch the account. A password typed: tell IT before you send more mail, change a vendor or approve a payment, and the account is reset the same day. An MFA prompt you did not expect and approved: say so, because that prompt is part of the incident.
What to search, defanged.
Microsoft published these indicators on 16 November 2026. Brackets keep the names from becoming links. Remove the brackets before you search or block, and confirm a hit in your own logs before you treat it as this campaign.
| Indicator | Type | Use |
|---|---|---|
| moments-notice[.]com | Sender | Search |
| em4493.moments-notice[.]com | Sender | Bounce or mail-from |
| planetmaison[.]com | Sender | Search |
| newbooker[.]com | Sender | Search |
| em.newbooker[.]com | Sender | Bounce or mail-from |
| url.newbooker[.]com, url7489.newbooker[.]com | Tracking | Click and open host |
| reallifeaccounting[.]com | Destination | Block |
| reallifeaccounting[.]com/themelist0.html | URL | Block the path |
| outagefixed[.]sbs | Destination | Block |
| outagerestored[.]sbs | Destination | Block |
| outagerestored[.]sbs/topics_pxyk/themelist0.html | URL | Block the path |
| 162.120.17[.]69 port 8080 | IP | Tracking images, /t/v3 |
| Outage - <six characters> | Subject | Random token |
| Strengthen - Security <token> | Subject | Random token |
| Restore -- 4 messages <token> | Subject | Random token |
Leave SendGrid in place. Three tracking hosts appeared under ct.sendgrid[.]net: u113727626, u118254266 and u118250677. Search for them beside the sender, the subject and the destination. A block on sendgrid[.]net will break legitimate mail. Microsoft's guidance is to combine sender, content, URL and behaviour, and to block the destination domains above. In Microsoft Defender XDR, Microsoft published three advanced hunting queries: messages by sender domain or subject, messages that contain the campaign URLs, and clicks on those URLs. Tenants without Defender for Office 365 can search for the same sender domains, subjects and URLs in Exchange message trace and the URL click report, from 12 November 2026.
Search, then decide.
Defender for Office 365 is already blocking this mail where it is switched on. The search still matters for anything delivered earlier, and for tenants that do not have that product.
-
1
Search from 12 NovemberSender domains and subject patterns in the indicator table, plus any URL containing reallifeaccounting, outagefixed or outagerestored. Use Explorer or quarantine with Defender for Office 365. Otherwise use message trace in the Exchange admin centre.
-
2
Remove what was deliveredQuarantine matches and delete delivered copies under your usual process. Record the recipients before you purge, so the click review has a list.
-
3
Name who clickedUse the click log in Microsoft Defender, the URL click report, proxy logs and the endpoint browser. Record whether the click was allowed and whether the destination opened.
-
4
Split the responseA click with no password typed: watch the account and coach the person. A password that may have been typed: go to the same-day steps. Payments, vendor-master and administrator accounts take the stronger path on any doubt.
-
5
Block the destinationsBlock reallifeaccounting[.]com, outagefixed[.]sbs and outagerestored[.]sbs at the mail gateway and the web proxy. Keep the block tied to this campaign and revisit it when Microsoft updates the list.
-
6
Tell people where service health livesSend the staff note below. Say, in one line, who receives a report and how fast a typed password is reset.
Name an owner for each action. The Microsoft 365 administrator runs the search and the quarantine. The identity administrator resets passwords and revokes sessions. The finance controller watches vendor bank accounts and payment journals for the people on the click list. The service desk sends the staff note and takes the reports. One name on each, today. Done when the search runs from 12 November through today and the recipient list is kept, every click is marked as a password typed or not typed, the three destinations are blocked at mail and at the web proxy, and the staff note has gone out.
Same day, identity first, then the ledger.
Microsoft did not observe this follow-on activity in the samples. These checks are the ones to run when a person may have submitted credentials to the landing page.
-
1
Reset and revokeReset the password. Revoke active sessions and refresh tokens in Entra ID. Sign the user out of Outlook, Teams and Dynamics 365.
-
2
Check the second factorLook for an MFA method added or changed after 12 November. Remove anything the user does not recognise. Prefer a phishing-resistant method when you re-register them.
-
3
Read the sign-insNew IP addresses, new devices, unfamiliar user agents and sign-ins outside normal hours. Include the Dynamics 365 and Business Central applications, not only Exchange.
-
4
Read consent and rulesNew OAuth grants. Inbox rules, forwarding and delegate access. Remove anything the user did not create.
-
5
Read the files they can openUnusual access to Exchange, SharePoint, OneDrive and Teams from that account after the click time.
Then read Finance and Operations, or Business Central
| Look at | From the click time, for that user |
|---|---|
| Vendor bank account | Any change by that user, or by someone they emailed in the days after the click. |
| Payment journal | Lines created, edited or posted by that user. |
| Security roles | A new role, a new approver, or a change to an integration account they administer. |
| Workflow | Approvals completed from a new location or a new device. |
| Power Automate | A flow that moves mail, payment files or vendor records, created by that user. |
Pause that user. The payment run continues. Until the five identity checks and the ledger checks are clean, pause vendor-bank edits and payment posting for that user. A finance manager reviews the held items before they are released. Bring six facts to the ticket: the user, the click time, whether a password was typed, whether an unexpected MFA prompt was approved, sign-ins since the click, and any vendor-bank or payment-journal change since the click.
Make the next lure expensive.
The pretext will change. The next one will borrow a different outage, a tax deadline or a payment hold. These controls still apply.
Passkeys or FIDO2 security keys for finance, vendor-master and administrator roles first. App-based MFA everywhere else. Retire SMS for those roles.
Safe Links, Safe Attachments and Zero-hour auto purge, so a message delivered before the intelligence lands can still be removed.
Block legacy authentication. Require MFA for Exchange, SharePoint and the Dynamics 365 and Business Central applications.
A vendor-bank change needs a second person. Alert when a vendor bank account changes, and when a payment journal is posted from a new device.
Attack simulation training with an outage, a 24-hour deadline and a Restore messages button. Include the finance team.
The Outlook Report button, routed to people who can search the tenant the same day. Publish that path in the staff note.
Source: Microsoft Threat Intelligence, 16 November 2026, high volume phishing campaign, Microsoft Security Blog. MITRE ATT&CK as mapped by Microsoft: T1566.002, T1036 and T1204.001. Microsoft did not map credential capture, malware, command and control, or theft of data. Software Dynamics has not independently examined the samples.
Häufig gestellte Fragen
What is the Microsoft 365 outage phishing email?
A high-volume phishing campaign that Microsoft Threat Intelligence saw on 13 November 2026. The message pretends to be a Microsoft 365 service-health notice, says mail held during an Exchange Online incident will be deleted within 24 hours, and asks the reader to click Restore messages or Take action. Microsoft assesses it as credential phishing.
How do I recognise the message?
The subject is Outage followed by a random token, or Strengthen - Security, or Restore -- 4 messages. The sender domain is moments-notice, planetmaison or newbooker, not Microsoft. The button opens a link that leaves Microsoft and lands on reallifeaccounting[.]com or an outage-themed .sbs host.
Where is a real Microsoft 365 outage published?
In Service health in the Microsoft 365 admin centre. Recovery of held mail is not sent through a website outside Microsoft, so an unsolicited restore link is the phish.
What should we do if someone clicked or typed a password?
Report the message and the time. If a password may have been typed, reset it the same day, revoke sessions and refresh tokens in Entra ID, check for new MFA methods, inbox rules and OAuth grants, and review sign-ins. For a payments, vendor-master or administrator account, also read vendor bank-account, payment-journal and security-role changes in Dynamics 365 from the click time.
Why does this matter for Dynamics 365?
The person who reads finance mail usually signs into Finance and Operations or Business Central with the same Entra ID account. A captured Microsoft 365 password can reach the mailbox and, where multifactor authentication is weak or already satisfied, the ledger.
PHP2Shell and the portal that calls Dynamics 365: the October 2026 advisory on the PHP flaws and the identities that portals hold. Our Dynamics 365 services cover security roles, Entra ID and approval design.
