When you schedule a Teams meeting in Outlook and add an external guest, the guest may sit in the lobby forever while you wait for them to appear. The meeting host sees the guest in the lobby but has no button to admit them, or the guest never appears at all. This happens because the meeting policy that controls external participant access is not set to allow people from outside your organization to bypass the lobby. In this article, you will learn how to identify the exact policy setting that blocks guest admission and how to change it in the Teams admin center.
You will also learn the difference between the meeting policy setting and the per-meeting lobby option, and how to verify that your changes actually apply to the meeting you scheduled in Outlook. The fix takes about five minutes and requires Teams admin center access.
Key Takeaways: Fix Guest Lobby Blocks for Outlook-Scheduled Teams Meetings
- Teams admin center > Meetings > Meeting policies > External participants: Set “People external to your organization” to “Everyone” to let guests bypass the lobby.
- Meeting policy > Meeting lobby > Who can bypass the lobby: Check that “People in my organization, trusted organizations, and guests” is selected.
- Outlook meeting invite > Meeting options: Override the policy per meeting by setting “Who can bypass the lobby” to “Everyone” for that specific event.
Why a Guest Gets Stuck in the Lobby for Outlook-Scheduled Meetings
The lobby behavior for a Teams meeting is controlled by two layers: the meeting policy assigned to the organizer and the per-meeting lobby options. When you schedule a meeting in Outlook, the Teams meeting add-in embeds a link that points to a meeting with default settings from the organizer’s policy. If that policy does not allow external participants to bypass the lobby, the guest will be placed in the lobby when they join.
The specific setting is called “Who can bypass the lobby” under the Meeting lobby section of a meeting policy. For external users, the relevant sub-option is “People external to your organization.” If this is set to “Only organizers and co-organizers” or “People in my organization,” then any guest who joins will be held in the lobby. The host may see a notification that a guest is waiting, but the admit button might be missing if the host is not a presenter or if the meeting policy blocks host admission for external participants.
Another cause is that the meeting policy assigned to the organizer is not the one you edited. In Teams, each user has one assigned meeting policy. If you changed a policy but the organizer is assigned to a different policy, the change has no effect. Additionally, the per-meeting override in Outlook’s Meeting options can override the policy, but only if the organizer opens the meeting invitation and clicks the Meeting options link.
The Role of the Teams Meeting Add-in in Outlook
The Teams Meeting add-in for Outlook creates a join link that includes a meeting ID and a set of default settings. These defaults come from the organizer’s meeting policy at the time the meeting is created. If you change the policy after the meeting is created, the existing meeting may still use the old settings. This is why you might need to recreate the meeting or adjust the per-meeting options.
Steps to Fix Guest Lobby Blocking for Outlook-Scheduled Meetings
Follow these steps in order. You need Teams admin center access to change policies. If you are not an admin, ask your IT team to make the changes.
- Identify the organizer’s assigned meeting policy
Sign in to the Teams admin center at admin.teams.microsoft.com. Go to Teams admin center > Users > Manage users. Find the organizer who scheduled the meeting. Click their name, then select the Policies tab. Look for the Meeting policy field. Write down the policy name, for example “Global (Org-wide default)”. - Edit the meeting policy to allow external participants to bypass the lobby
In the Teams admin center, go to Teams admin center > Meetings > Meeting policies. Select the policy name you found in step 1. Scroll to the Meeting lobby section. Next to “Who can bypass the lobby,” choose “People in my organization, trusted organizations, and guests.” Then, next to “People external to your organization,” choose “Everyone.” Click Save. - Wait for policy propagation
Policy changes can take up to 24 hours to propagate fully, but usually they apply within a few minutes. Ask the guest to try joining the meeting again after 10 minutes. If the guest still sits in the lobby, proceed to the next step. - Override the lobby setting for the specific meeting in Outlook
Open the meeting invitation in Outlook. Click the Meeting options link near the join link. In the Meeting options web page, under “Who can bypass the lobby,” select “Everyone.” Click Save. This override applies only to this meeting. - Recreate the meeting if the override does not work
If the meeting was created before the policy change, delete the meeting and schedule a new one in Outlook. The new meeting will use the updated policy. Send the new invite to the guest. - Verify the change by joining as a test guest
Use a personal Microsoft account or a different organization account to join the meeting link. Confirm that you are admitted without waiting in the lobby. If you are still placed in the lobby, check the policy assignment again.
What to Do When the Admin Cannot Change the Policy
If you are not a Teams admin, you cannot change the meeting policy. In that case, you can still use the per-meeting override in Outlook’s Meeting options. This override works even if the policy is restrictive, as long as the organizer has permission to change lobby settings. If the organizer does not see the Meeting options link, they may not have the required license.
If the Guest Still Never Gets Admitted
Teams Shows “Waiting for someone to admit you” Forever
This message means the guest is in the lobby and the host has not admitted them. Check that the host is actually in the meeting and is a presenter. If the host is a co-organizer, they may not have permission to admit external users. Change the host’s role to presenter in the meeting options.
Host Does Not See an Admit Button
The host might not see the lobby notification if the meeting is not using the classic lobby experience. In the new Teams client, the host sees a banner “Someone is waiting” but the admit button appears only if the host has presenter rights. Make sure the host is not in “Breakout rooms” or “Together mode.”
Guest Is Blocked by an External Access Policy
Even if the lobby setting is correct, the guest might be blocked by the external access policy. Go to Teams admin center > External access > External access. Ensure that “Users can communicate with other Skype for Business and Teams users” is set to On. Also check the allowed domains list to confirm the guest’s domain is not blocked.
New Teams Meeting Lobby Settings vs Per-Meeting Override: Key Differences
| Item | Meeting Policy Setting | Per-Meeting Override |
|---|---|---|
| Where to configure | Teams admin center > Meetings > Meeting policies | Outlook meeting invite > Meeting options link |
| Applies to | All meetings organized by users with that policy | Only the specific meeting you edit |
| Who can change | Teams admin only | Meeting organizer |
| Propagation time | Up to 24 hours | Immediate |
| Effect on existing meetings | May not apply to meetings created before the change | Applies to the meeting immediately |
| Best for | Global fix for all future meetings | Quick fix for one meeting |
Use the policy setting for a permanent fix. Use the per-meeting override for an immediate fix without waiting for policy propagation.
After you change the policy, remember that the guest must be from an external domain. If the guest uses the same organization account, they are not considered external and will follow the internal lobby rules.
You can now fix the lobby issue for any Outlook-scheduled Teams meeting. Start by checking the organizer’s meeting policy, then adjust the lobby setting, and use the per-meeting override if needed. For a permanent solution, update the meeting policy in the Teams admin center. Test the fix with a dummy guest account before sending the final invite. If the problem persists, review the external access policy and confirm the guest’s domain is allowed.