A Teams message from "IT Support" offering to fix your flooded inbox feels helpful. It's one of the most effective ways attackers get remote control of a business laptop, and a few settings plus one clear rule stop most of it.
Microsoft Threat Intelligence has documented this pattern in detail, tracking a financially motivated group it calls Storm-1811 whose intrusions led to Black Basta ransomware. Microsoft's write-up of the campaign describes a chain that is simple enough to run against any business on Microsoft 365:
Nothing here is a software flaw. Every step uses a feature working as designed: open external chat, a built-in remote support app, and a stressed employee who wants their inbox back.
Staff have been trained for years to distrust strange emails. Far fewer think twice about a Teams chat, because Teams feels internal. Three things make this attack land:
Teams does show an External label and an accept-or-block prompt for a first chat from outside your organisation, and Microsoft added brand impersonation warnings for first-contact external messages in January 2025. Those help, but a busy person staring at an inbox full of spam will click past a lot of warnings.
Most of the fix lives in the Teams admin center under Users > External access. Microsoft's external access guide walks through each option. Here is how they compare for a typical SME:
| Setting | Default | Recommended for most SMEs | Effect on scams |
|---|---|---|---|
| Teams users in external organisations | Allow all external domains | Allow only specific external domains (your clients and suppliers) | Attacker-owned tenants can no longer start a chat or call |
| Communicate with unmanaged Teams accounts | On | Off, or at least stop them from starting conversations | Blocks personal Teams accounts set up with a fake "IT" name |
| Accounts in trial-only Teams tenants | Blocked | Leave blocked | Stops throwaway trial tenants reaching your staff |
| Block specific external users | Off | Turn on and add any account that has targeted you | Removes a known bad sender from existing chats |
| Report a security concern (messaging policy) | Check both the Teams admin center and Defender portal | Confirm it is on and that reports reach someone who reads them | Turns staff into an early warning system |
Summarised from Microsoft Learn at time of writing. User reporting of Teams messages and calls requires Microsoft Defender for Office 365 Plan 1 or Plan 2, which Microsoft 365 Business Premium includes.
An allow list takes an afternoon to build: export a list of the external domains your team actually chats with, confirm them with each department, and switch over. If you block a domain by mistake, adding it back takes a minute. If you leave everything open, the attacker needs only one employee to accept one chat.
If your IT provider uses a different remote support tool, yes. Microsoft's own guidance in its threat report is to block or uninstall Quick Assist and any other remote management tools you don't use. Its Quick Assist documentation also suggests that organisations supporting users inside a single Microsoft Entra tenant consider Intune Remote Help instead, which adds Conditional Access, role-based permissions and session logging.
The same thinking applies to AnyDesk, TeamViewer and similar apps. Keep exactly one approved remote support tool, block the rest, and make sure staff know which one is real. Device management through Microsoft Intune is the practical way to remove an app from every company laptop at once and stop it coming back.
Settings narrow the door; people decide whether to open it. Give your team one rule they can remember under pressure:
Back that rule up with a few specifics:
Short, regular practice beats an annual slideshow. Our security awareness training guide covers how to run it without taking up much of anyone's week.
If you're unsure how your backups would hold up if this turned into ransomware, our Ransomware 101 guide is a good next read.
Under the PDPA's Protection Obligation, organisations must make reasonable security arrangements to protect personal data. Leaving Teams open to every external tenant and Quick Assist on every laptop is hard to call reasonable once you know how this attack works. Restricting external access and controlling remote tools also map neatly onto the access control and secure configuration areas of CSA Cyber Essentials.
At Cloudeli, our Cloudeli Secure package (US$28.50 per user per month on an annual plan) includes anti-phishing and malware protection for email, Teams and SharePoint. Cloudeli Complete (US$36.60) adds Microsoft Defender for Business and security awareness training with phishing simulations. Whichever way you go, the first step is free: check who can message your staff on Teams today.
This article is general guidance, not legal advice.
By default, yes. Teams external access is set to allow all external domains, so anyone with a Teams account in another Microsoft 365 organisation can find a user by email address and start a chat or call. Admins can restrict this to specific trusted domains in the Teams admin center.
Teams labels people from other organisations as External and, for a first message, asks you to accept or block the chat. A message from "IT Support" or "Help Desk" carrying an External label is a strong warning sign, because your real IT team sits inside your own organisation or contacts you through a channel you already know.
Quick Assist is a remote support app built into Windows that lets another person view or take control of your screen after you enter a code they give you. Scammers use it because it is already installed and looks legitimate. Microsoft recommends removing it if your organisation uses a different remote support tool.
Not necessarily. Most SMEs work with clients and suppliers on Teams, so the better default is to allow only the external domains you trust and block chats from unmanaged personal Teams accounts. Review the allow list whenever you take on a new partner.
Disconnect the session, unplug the device from the network, and report it to your IT provider immediately. Then change the user's password and revoke their sessions, scan the device, and check for newly installed remote access tools before it reconnects.
Book a free consultation. We'll review your Teams external access, remote support tools and reporting setup, and show you which settings to tighten without cutting off the clients and partners you actually work with.