Teams says 'someone in the meeting' but no one is admitting you — fix the lobby trap

It's 9:58 AM. The all-hands started two minutes ago. Your screen says Someone in the meeting should let you in soon, you can see the attendee count quietly creeping up on the lobby card, and nobody — not the host, not the co-host, nobody — is letting you in. You can hear, faintly, your dog barking at the postman. The room is otherwise silent. You sit there.

Welcome to the Teams lobby trap.

Look — this is almost never a network problem. I get emails about it every week and people always assume it's their VPN or their Wi-Fi or some weird firewall thing. It's not. It's a settings problem. Almost always a settings problem nobody knew was on. And once you understand the four causes, you can usually unstick yourself in about thirty seconds without even bothering the host.

What the lobby actually is

Every Teams meeting carries a lobby setting. The organiser chose it (or, more accurately, accepted whatever the default was) when the meeting got created. That setting decides who has to wait for somebody to click "admit" and who walks straight in.

If you're sitting in the lobby and you didn't expect to be, one of these is true:

• The organiser set lobby rules tighter than you guessed.
• You joined as a guest or anonymous user when the organiser thought you were going to be signed in.
• You signed in with the wrong identity. Personal Microsoft account vs work account, that kind of thing.
• The tenant has a global policy that silently overrides the meeting's own setting.

Knowing which one applies tells you whether to just wait it out, switch accounts, or pick up the phone.

Who actually skips the lobby

In a meeting's options, Who can bypass the lobby? has these choices:

Setting	Bypasses lobby
Only organisers and co-organisers	Just the organiser and named co-organisers
People I invite	Anyone explicitly named on the invite (must be signed in to that account)
People in my organisation	Anyone signed in with a tenant-issued account
People in my organisation, trusted organisations, and guests	Tenant users plus federated/guest accounts
Everyone	Anyone with the link, including anonymous users

Most enterprises default to People in my organisation and guests. The two settings that catch people out the most:

1. People I invite is strict. If the organiser added you via a distribution list (e.g. engineering-all@company.com) instead of your individual address, Teams might not match you to that list and dump you in the lobby. I've seen this happen even to invited people whose names appear right there on the calendar invite.
2. People in my organisation does NOT include guests. Even guests who have a guest account in the tenant. If you're an external collaborator and the organiser picked this setting thinking it was inclusive — you sit in the lobby. Forever, potentially.

Why guests get parked even when the host wanted them in

This is the most common scenario I get asked about. Picture it. External user accepts a Teams invite. Joins on time. Lands in the lobby. Organiser swears up and down that they "added you to the meeting." But you sit there.

Here's what's happening behind the scenes. People I invite matches against the email address on the invite, but only when you're signed into Teams with that exact email. If the invite went to you@gmail.com and you're signed into Teams as you@yourcompany.com — Teams sees an unrecognised identity and treats you as anonymous. Boom. Lobby.

The fix in the moment:

• Sign out of Teams completely. Or — easier — open the meeting link in a private/incognito browser tab.
• Click the join link again.
• Choose Continue on this browser when prompted, sign in with the email that received the invite.
• If that email doesn't have a Teams account, pick Join as a guest and use the exact display name you'd want the organiser to see in their admit list. (If your name is "Sam" but your email says "Samantha", picking "Samantha" makes you easier to recognise.)

I've watched people lose ten minutes of a meeting over this. The whole fix takes forty seconds once you know.

The "Anonymous users can join a meeting" tenant block

Even with a permissive meeting policy, a tenant administrator can globally block anonymous joins. If they have, the Join as a guest option will silently fail. You'll enter your name, click Join Now, land in the lobby, and never get admitted. Because nobody can admit you. The system literally won't show you to the host.

You cannot tell this is the problem from the join page itself. There's no error message. It just... doesn't work.

