Public mode

No tenant, Graph, or device access. Every item links to its source. What this means

Some sources or documents need attention: 253/255 feeds/APIs · 417/444 docs · checked 13:25 UTC Customize Public modeDiscuss ChangeIntel on Discord

(Updated) Brand impersonation protection for Teams Calling

Versions captured by this deployment. Earlier versions and notices may be missing; first observed is not first published.

Rollout

Ends
30 Oct 2026
Roadmap
543239
Platforms
Desktop, Mac

Rollout dates are often only in the text. When Microsoft moves them, the change shows under "What changed".

Microsoft's start date
21 Jan 2026
Last changed by Microsoft
29 Jun 2026
First seen here
19 Oct 2026
Versions seen
2

What the notice says

Microsoft's text, with its sections, lists and tables; source markup removed

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.

What changed

Between the versions this installation saw, newest first
  1. Only details this page does not show changed.

  2. · first version seen

Linked documentation

Microsoft pages the notice links to

The notice links to no Microsoft Learn or Support page that this installation reads.

Not confirmed here

What this page cannot tell you
  • Whether your tenant is affected: this is Microsoft's notice, not a check of your settings.
  • Versions before 19 Oct 2026: this installation first saw the notice after Microsoft posted it.
ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 19 Oct 13:25 UTC · 253 of 255 readable · 252 fully read · documentation 417/444 current