If people keep bypassing the lobby after you changed the meeting, the setting may be correct but applied to the wrong event scope. Open the meeting as its organizer, edit Meeting access, select the intended audience under Who can bypass the lobby?, and choose Apply. For a recurring meeting, make sure you edit the series when the rule should cover future occurrences.
This is not always a local Teams problem. A meeting template, sensitivity label, or administrator policy can lock or override some controls. The useful approach is to separate an event-level mistake from a policy-level restriction before repeatedly toggling the same option.
Identify which lobby behavior is wrong
Write down what actually happened during a test join. “The lobby did not work” can describe several different conditions:
- An external guest entered directly.
- A dial-in participant skipped the lobby.
- A presenter admitted people although only organizers should do so.
- The change worked for one occurrence but not the next meeting in the series.
- The dropdown was unavailable or returned to an organization default.
Each symptom maps to a different control. Who can bypass the lobby? controls direct entry, while Who can admit from the lobby controls who can release waiting people. Dial-in behavior also has its own toggle.
Confirm you are the organizer
Open Calendar, select the meeting, choose View event, and then open Options. Use the account that created the event. A presenter can manage participants during a meeting, but that does not make the presenter the owner of every meeting option.
If the Options entry is missing from an Outlook-created event, first restore the calendar-side meeting controls before diagnosing lobby rules. That underlying integration problem can hide the path you need without changing the meeting itself.
Match the control to the audience
Under Meeting access, choose a value that reflects the invitation. For example, People in my org keeps guests and external people waiting, while Everyone is intentionally permissive. Microsoft notes that anonymous, untrusted, or dial-in participants can still be held temporarily by policy even when Everyone is selected.
Set Who can admit from the lobby separately. This prevents a broad presenter role from becoming an unintended admission role. Select Apply, close the options window, then reopen it once to confirm the saved value.
Handle recurring meetings without losing the change
A recurring series is the most common source of “ignored” settings. Editing one occurrence can leave the remaining meetings untouched. Open the event from Teams Calendar and choose the series-level edit when the lobby rule should remain consistent.
- Select the recurring meeting in Calendar.
- Choose the option to edit the series, not only this event.
- Open Options > Meeting access.
- Set lobby bypass, dial-in bypass, and admission roles.
- Select Apply, save the series, and reopen a future occurrence.
Do not test only with your organizer identity. Use a colleague, guest test account, or private browser session that represents the affected attendee type. A successful organizer join says nothing about lobby behavior for guests.
When Teams will not let the choice stick
Some controls can be unavailable because of an organizational meeting template or sensitivity label. Microsoft explicitly notes that these protections may set and lock options. In that situation, changing clients or clearing the Teams cache will not unlock the field.
A dropdown is locked or missing
Capture the meeting title, organizer account, affected option, and whether the meeting uses a template or sensitivity label. Ask the Teams administrator to compare the organizer’s assigned meeting policy with the template. The request should be about the specific control, not a broad demand to disable the lobby.
The saved value reverts later
Reopen the exact event and check whether it belongs to a series. Also confirm that a co-organizer did not intentionally update access settings. If values consistently return to a default across new meetings, the tenant’s default meeting policy is the more likely source.
For meetings where the participant role is also wrong, the role assignment walkthrough helps separate admission rights from presentation rights. Keeping those decisions distinct avoids granting broad control just to solve a lobby issue.
Prove whether the meeting or a policy controls the lobby
When a lobby choice is unavailable or keeps reverting, verify the saved meeting first and then separate that behavior from a template, sensitivity label, or administrator policy. Use a noncritical test meeting with the same organizer account as the affected meeting.
-
Record the intended audience
List who should bypass the lobby: people in your organization, guests, trusted organizations, anonymous users, or callers. Also decide who should be able to admit people. This prevents an apparently convenient setting from granting broader access than the meeting requires.
-
Save the controls on the event
In Teams, open Calendar, select the event, choose View event, and open Options. Under Meeting access, set Who can bypass the lobby, People dialing in can bypass the lobby when available, and Who can admit from the lobby. Select Apply, close the event, reopen Options, and verify that each value remained saved.
-
Look for an enforced control
If a dropdown is locked, missing, or resets immediately, check whether the meeting uses a template or sensitivity label. Those controls and the organizer's meeting policy can restrict the available choices. Do not create a new organizer account or remove a protection label as a workaround; record the locked field for the administrator.
-
Test the setting during the meeting
Join the test meeting as organizer. Open Controls, choose the additional meeting options, and review Meeting access. Have a trusted tester join using the same identity type that failed before, such as a guest or anonymous browser participant. Confirm whether the tester enters directly or waits in the lobby.
-
Escalate with reproducible evidence
If the saved value and actual behavior differ, give IT the meeting link, organizer, time, tester identity type, expected lobby choice, saved value, and observed result. Mention any template or sensitivity label. Repeat the test after the policy correction and confirm both the reopened option and the participant's join path.
Questions about Teams lobby settings
Why can someone still bypass the lobby when I selected People in my org?
The person may be joining with an account recognized inside your tenant, or through an allowed trusted relationship. Confirm the identity shown in the participant list and test with the exact external account that reported the problem. Dial-in participants also follow the separate dial-in bypass option and applicable admin policy.
Do changes made during a meeting affect people already waiting?
Microsoft says people already waiting remain in the lobby after you change lobby settings during the meeting. Apply the new rule, then admit or deny those participants manually. Test the updated behavior with a new join attempt.
Why does Everyone still place some callers in the lobby?
Tenant policy can temporarily hold anonymous users, people from untrusted organizations, or dial-in participants until someone from your organization joins. That safeguard can apply even when the event-level selection is Everyone. Ask IT to confirm the policy before assuming the dropdown failed.
Can I make one lobby rule the default for all new meetings?
Event options change a meeting or series, not the tenant-wide default. Microsoft directs users to their IT administrator for default lobby settings. Ask for the business requirement and audience type to be reviewed rather than copying a permissive value to every meeting.
Keep the next meeting predictable
Use organizer access, edit the correct occurrence or series, and verify all three lobby-related controls together. Then join as the attendee type that previously behaved incorrectly. If a field is locked or consistently reverts, stop repeating local fixes and have the administrator review the assigned policy, template, or sensitivity label.