Fix Teams Meeting Lobby Never Admits a Guest After a Meeting Policy Change

You changed a Teams meeting policy, and now external guests sit in the lobby forever. The meeting organizer clicks Admit, but the guest never enters the call. This problem usually comes from a policy setting that blocks external participants from bypassing the lobby. This article explains the exact policy that causes this behavior and shows you how to fix it in the Teams admin center.

When you modify meeting policies, the setting called Who can bypass the lobby controls whether guests wait in the lobby. If this setting excludes external users, the Admit button appears but the guest cannot be admitted automatically. You will learn how to correct this setting, verify the policy assignment, and handle cases where the guest still waits.

This guide covers the root cause, step-by-step fixes, related issues, and a comparison of policy options.

Why Teams Meeting Lobby Blocks Guests After a Policy Change

The lobby is a virtual waiting room that appears when a participant is not allowed to bypass it. The setting Who can bypass the lobby is a per-policy setting that determines who can enter the meeting directly. When you change this setting to something other than Everyone, external guests are often excluded.

For example, if you set it to People in my organization, only internal users bypass the lobby. External guests, including federated users and anonymous users, are sent to the lobby. The organizer can still click Admit, but the guest may not be admitted if the policy also restricts manual admission.

Another related setting is Allow external participants. This controls whether external users can join meetings at all. If this is disabled, the guest may be placed in the lobby and never admitted because the system treats them as unauthorized.

The policy change you made likely altered one of these two settings. The fix is to adjust the bypass setting or the external participant setting in the correct meeting policy.

The Role of Meeting Policy Assignment

The meeting policy that applies to the organizer determines the lobby behavior. Each user can have a specific policy, or they inherit the global policy. If you edited the global policy but the organizer has a custom policy, the change has no effect.

You must verify which policy the organizer uses. The Teams admin center shows the effective policy for each user.

Steps to Fix Guest Lobby Admission After a Policy Change

Follow these steps in order. The first step confirms the policy assignment, the second changes the bypass setting, and the third checks the external participant setting.

1. Verify the organizer’s meeting policy
   Open the Teams admin center at admin.teams.microsoft.com. Go to Users > Manage users. Find the meeting organizer and click on their name. Under the Policies tab, look for Meeting policy. Note the policy name, such as Global (Org-wide default) or a custom policy.
2. Edit the correct meeting policy
   Go to Meetings > Meeting policies. Click the policy name you noted in step 1. If the organizer uses the global policy, click Global (Org-wide default). If they use a custom policy, click that policy.
3. Change the bypass lobby setting
   In the policy settings, scroll to Meeting join and lobby. Find Who can bypass the lobby. Select Everyone from the dropdown. This allows all participants, including guests, to enter the meeting directly without waiting in the lobby.
4. Enable external participants
   In the same policy, scroll to External participants. Ensure Allow external participants is set to On. If it is Off, turn it on with the toggle.
5. Save and apply the policy
   Click Save at the bottom of the page. Policy changes can take up to 24 hours to propagate, but usually apply within a few minutes. To speed up the process, ask the organizer to sign out of Teams and sign back in.
6. Test with a guest account
   Schedule a test meeting with an external guest. Have the guest join the meeting link. If the setting is correct, the guest should enter the meeting directly or be admitted automatically when the organizer clicks Admit.

If You Cannot Change the Policy Because You Are Not an Admin

If you are not a Teams administrator, you cannot change these settings. Contact your IT department and ask them to modify the Who can bypass the lobby setting for the relevant policy. Provide them with the organizer’s name and the policy name if you know it.

If Teams Still Keeps Guests in the Lobby After the Fix

Sometimes the main fix does not resolve the issue. The following related problems can also cause guests to wait in the lobby.

Guest Is Still in the Lobby Because the Policy Has Not Propagated

Policy changes can take up to 24 hours to apply. If you just changed the policy, wait at least 30 minutes and test again. Ask the organizer to restart Teams to force a refresh of policy settings.

Guest Is Blocked by a Custom Meeting Policy on the Organizer

If the organizer has a custom policy that overrides the global policy, your changes to the global policy have no effect. Verify the policy assignment again. If the organizer uses a custom policy, edit that specific policy instead.

Guest Is Blocked by a Tenant-Level External Access Setting

The Teams admin center also has a setting called External access under Users > External access. If this is set to Block all external users, guests cannot join any meeting. Set it to Allow all external users or configure allowed domains.

Guest Is Blocked by an Anonymous User Setting

For anonymous users, the setting Anonymous users can join a meeting must be enabled. This is found in the same meeting policy under Meeting join and lobby. If it is off, anonymous guests are placed in the lobby and cannot be admitted.

Who Can Bypass the Lobby: Everyone vs People in My Organization

Item	Everyone	People in My Organization
Description	All participants bypass the lobby, including external and anonymous users	Only internal users bypass the lobby; external guests wait in the lobby
Guest admission	Guests enter directly without waiting	Guests wait until the organizer admits them
Security	Lower security because anyone can join directly	Higher security because external users are screened
Use case	Open meetings with external partners or clients	Internal meetings where external participation is rare

Conclusion

You can now fix the guest lobby issue by editing the Who can bypass the lobby setting in the correct meeting policy. Verify the policy assignment first, then change the setting to Everyone and enable external participation. Test with a guest account to confirm the fix.

If the problem persists, check the external access settings at the tenant level and ensure the organizer uses the intended policy. As a next step, explore the Meeting join and lobby section in the same policy to fine-tune other lobby behaviors, such as allowing phone users to bypass the lobby. For a more advanced approach, consider creating a custom policy for external-facing meetings to keep security high while allowing guests to enter smoothly.