NEWS

Microsoft Teams to Get AI-Powered, Context-Aware Phishing Detection

Starting early November 2026, Teams will use AI to flag phishing and social engineering in chats, including messages with no links or files.

Dylan H.

News Desk

October 25, 2026
2 min read
Microsoft Teams to Get AI-Powered, Context-Aware Phishing Detection

Overview

Microsoft will add AI-powered phishing detection to Teams messages beginning in early November 2026. The feature reads the context of a conversation to spot phishing, social engineering, impersonation, and deceptive intent.

Rollout Timeline

PhaseTiming
Targeted release beginsEarly November 2026
Targeted release endsMid-November 2026
Worldwide general availabilityEarly to mid-December 2026

How It Works

  • Analyses conversation context rather than relying only on malicious links or attachments, which suits attacks that carry no traditional indicators.
  • Focuses on higher-risk situations such as first-contact chats from external users.
  • Microsoft says message content is not retained by the detection system for model training or other secondary uses, and that the feature is limited to security purposes.

Admin Impact

No admin action is needed to enable it, and the announcement describes no setting to control it. Microsoft announced related Teams protections separately:

  • Admins can block external users from the Defender portal, starting in January.
  • A meeting protection policy, rolled out in August, can block identified external bots.
  • QR codes from external senders will be blurred, and users will be able to report suspicious guest invitations.
  • Third-party deepfake detection in meetings is planned.

Why It Matters

Attackers increasingly use Teams chat, often impersonating IT support from an external tenant, to deliver malware. Detecting intent in text fills a gap that URL and file scanning cannot.

Recommendations

  1. Brief help desk and staff that new warnings may appear on external first-contact chats.
  2. Review external access settings and restrict federation to trusted domains.
  3. Keep user reporting for suspicious Teams messages in your phishing training.

Sources