Forum Discussion
Teams calls reporting as potentially scams incorrectly
Hey Teams Community,
In the past 5 days I am seeing callers from external tenants that are trusted and in mto showing as suspected scam callers when they call me. They see.me as a suspected scam also when I call. These tenants are all trusted and most of them are.members of the same MTO. This only started happening in the last 7 days.
What is causing this?
Does anybody else see this happening recently with a similar setup?
2 Replies
This sounds more like a false positive in Teams scam detection than a problem with your MTO setup. Being in the same MTO does not automatically prevent a call from being checked or marked as suspicious.
First, test how the call is made:
- Call the person directly from their Teams profile or chat.
- Then test by dialing their telephone number.
If only the telephone-number call is flagged, the problem is probably related to caller ID or the number’s reputation. If a direct Teams-to-Teams call is also flagged on both sides, it is more likely a Teams service issue.
Since this started recently and affects several trusted tenants, I would check Microsoft 365 Service health first. If no incident is listed, ask your Teams admin to open a support case and include the affected users, call times and call IDs from Teams call analytics. Reinstalling Teams is unlikely to fix it if both sides and multiple tenants are seeing the same warning.
Calls between two trusted external tenants are now marked as potential scams in both directions, despite the multitenant organization relationship. That relationship governs cross-tenant identity and collaboration; it does not guarantee how Teams classifies a call. Because this changed suddenly in both tenants, capture two examples per direction: UTC time, caller and callee UPN or number, tenant IDs, client version, call ID, and the warning screenshot. Compare desktop, web, and mobile, then place an internal call to distinguish client display from service classification. In Teams admin center, inspect each example with Call Analytics and check Microsoft 365 service health for an advisory. Do not change federation or MTO settings merely to suppress the label. If the warning repeats while the calls look normal in analytics, open a Microsoft support case with the paired call IDs and timestamps. The cited Microsoft guidance does not provide a tenant override for this classification.
