Microsoft Teams: FAQ

Why does the bot have Unverified after the name?

Microsoft released an update February 2024 that affects how Teams participants are displayed depending on their account's relationship with the organization.

This only affects the new version of teams (teams.microsoft.com), and is not applicable for the old version (teams.live.com).

Below is a summary of these changes:

No label: All participants who are part of the organizer’s organization.

External: All participants who are external to the organizer’s organization but have a trusted relationship with the organizer or their organization.

Unverified: All other participants will be seen with this label. This will include Microsoft Entra ID users who belong to organizations that do not have an explicit external access setup with the organizer’s organization, Microsoft Account (personal) users, users who are not using any Microsoft ID while joining meetings, and others.

This means that, by default, bot that join a Teams meetings hosted at teams.microsoft.com will have the Unverified suffix.

How to remove the unverified tag

If you wish to remove this tag in favor of the (External) tag, you can authenticate Teams bots as outlined in Microsoft Teams Bot Login.

Microsoft Tenants can specify trusted organizations by following these steps.

Why did my Microsoft Teams bot stay in the meeting after everyone left?

Depending on your Microsoft Teams ecosystem and configuration, Teams may add its own app/service participants to a meeting, such as recording, transcription, Copilot, or other real-time meeting features.

Recall has an internal feature flag that controls whether these Teams app participants count as regular participants for automatic leave behavior. If they are counted, the bot may not trigger everyone_left_timeout after all human participants leave.

If you see this behavior, contact Recall support with the bot ID and approximate meeting time. We can review the logs and adjust the feature flag behavior for your workspace if needed.