Teams calls reporting as potentially scams incorrectly

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.