Troubleshoot Microsoft Teams Join Failures

Edited

Here are some of the most common issues you may encounter when using Fathom with Microsoft Teams, along with steps to resolve them.

Why does Fathom show as “Unverified”?

Microsoft is labeling a third-party meeting bot.

What to try: the label by itself isn't a recording failure — check whether Fathom was actually admitted or blocked. Keep your security controls at the level your organization prefers.

Why didn’t Fathom join my Teams meeting? 

Common causes: the desktop app is closed, outdated, or signed out; auto-record is off for that meeting type; the meeting is on a secondary or unconnected calendar; the event has no valid web link; or it's an impromptu meeting with no link added manually.

What to try: open and update the desktop app; check your recording preferences and connected primary calendar; join from the Fathom desktop app or paste the web link into Add to Meeting.

Why did a teammate's Fathom record instead of mine? 

Your organization may have "limit to a single bot per meeting" enabled, or recording may be limited to the organizer or first eligible teammate.

What to try: find the recording in that teammate's account and ask them to share it; ask your Fathom admin to review the single-bot setting; agree on one recorder per meeting to avoid duplicates.

Can Fathom rejoin after the host removes it? 

The organizer or another attendee removed the notetaker, and the missing portion can't be recovered. Fathom may not be able to rejoin the same meeting link or recurring meeting ID after removal — create a new meeting link if you need to.

Why did Fathom disconnect or record no audio? 

The meeting may have been very short or had little audio; the mic or meeting audio was muted or undetected; a long silent stretch triggered a reconnect that left Fathom in the lobby; or the meeting exceeded supported size/resource limits.

What to try: confirm the meeting ran several minutes with audible conversation; check lobby admission and participant count; if it keeps happening on normal meetings, send Support the details in the last section.

Why is a shared document missing from my Fathom recording? 

Content shared through Teams' built-in Office sharing may not be captured correctly.

What to try: open the file in its desktop app (PowerPoint, Word, etc.) and share the application/window instead of using the built-in sharing flow.

Can Fathom record webinars, live events, or registration meetings? 

These meeting types use different join flows or stricter participant rules.

What to try: recreate it as a standard Teams meeting when you need Fathom to capture it.

Can Fathom record government or sovereign-cloud (GCC, GCC High, DoD) meetings? 

These environments use different domains and stricter anonymous/external access rules, so compatibility isn't guaranteed.

What to try: run a test first. If the standard checklist doesn't work, contact Support with your exact Teams environment and join link.