When an employee accepts a Microsoft Teams guest invitation from another company, that guest session runs under the host company’s security settings, not yours. If the host tenant has no Microsoft Defender for Office 365 protection, which is easy to end up with on a cheap Microsoft 365 plan, your employee is unprotected inside that session even though their own account is fully covered at home. Microsoft is rolling out a Teams reporting tool this month to catch suspicious invites after the fact, but the real fix is controlling who can send your team a guest invite in the first place.
- Teams guest access runs under the host tenant’s security configuration, not the guest’s home organization, according to research published by security vendor Ontinue.
- An attacker can set up a bare-bones Microsoft 365 tenant on a plan such as Teams Essentials, which doesn’t include Defender for Office 365, then invite a target into what Ontinue calls a “protection-free zone.”
- Microsoft has begun rolling out a feature, detailed in Teams message center post RM571297, that lets a user flag a suspicious guest invitation when they decline it, with the report routed to IT admins and to Microsoft.
- That reporting tool only helps after someone notices an invite looks wrong. Microsoft Entra ID’s external collaboration settings can stop an untrusted invite from reaching an inbox at all.
- Boston firms that rely on Microsoft 365 for client collaboration are a natural target, since guest invites from unfamiliar companies are routine and easy to accept without a second look.
What actually happens when someone accepts a Teams guest invite?
Microsoft 365 treats a guest session as belonging to the tenant doing the hosting. Your employee’s identity travels with them, but the mail filtering, link scanning, and attachment sandboxing that Defender for Office 365 normally provides come from whichever organization set up the meeting or chat. If that organization pays for a plan without Defender for Office 365, none of that scanning happens during the session. A malicious link or file shared in that guest chat reaches your employee with no extra layer of inspection, even though their own company’s Microsoft 365 subscription includes full protection everywhere else they work.
Why does the host tenant’s configuration override the guest’s own protections?
This is a function of how Microsoft 365 licensing and policy enforcement are scoped to a single tenant, not a flaw someone can patch out. Protection follows the admin console that owns the meeting, not the person attending it. Ontinue’s research found this makes guest invitations an easy entry point: a throwaway tenant costs little and takes minutes to set up, and it gives an attacker full control over which protections stay on.
Is Microsoft treating this as a vulnerability it will fix?
No. Microsoft and Ontinue both frame this as expected behavior tied to how tenant-based licensing works, not a bug. Independent reporting on the research noted Microsoft had not issued a patch or changed the underlying design as of the story’s publication, because there is nothing technically broken to repair. That means the responsibility for managing this risk sits with each organization’s admin settings, not with a future Microsoft update.
What does the new Teams reporting feature actually change?
Starting this month, a user who declines a Teams guest invitation can flag it as suspicious. The report lands in the Teams admin center under user-reported security submissions and also goes to Microsoft, per the rollout notice in message center post RM571297. That’s a useful signal for IT, but it depends on an employee first recognizing the invite as suspicious. It does nothing to stop a convincing invite from arriving in the first place.
How should a Boston business lock this down now?
Start in Microsoft Entra ID’s external collaboration settings and restrict guest invitations to a specific allowlist of trusted domains, rather than leaving the default that accepts invites from any Microsoft 365 tenant worldwide. From there, require admin approval for new guest access requests and review the Teams admin center’s external access policies at least once a quarter. This pairs well with locking down who can approve multifactor prompts, a problem we covered in our piece on MFA fatigue attacks, since both issues come down to tightening who your Microsoft 365 tenant trusts by default. If your team has already dealt with suspicious content slipping past automated filters, our post on prompt injection attacks against Microsoft 365 covers a related gap in how AI-assisted tools handle untrusted input.
Frequently asked questions
Does this affect every Microsoft 365 plan?
It affects any organization whose employees accept Teams guest invitations from outside tenants, regardless of the employee’s own plan. The risk comes from the host tenant’s configuration, not the guest’s.
Is accepting a Teams guest invite always risky?
Not always. Invites from known business partners on properly licensed, well-managed tenants carry little added risk. The concern is unsolicited or unexpected invites from unfamiliar organizations.
What should an employee do with an unexpected guest invite?
Decline it unless they can confirm who sent it and why, and use the new reporting option when declining if the invite looks like a phishing attempt rather than a legitimate business request.
Can IT block these invites without Microsoft’s new reporting feature?
Yes. Microsoft Entra ID’s external collaboration settings let admins restrict guest invitations to approved domains or require admin sign-off, which stops most unwanted invites before anyone has to make a judgment call.
If your business collaborates with outside firms over Microsoft Teams and no one has reviewed your Entra ID external collaboration settings since you set up Microsoft 365, that’s worth 15 minutes before it becomes an incident. Boston Managed IT offers a free 15-minute Microsoft 365 security review to check your guest access, external sharing, and multifactor settings against what’s actually safe for your business. Call (617) 322-5155 or visit bostonmit.com/contact to set it up.
— Boston Managed IT