A new security feature for Teams Calling now alerts users to suspicious external calls that try to impersonate trusted organizations.
The feature will begin deployment in mid-February 2026 for Targeted Release customers, with general availability timelines to be communicated later.
Brand Impersonation Protection is a proactive security safeguard that evaluates inbound Voice over IP (VoIP) calls from first-contact external callers for signs of fraud or deception.
The feature is designed to reduce social engineering risks and voice phishing (vishing )attacks, in which malicious actors pose as legitimate companies to steal sensitive information or manipulate users into taking harmful actions.
When Teams detects a high-risk call, users will see warning messages before answering.
If risk signals persist during the conversation, warnings may continue throughout the call. Users will be able to accept, block, or end suspicious calls based on these alerts.
According to Message Center ID MC1219793, the feature will 2ESDDCCbe enabled by default for all organizations using Microsoft Teams Calling.
Targeted Release customers can expect deployment starting mid-February 2026, with completion anticipated by late February 2026.
General availability dates will be announced in future communications. The feature is supported on Desktop and Mac platforms and does not require any modifications to existing Teams Calling policies.
Organizational Impact and Preparation
Microsoft confirmed that no administrative action is required for deployment. However, IT teams should prepare for the rollout by informing helpdesk staff about the new high-risk call warnings that users may encounter.
Organizations are also encouraged to update internal training materials to educate employees on how to respond to brand impersonation alerts.
The feature aligns with Microsoft’s ongoing commitment to caller identity protection and secure collaboration, addressing the growing threat of fraudulent calls targeting enterprise environments.
No compliance considerations have been identified, though organizations should review the feature in line with their specific regulatory requirements.
Microsoft will update documentation on caller ID security before the rollout begins, providing additional guidance for administrators and security teams.
Follow us on Google News, LinkedIn, and X for daily cybersecurity updates. Contact us to feature your stories.
