Microsoft Message ID: MC1219793 – 2026-01-27 | (Updated) Brand impersonation protection for Teams Calling

Microsoft 365 Update

💡 Our Technical Review in summary

#### Summary

Microsoft is introducing “Brand Impersonation Protection for Teams Calling” (Roadmap ID 543239), a security feature designed to combat social engineering and fraudulent activity. This update provides proactive safeguards by identifying and flagging inbound external VoIP calls that attempt to mimic trusted organizations. The system evaluates “first-contact” external callers for risk signals and provides real-time warnings to users to improve tenant security.

Impact

  • User Experience: Users will receive “high-risk” call warnings on their screens before answering suspicious external calls. These warnings may persist during the call if risk signals remain active.
  • User Control: Upon seeing a warning, users have the direct option to accept, block, or end the call immediately.
  • Default Configuration: The feature will be enabled by default for all organizations utilizing Microsoft Teams Calling.
  • Scope: This specifically impacts inbound VoIP calls from external callers with whom the user has not previously interacted.
  • Policy Stability: Existing Teams Calling policies remain unchanged; this is an additional security layer rather than a replacement of current configurations.
  • Timeline: Targeted Release is scheduled to begin mid-March 2026 and complete by late March 2026. General Availability dates are yet to be announced.

Action Required

  • Helpdesk Preparation: Inform IT support and helpdesk staff that users will begin seeing these security warnings to prevent them from being reported as system errors or bugs.
  • Internal Training: Update internal documentation, user guides, and security awareness training materials to reflect the new call warning interface.
  • Documentation Review: Monitor the Microsoft 365 Message Center for updated technical documentation and specific screenshots of the warnings, which Microsoft has committed to providing before the rollout begins.
  • Policy Review: While no admin action is required to enable the feature, IT admins should review their current external communication settings to ensure they align with these new security alerts.

Microsoft Official Update

Service: N/A
Category: stayInformed
Severity: normal


Updated January 26, 2026: We have updated the timeline. Thank you for your patience. 

[Introduction]


Brand Impersonation Protection
for Teams Calling adds proactive safeguards against fraudulent or deceptive external callers who attempt to appear as trusted organizations. This helps reduce social-engineering risks and improves tenant security when users receive first-contact external calls. This update aligns with Microsoft’s ongoing investments in caller identity protection and secure collaboration.

This message is associated with Microsoft 365 Roadmap ID 543239.

[When this will happen:]

Targeted Release: Rollout will begin mid-March 2026 (previously mid-February) and is expected to complete by late March 2026 (previously late February).
General Availability: Timelines will be communicated in a future message.

[How this affects your organization:]

Who is affected:

  • All organizations using Microsoft Teams Calling that receive inbound VoIP calls from first-contact external callers.

What will happen:

  • Teams will evaluate inbound calls for signs of brand impersonation.
  • Users will see high-risk call warnings before answering suspicious calls.
  • Warnings may continue during the call if risk signals persist.
  • Users can accept, block, or end the call.
  • The feature will be enabled by default.
  • Existing Teams Calling policies remain unchanged.

[What you can do to prepare:]

No admin action is required at this time.

  • Inform helpdesk staff that users may begin seeing high-risk call warnings.
  • Update internal training materials if applicable.
  • Review Microsoft documentation on caller ID security when available.

Before rollout, we will update this post with new documentation.

[Compliance considerations:]

No compliance considerations identified, review as appropriate for your organization.