Troubleshoot Microsoft Teams Join Issues

If the Optiverse assistant joins some Microsoft Teams meetings successfully but fails on others, the issue is usually caused by Teams admin policy settings, not by an Optiverse outage.

This guide explains why that happens, how to preserve lobby-based approval for privacy, and what your IT admin should check to restore normal joining behavior.

When This Guide Applies

Use this guide if any of the following are true:

• The assistant joins one organizer's Teams meetings but not another's
• The assistant appears to hit a sign-in or anonymous access restriction
• Meeting options look correct, but the assistant still cannot join
• The issue started after a Microsoft change, policy rollout, or admin update

If you need a general explanation of how the assistant behaves in meetings, see How the Assistant Works.

Short Answer

Microsoft Teams controls meeting access at more than one level.

• Tenant-wide admin settings define the organization default
• Per-user meeting policies can override the default for specific organizers
• Per-meeting options only work within the limits set by the admin policy

That means a meeting organizer can set options that look correct, but the assistant may still be blocked if the assigned Teams policy does not allow anonymous participants to join.

Why It Works For Some Meetings But Not Others

This pattern usually means different organizers in your company are using different Teams meeting policies.

For example:

• Organizer A uses the global default policy, which allows anonymous users to join unverified
• Organizer B has a custom policy that blocks anonymous users
• Result: the Optiverse assistant can join Organizer A's meetings, but fails on Organizer B's meetings

This is why the issue can feel random even though the root cause is policy-based and consistent.

Privacy: You Do Not Need To Bypass The Lobby

Many teams worry that fixing this issue means letting the assistant enter meetings automatically. That is not required.

You can keep the assistant waiting in the Teams lobby until someone admits it.

This setup preserves control for the meeting host while still allowing the assistant to request entry successfully.

The Setting That Usually Fixes The Issue

Your IT admin should check whether "Anonymous users can join a meeting unverified" is enabled:

• At the global Teams meeting settings level
• On any custom meeting policy assigned to affected organizers

If this setting is off in either place, the assistant may be blocked before it can wait in the lobby.

IT Admin Checklist

1. Check The Global Meeting Setting

Go to the Microsoft Teams Admin Center and review the organization-wide meeting settings:

1. Open https://admin.teams.microsoft.com/one-policy/settings/meeting
2. Find the Meeting join & lobby section
3. Confirm that Anonymous users can join a meeting unverified is turned On

This is the default behavior used unless a custom meeting policy overrides it.

2. Check The Policy Assigned To Affected Organizers

Then confirm whether affected users have a custom policy:

1. Open Teams Admin Center
2. Go to Users
3. Select Manage users
4. Open the affected meeting organizer
5. Click the Policies tab
6. Review the Meeting policy row

If the organizer is assigned a custom meeting policy instead of Global (Org-wide default), that custom policy must also have Anonymous users can join a meeting unverified turned On.

3. Keep Lobby Approval If Needed

If your team wants full control over when the assistant enters, you can usually keep:

• Who can bypass the lobby = People in my org

With this setup, the assistant can reach the lobby and wait there until someone admits it.

Why Per-Meeting Settings Are Not Enough

Teams meeting options shown to the organizer are not the highest level of control.

If the organizer changes a meeting option but the admin-level policy blocks anonymous participants, the policy wins. From the organizer's point of view, it can look like the assistant is broken even though Teams is enforcing a higher-level rule.

This is the main reason support teams see statements like:

• "It worked before"
• "We changed the meeting options and it still did not work"
• "Only some users are affected"

How To Test After Changing The Settings

After your admin updates the relevant Teams settings:

1. Ask an affected organizer to schedule or reopen a Teams meeting
2. Send the assistant to the meeting
3. Confirm it appears in the lobby
4. Admit it manually
5. Verify that the assistant joins and posts its transparency message in the chat

If you miss the first attempt, you can resend the assistant from the Calendar page. More detail is available in How the Assistant Works.

Common Misunderstandings

"We must allow the assistant to bypass the lobby"

No. The assistant can work while still waiting for approval in the lobby.

"The organizer already changed the meeting settings, so Teams is configured correctly"

Not necessarily. Tenant settings and assigned meeting policies can override what the organizer sees at the meeting level.

"If some meetings work, Optiverse must be unstable"

Usually not. Mixed success across organizers often points to different Teams policies assigned to different users.

"It started after a Microsoft change, so Optiverse must have changed something"

Not always. Teams behavior can change after Microsoft updates, admin policy edits, or policy reassignment. Rechecking the meeting policy is a good first step.

When To Contact Optiverse Support

Contact support if:

• The required Teams settings are confirmed and the assistant still cannot reach the lobby
• The assistant joins but fails after being admitted
• You want help validating the Teams configuration with your IT admin

When contacting support, include:

• The affected organizer's email address
• Whether the issue affects all organizers or only some
• Whether the assistant reaches the lobby, shows a sign-in prompt, or never appears
• The exact Teams policy assigned to the affected user, if known

Related Pages

• Microsoft Teams Integration
• How the Assistant Works