The fix is to join with an actual account — any account from any tenant Teams recognises will at least change your status from anonymous. If you don't have one and can't get one, your only options are: ask the organiser to either change the tenant policy (this is rarely a thing they can do quickly — it's an admin-level change) or share the meeting content over a different channel like a Zoom link or a shared screen recording later.

Dial-in by phone is the trick nobody mentions

This is the single most useful workaround in the entire article. Genuinely. If you remember one thing, remember this.

Most Teams meeting invites include a phone number and a conference ID near the bottom of the invite. Phone joiners get governed by a separate setting — People dialing in by phone bypass the lobby — and the default in a lot of tenants is on.

Stuck in the lobby and the meeting has dial-in details? Try this:

• Don't close your laptop's lobby waiting screen.
• Pull out your phone. Dial the number, enter the conference ID followed by #.
• You'll usually land directly in the meeting audio. No waiting.
• Then go back to your laptop. Click Join meeting audio off / camera off to bring video and screen-share into the same session. Often this won't re-trigger the lobby because you're already a known attendee on the call from the phone leg.

Works on something like seven out of ten corporate Teams configurations I've tried it on. Worth attempting every single time you're stuck.

The lobby card is silent — go find the host another way

Here's a UX failure I'll never stop being annoyed about. The lobby card on your screen has no button that pings the host saying "hey, I'm out here." The organiser has to be actively watching the lobby to admit you. And in 90% of meetings I sit in, the organiser is heads-down sharing slides and has zero idea anyone is waiting.

So. Don't just wait. Reach out:

• Open a Teams 1:1 chat with the organiser and write "I'm in the lobby." That pings them in their main Teams client even when they're not watching the meeting window.
• No Teams chat with them? Send a fast Outlook email with subject LOBBY in caps. Lots of people have email banner alerts even when Teams meeting controls are minimised.
• Both fail? Text them. Or call. If you have the number.

Teams shows a small "1 person waiting" pill in the meeting controls but it doesn't blink, pop, or make a sound. Honestly that's a design choice I'd love to see Microsoft revisit. Until they do, you have to break the silence yourself.

When the organiser is the only allowed presenter and they're late

Particular flavour of disaster. Meeting was set to Only organisers and co-organisers can present, lobby is set to Only organisers and co-organisers, and the organiser is running late. Everyone else is locked outside watching paint dry.

What you can do:

• A co-organiser, if there is one, can admit folks. Check the calendar invite carefully. Co-organisers are listed in meeting options, not always visible right on the invite. Ask around if anyone's a co-organiser.
• No co-organiser? Nobody inside the meeting can admit you. The meeting is functionally on hold until the organiser shows up, even if twelve other people are sitting in the meeting room staring at each other.
• The organiser can fix this from their phone. Tap the meeting in their Teams calendar → Meeting options → change Who can bypass the lobby. Works even before they've joined from a laptop. Takes about thirty seconds.

If you ARE the organiser and you're running late — change the lobby setting from your phone while you're walking to your desk. Don't make eight people wait while you boot a laptop.

Switching accounts when the host is unreachable

If sign-in surgery is faster than getting the host's attention, here are the fastest routes:

• Teams desktop client: top-right account menu → Sign out → sign back in with the account that was actually invited.
• In a browser: open the join link in an incognito/private window. Teams prompts for fresh credentials. Fastest test for "is it because I'm signed in wrong?"
• Mobile: long-press the join link, choose Open in browser, sign in fresh. The Teams mobile app has an irritating habit of locking you to one account.

If you've got both a personal Microsoft account and a work account on the same machine, this is almost certainly your problem. Teams auto-picks whichever account was used most recently for some other Microsoft service — could be Xbox, could be your kid's school OneDrive, could be anything — and that account doesn't match the invite.

One last thing — the "you're already in" loop

Rare but worth knowing. Sometimes you'll get into the meeting on your laptop, then want to also bring up the meeting on your phone for backup audio, and your phone says you're already in the meeting and won't let you join. That's not a lobby issue. That's Teams' single-session-per-account rule. Sign into the phone with a different account, or accept that you can only be on one device. (Or use the dial-in number from your phone, which counts as a different "device" from Teams' perspective.)

So basically

The lobby isn't broken. It's doing exactly what it was set up to do. Your job in the moment is identifying which of the four causes is yours: wrong account, guest with no admission, anonymous block, or organiser not paying attention. Try dial-in. Sign out and back in with the right address. Ping the organiser somewhere else. And if you're the host running late — fix the lobby from your phone before you sprint to your desk.