The campaign Microsoft confirmed (opens in new tab) on 14NOV is the model of an event lure. Emails posed as service-health notices, cited the real incident identifier, EX1550543, and warned that mail held during the outage would be deleted within 24 hours unless the recipient clicked to restore it. Display names took the form of the recipient's own organization followed by "Outage Notification" or "Service Health". Links were per-recipient and routed through a legitimate email delivery service, then a redirector that showed a decoy blog to anyone who was not a target, then a landing page on a random subdomain behind a bot check, the shape of an adversary-in-the-middle sign-in proxy. The infrastructure was four aged domains bought through two registrars, three sharing one CDN account, two sharing one cloud host, and all three senders sharing one mail provider. The delivery service disabled the links and the sender domains stopped resolving by 16NOV. Microsoft assesses the activity as likely credential phishing and has not confirmed credential capture or account compromise.
A second campaign, reported (opens in new tab) on 17NOV and still being detected that day, took a different shape. Subject line "disconnected after the outage", a verification code in the body, and a link to a sign-in clone that walks the visitor through entering an account name, requesting a new code, and entering it, with a "use your password" fallback at every step. The flow fits either a device-join attempt or a plain credential theft, and the same "outage" banner sits on the sign-in page regardless of the lure, which is the signature of a kit built to be reused for the next event.
The first outage-themed harvesting page came from a different operator. Registered 23 hours after onset on a Bahamas-based registrar and hosted on a mainstream cloud provider, winrefrequests[.]com presented a "Microsoft Refund Request Form" marked confidential and asked for full legal name, date of birth, Microsoft account, alternate email, phone, billing address, purchase channel, payment method, bank name, and refund amount. The form rendered client-side and posted to a relay script on a second domain. Nothing about its registrar, hosting, or DNS connects it to the service-health campaign. Two crews worked one headline with two different asks. One wanted a credential. The other wanted an identity and a bank relationship.