MC1219793 - Brand impersonation protection for Teams Calling

Message Center

Summary

Brand Impersonation Protection for Teams Calling will roll out mid-May 2026, warning users of suspicious inbound calls from first-contact external callers to reduce fraud risks. The feature is enabled by default, requires no admin action, and existing calling policies remain unchanged.

Last Updated

May 5, 2026

Published Jan 21, 2026

View version history

Service

Microsoft Teams

Tag

Updated message
New feature
User impact
Admin impact

Platforms

Desktop
Mac

More information

Updated May 5, 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-May 2026 (previously early May) and is expected to complete by late May (previously late April).
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.

Version history

5 versions tracked

Updated 4 times since Jan 21, 2026. Microsoft Message Center only ever shows the current version; this archive preserves the history.

Compare any two versions

From
To
  1. May 5, 2026 · 04:43 PMLatest · v5

    Changed: Body

  2. Mar 30, 2026 · 06:57 PMv4

    Changed: Body, End date

  3. Feb 26, 2026 · 07:04 PMv3

    Changed: Body, End date

  4. Jan 27, 2026 · 05:17 PMv2

    Changed: Body, Tags, End date

  5. Jan 21, 2026 · 12:38 AMOriginal · v1

    Changed: Initial version