How to Fix Microsoft Teams Meeting Lobby Bypass Settings Not Working for External Guests
Summary
This guide helps you troubleshoot and resolve: How to Fix Microsoft Teams Meeting Lobby Bypass Settings Not Working for External Guests. Follow the steps below to fix the issue.
Common Causes
Microsoft Teams lobby settings control who can join a meeting directly and who must wait in the lobby to be admitted by the organiser. If external guests are still being held in the lobby despite your settings appearing correct, it is usually due to meeting options overriding organisation policies, guest access restrictions, or the meeting being scheduled from a personal calendar rather than a Teams channel.
Quick Fix Steps
- Open the meeting in your Teams calendar and select Meeting options.
- Under Who can bypass the lobby?, select Everyone or People in my organisation and guests.
- Save the changes and re-send the meeting invitation to external guests.
- Ask the guest to join using the Teams app or web browser rather than dialling in by phone.
Detailed Instructions
Check Meeting Options
- Open Microsoft Teams and go to the Calendar tab.
- Select the affected meeting and click Meeting options in the top toolbar. This opens the meeting options page in your default web browser.
- Locate the Who can bypass the lobby? dropdown.
- Change the setting to Everyone to allow all external guests to join directly, or People in my organisation and guests if you only want authenticated external users to bypass.
- Click Save.
- Update the meeting and send the revised invitation to all external attendees.
Verify Guest Access is Enabled in Teams Admin Centre
- Sign in to the Microsoft Teams admin centre.
- Navigate to Users > Guest access.
- Ensure Allow guest access in Microsoft Teams is toggled to On.
- Confirm the external guest has been added as a guest user in your Microsoft 365 tenant, or is joining from an organisation that has federated Teams access with yours.
- Ask the guest to sign in to Teams with their own Microsoft 365 or Office 365 account before clicking the meeting link.
Schedule from a Team Channel (Optional)
Meetings scheduled inside a Teams channel sometimes handle lobby permissions differently than meetings scheduled from your personal Outlook or Teams calendar. Channel meetings may have different lobby behaviour depending on the channel settings and meeting policies. If lobby issues persist, try creating the meeting within a relevant channel and inviting the external guest directly.
Troubleshooting
Guest Still Stuck in Lobby After Changing Settings
- Ask the guest to fully close and restart the Teams app, or clear the Teams cache by deleting the contents of
%appdata%\Microsoft\Teamson Windows. - On macOS, quit Teams and remove the Teams cache folder from
~/Library/Application Support/Microsoft/Teams. - Ensure the guest is using the meeting link from the updated invitation, not an old calendar entry.
- Verify the guest is not using a consumer Skype account. Consumer Skype accounts may behave differently and are not always subject to the same lobby bypass rules as Microsoft 365 guest accounts. Ask the guest to join with a Microsoft 365 or Office 365 account where possible.
Meeting Options Greyed Out or Missing
- This usually means your organisation’s admin has restricted lobby settings at a policy level. Meeting policies assigned to your user account may prevent you from changing lobby options. Contact your IT administrator or Open a Ticket to review your Teams meeting policies.
- If you are not the meeting organiser, you cannot change lobby settings. Ask the organiser to update the options.
External Guests Cannot Join at All
- Verify that Anonymous users can join a meeting is enabled in your Teams meeting policies if you want unauthenticated external users to bypass the lobby.
- Check that the guest’s email domain is not blocked in your organisation’s external access settings.
- Review your conditional access policies. Conditional access policies in Azure AD Premium P1 or P2 may block guest access even when Teams lobby settings are configured correctly.
Still Having Issues?
💻 Open a Ticket