You spent good money on a meeting room. There's a big screen, a video bar and a touch panel on the table, but meetings still start late. Remote people say they can't hear, the room sits in the lobby waiting to be let in, and somebody ends up running the call from their laptop anyway.
In our experience it's rarely the hardware. The problems that make a Teams meeting room frustrating are usually in the room design, Microsoft 365, or the network. These are the ones we see most often on real installs, what causes each one, and how to fix it.
1. Remote participants can't hear the people at the far end of the table
What it looks like: people near the screen come through fine, but anyone at the back of the room sounds distant, or drops out entirely.
Why it happens: the microphones were chosen for a smaller room. A video bar for a huddle room isn't built to pick up voices six or eight metres away, and a laptop microphone definitely isn't.
The fix: size the audio to the room, not the screen. For small and medium rooms, a bar like the MaxHub XBar V50 covers the table. For longer tables and boardrooms, the XBar V70 uses more microphones and picks up voices up to 10 metres away. If the room is long and narrow, plan for extra microphones down the table rather than turning the volume up.
2. Remote people can hear the meeting next door
What it looks like: remote callers hear background voices that aren't coming from your room.
Why it happens: on a recent whole-floor fit-out, the smart microphones were doing exactly what they're designed to do. Beamforming arrays and automatic gain pick up quiet voices, so they also picked up speech coming through a partition and across the shared ceiling void from the next room.
The fix: work from the cheapest end. First, narrow the microphone pickup zone and reduce gain in the device settings. Modern bars, including MaxHub's, have an audio fence that ignores voices outside a defined area. Only if that isn't enough do you need building work, and the place to look is usually the ceiling plenum, not the wall.
3. The room sits in the lobby until someone lets it in
What it looks like: someone books the room and invites it, but the screen shows "someone will let you in shortly" until the organiser joins and admits it.
Why it happens: everyone blames the Teams lobby policy. In the case we saw, the policy was fine. The room's account had been created as a user mailbox instead of a room mailbox, so Teams treated the device as a person, not a room.
The fix: convert the account to a room resource mailbox and set its calendar processing correctly. The room then auto-joins its meetings. This is an Exchange Online problem, which is why it's often missed when the installer only does AV.
4. The Teams Rooms licence won't attach to the room
What it looks like: the device is on the wall, but the licence assignment fails, so the room won't sign in properly.
Why it happens: the room account has no usage location set in Entra ID. Microsoft won't assign a licence to an account without one. It's a common trap when room accounts are created by script.
The fix: set the usage location to Australia. It's one field and takes thirty seconds once you know where to look.
5. Visitors can't save what's on the whiteboard
What it looks like: a client draws on the interactive board, scans the QR code to take the whiteboard away, and gets nothing.
Why it happens: the QR code points to the board itself, and the visitor's phone is on the guest Wi-Fi. A properly built guest network is isolated from the corporate network, so the phone can't reach the board. The isolation is working; it's just blocking a feature you want.
The fix: add one firewall rule that lets guest devices reach that single board on the ports it uses. Visitors get their whiteboard back, and the guest network stays isolated from everything else.
6. Glass walls, echo, and people walking past on camera
What it looks like: a hollow, echoey sound for remote callers, and the camera keeps reframing every time someone walks past the glass.
Why it happens: glass reflects sound, and AI cameras are designed to find people, including the ones in the corridor.
The fix: choose devices with good echo cancellation, and set a video fence so the camera only frames people inside the meeting area. MaxHub's XBar range has both. Soft furnishings help with echo more than most people expect.
7. The wrong device for the room
What it looks like: a huge board in a two-person huddle room, or a small video bar struggling in a 12-seat boardroom.
The rule we use:
| Room | Best fit | Why |
|---|---|---|
| Small meeting or huddle room where people want to write on the screen | Interactive board, 55 or 65 inch | One unit does display, camera, audio and whiteboard |
| Small or medium room with a good display already on the wall | Video bar (e.g. XBar V50) | Reuses the screen and adds camera and audio |
| Boardroom or long table | Video bar built for larger rooms (e.g. XBar V70), or a large board with extra audio | The camera and microphones need to reach the far end |
| Town hall or all-hands space | Large interactive board, 86 to 98 inch | Big enough for the back row, with remote staff on screen |
We install MaxHub XBoard V7 boards from 55 up to 98 inches. A board makes most sense where one unit can cover the room and the team actually works on the screen. Where the room is bigger, or the display is already there, a bar does the job better.
The pattern: it's rarely the hardware
None of the problems above were hardware faults. They were room design, Exchange, Entra ID and network issues. If your AV installer doesn't touch Microsoft 365, and your IT provider doesn't touch rooms, those problems fall into the gap between them and sit there.
Treat your rooms as Microsoft 365 objects first. Mailbox type, calendar processing, usage location and network access decide whether a room joins a meeting. Get those right before you blame the screen.
There's also a security angle, which matters if you hold ISO 27001 or are working towards Essential 8. Room devices are company devices. They should be enrolled, visible in Teams admin, and (on Teams Rooms Pro) under your Conditional Access and Intune policies like everything else.
A word on licensing
Every fix above works on the free Teams Rooms Basic licence, which covers up to 25 rooms. Teams Rooms Pro is AU$59.90 per room per month ex GST, billed annually (Microsoft AU RRP as at October 2026). It adds remote management and device alerting, so you hear about a fault before the 9am board meeting does. It also adds Front Row, split gallery across two screens and Conditional Access. The full comparison is in Teams Rooms Basic vs Pro.
Want a second opinion on your rooms?
If you recognise your meeting room in any of the above, tell us what's going wrong. We'll tell you whether it's a setting, a configuration change or genuinely the hardware, and what it would take to fix. If it is time for new rooms, we design, supply and install Microsoft Teams Rooms Australia-wide, configured against your Microsoft 365 tenant before they go on the wall.
Talk to us about your meeting rooms
The examples in this article come from our own installs, including a whole-floor MaxHub fit-out for a consulting firm.
Frequently asked questions
Why does my Teams Room wait in the lobby instead of joining the meeting? The most common cause is that the room account was created as a user mailbox instead of a room resource mailbox, so Teams treats the device as a person who has to be admitted. Converting the account to a room mailbox and fixing its calendar processing settings makes it join automatically.
Why won't a Teams Rooms licence assign to a room account? Check the account's usage location in Entra ID. Licences can't be assigned to an account with no usage location, which is a common trap when room accounts are created by script. Set it to Australia and the licence will attach.
Why can remote participants hear people in the next room? Beamforming microphones and automatic gain are designed to pick up quiet voices, so they also pick up speech coming through a thin partition or a shared ceiling void. Start by narrowing the microphone pickup zone and reducing gain in the device settings. If that isn't enough, treat the ceiling plenum between rooms, which is usually the path the sound is taking.
Should I get an interactive board or a video bar for a meeting room? Use an interactive board where one unit can cover the room and people want to write on the screen. Use a video bar where there is already a good display, or where the room is too big for a single board's camera and microphones to cover on their own.
Do I need Teams Rooms Pro to fix these problems? No. Every fix in this article works on the free Teams Rooms Basic licence. Pro (AU$59.90 per room per month ex GST, billed annually, Microsoft AU RRP as at October 2026) adds remote management, alerting and Conditional Access, which helps you find problems before your users do.