An email says messages are missing after a service outage. There is a deadline to recover them, and a button promising to put everything right. For someone waiting on a customer approval or supplier invoice, that is a tempting offer.
This week, that scenario is a real security concern. In a November 16, 2026 report, Microsoft described a phishing campaign observed on November 13 that impersonated Microsoft 365 service-health notifications. The messages claimed held emails would be deleted within 24 hours unless recipients acted. Source: Microsoft Security Blog, https://www.microsoft.com/en-us/security/blog/2026/11/16/high-volume-phishing-campaign-uses-microsoft-365-outage-lures-target-multiple-industry-sectors-2/. ([microsoft.com](https://www.microsoft.com/en-us/security/blog/2026/11/16/high-volume-phishing-campaign-uses-microsoft-365-outage-lures-target-multiple-industry-sectors-2/?utm_source=openai))
For business owners, the immediate question is not just whether staff can spot a suspicious email. It is whether they know how to verify an unexpected IT instruction without using the contact details inside it.
What is confirmed, and what is not
Microsoft assessed the campaign as likely credential phishing, but said its available evidence did not confirm credential capture, malware delivery or subsequent account compromise. That distinction matters: an observed attempt is not proof that every recipient was breached. Source: Microsoft Security Blog, same report. ([microsoft.com](https://www.microsoft.com/en-us/security/blog/2026/11/16/high-volume-phishing-campaign-uses-microsoft-365-outage-lures-target-multiple-industry-sectors-2/))
Separately, Cofense reported an active credential-phishing campaign exploiting confusion around the November Microsoft outage. The practical warning is straightforward: treat unexpected recovery instructions as something to verify, not something to rush through. Source: Cofense, https://cofense.com/blog/flash-alert-weaponizing-the-november-2026-microsoft-outage. ([cofense.com](https://cofense.com/blog/flash-alert-weaponizing-the-november-2026-microsoft-outage))
Give staff a trusted route to help
We recommend choosing one clear route for employees to check unusual IT requests. That might be your established help desk number, a bookmarked support portal or a named internal contact. For multiple locations, give every branch the same instructions and identify a backup contact for each site.
Do not ask employees to resolve uncertainty by replying to the suspicious message or calling its supplied number. NIST recommends verifying requests through known contact information or a public company website, rather than information in the message itself. Source: NIST, https://www.nist.gov/itl/smallbusinesscyber/guidance-topic/phishing. ([nist.gov](https://www.nist.gov/itl/smallbusinesscyber/guidance-topic/phishing?utm_source=openai))
Put that trusted route somewhere staff can find without searching their inbox. Include it in onboarding, keep it in the staff directory and remind managers to use it themselves. Make verification an ordinary business step, not an admission that someone does not understand technology.
Set expectations before the next urgent message
Ask your IT provider to help you write a short statement explaining how legitimate support works in your business. Specify who can authorize account changes, how employees confirm a support technician’s identity and where approved service updates appear.
We suggest a rule that unexpected requests to sign in, install software or approve an authentication prompt must be checked through your established support route. Avoid relying on a logo, familiar product name or urgent wording as the deciding factor.
The FBI notes that attackers can disguise sender details and direct people to websites that closely resemble legitimate ones. A convincing appearance is not independent verification. Source: FBI, https://www.fbi.gov/how-we-can-help-you/common-frauds-and-scams/spoofing-and-phishing. ([fbi.gov](https://www.fbi.gov/how-we-can-help-you/common-frauds-and-scams/spoofing-and-phishing?utm_source=openai))
Make reporting easier than hiding a mistake
Tell employees exactly what to do if they click: stop interacting with the message and contact IT through the trusted route. Ask them to explain whether they only opened a link, entered a password, approved a prompt or downloaded something. Keep the conversation factual and blame-free.
Request an investigation appropriate to what happened, rather than assuming that deleting the email closes the issue. Microsoft identifies unusual sign-ins, authentication-method changes and new mailbox forwarding rules among the checks relevant to users who interacted with this campaign. Source: Microsoft Security Blog, report linked above. ([microsoft.com](https://www.microsoft.com/en-us/security/blog/2026/11/16/high-volume-phishing-campaign-uses-microsoft-365-outage-lures-target-multiple-industry-sectors-2/))
Try a short exercise this week
At your next team meeting, describe a hypothetical message claiming that yesterday’s missing emails will disappear unless someone signs in immediately. Ask three questions: Would you act? Where would you verify it? Who would you contact if you already clicked?
If answers differ across departments or locations, use that as your improvement list. Assign someone to publish the approved process and confirm that staff can find it. The goal is not to turn everyone into a security analyst. It is to give everyone a dependable next step.
Magic Touch Computers is Your Global IT Department, providing business IT services since 2003 from Calgary to businesses internationally. To review your support verification and phishing-response process, contact Magic Touch at (403) 770-6652, magictouchit.ca/contact, or take the free AI IT assessment at magictouchit.ca/it-assessment.
— The Magic Touch Team