Insights

Bad meeting rooms: find the faults before buying more hardware

13 October 2026

Run a Teams meeting-room audit covering sound, cameras, guest access, licensing, network quality and support ownership before replacing equipment.

Logitech has highlighted meeting-room friction in a sponsored ARN article promoting its conferencing equipment. For Australian Microsoft 365 workplaces, the useful question is not how widespread the problem might be, but whether your own rooms work reliably. A Teams meeting-room audit can identify what needs fixing before you commit to replacement hardware.

The Logitech-sponsored article on ARN presents Logitech’s perspective on hybrid collaboration. Its product promotion is not a substitute for testing your environment. Start with evidence from your rooms, your users and the people joining remotely.

Start your Teams meeting-room audit with a baseline

List each room’s capacity, equipment, connection method and support owner. Distinguish dedicated Microsoft Teams Rooms systems from rooms where users connect their own laptop to a display, camera and speakerphone. They have different management and licensing requirements.

Run a normal meeting with someone outside the office. Use an ordinary employee account, not an administrator account, and follow the instructions actually available in the room.

Record:

  • Time from entering the room to a usable call.
  • Whether the invitation appears and the room can join as expected.
  • Whether remote attendees can hear every seat and see relevant participants.
  • Whether content sharing works without changing several cables or settings.
  • Any intervention needed, including who provided it.

Repeat the test during a busy period. Keep a fault log with the room, time, meeting platform and symptoms. This gives your Teams meeting-room audit a baseline without relying on vendor estimates.

Test audio pickup from every seat

A camera can look impressive while the room remains difficult to use. Audio should be the first acceptance test because unclear speech prevents participation even when the video is sharp.

Have someone speak at a normal volume from each seat, including the far end of the table. Ask the remote participant to check intelligibility, not just whether sound is present. Test with ventilation running, laptops open and the door in its usual position.

Then check overlapping speech. Can a remote attendee interrupt politely without their voice disappearing? Does the room hear an echo when someone joins on a laptop as well as the room system?

Check microphone coverage, speaker level and room acoustics separately. Moving a microphone or reducing hard-surface reflections may help more than replacing the camera. If several people join individually from the room, keep only the intended room audio connected to avoid feedback.

Document the selected microphone and speaker devices. A successful test should not depend on one employee remembering a hidden setting.

Position the camera for conversation, not just coverage

Inspect the remote view with the room occupied. An empty-room preview will not reveal blocked faces, awkward seating angles or people outside the frame.

Check whether the camera sits close enough to the display to support natural conversation. A camera far to one side can make participants appear to be looking away. Avoid strong backlighting from windows, and confirm that the nearest seat is not disproportionately large in the picture.

Test any automatic framing with people entering, leaving and speaking from different seats. Establish whether the resulting view is useful rather than assuming automation improves every layout.

If whiteboards matter, test them explicitly. A wide-angle view of the room may not make handwriting readable. Choose a supported content-capture method or share a digital whiteboard, and confirm external participants can access what they need.

Include readable shared content in the Teams meeting-room audit, not just visible faces.

Rehearse guest joining in both directions

“Guests can join” can describe several different workflows. Test each one your business actually uses:

  • An external participant joining a Teams meeting hosted by your organisation.
  • Your room joining a Teams meeting hosted by a customer or supplier.
  • Your room joining another meeting platform through a supported method.
  • A visitor presenting from their own laptop.

Check lobby behaviour, who can admit attendees, invitation delivery and content sharing. Cross-platform joining depends on the room platform, configuration and supported capabilities; do not assume it offers the same experience as a native Teams meeting.

For visitor presentations, identify the approved cable or wireless method and test it without installing unexpected software. Keep a labelled spare adapter where appropriate.

Do not loosen organisation-wide meeting policies simply to resolve one room’s problem. Confirm the intended external access and meeting controls with your Microsoft 365 administrator. Our Microsoft 365 hardening guide explains why usability and security settings should be considered together.

Verify licensing, room accounts and management

Include a licensing review in your Teams meeting-room audit. A room mailbox, a user’s Teams licence and a dedicated Teams Rooms licence serve different purposes; do not treat them as interchangeable.

Ask your administrator or licensing partner to confirm the current Microsoft requirements for each deployed system. Verify that the assigned Teams Rooms licence supports the features and management capabilities you intend to use. Check separate scheduling panels and associated devices against their current requirements too.

Review the room resource account, calendar processing and booking permissions. Confirm that legitimate invitations appear as intended without unnecessarily exposing meeting information.

Also inspect device health, supported software versions and update arrangements. Apply Microsoft’s current room-specific identity guidance rather than copying employee sign-in policies blindly. Conditional Access must protect the environment while remaining compatible with the device’s supported authentication flow.

Record who monitors account failures, licence changes and unsuccessful updates. A room that works today still needs ongoing administration.

Check network quality during real calls

A successful speed test does not establish meeting quality. Real-time media is also affected by packet loss, jitter, latency and congestion.

Where practical, use a supported wired connection for fixed room equipment. Check the switch port, cabling, available capacity and any power requirements. For wireless equipment, inspect signal quality, interference and contention at the actual device location.

During a problem call, collect available Teams call-quality information and correlate it with network events. Check whether faults coincide with backups, large uploads or busy office periods.

Validate firewall, proxy and traffic-routing settings against Microsoft’s current connectivity guidance. Quality of service can help prioritise traffic on networks you control, but it cannot repair an unreliable internet service or missing capacity.

Segmentation also needs care. Room systems should have the access they require without unnecessary access to unrelated business devices. Our network segmentation checklist provides a starting point; test discovery, control and joining again after network changes.

Assign one owner and turn findings into actions

Meeting rooms often span facilities, IT, an audiovisual installer and an internet provider. That is manageable only if someone owns the incident from report to resolution.

Nominate one accountable service owner for each room. Document who handles hardware, Microsoft 365 settings, networking, warranties and on-site attendance. Put a short support instruction beside the controller, including a room identifier and a fallback method.

Turn the Teams meeting-room audit into an action register. For each fault, record its impact, likely cause, owner, next action and retest date. Prioritise recurring failures that prevent participation before cosmetic improvements.

Measure your own results: start delays, support requests and repeat faults. If estimating lost staff time, distinguish that estimate from direct financial savings. Use the same test meeting after each change so improvements are observable.

Make reliable rooms part of Microsoft 365 management

The aim is a room that ordinary staff and visitors can use without specialist help. Clear instructions, suitable equipment, supported configuration and accountable support all contribute.

Tech Engine can help configure, secure and manage Microsoft 365, with managed IT and networking support for the room environment. To discuss a Teams meeting-room audit, call 1300 088 324, email sales@techengine.au or visit aiaas.au.

Want this applied to your business?

Request an AI Blueprint and we will map the processes worth automating first.

Request an AI Blueprint