A meeting can sound terrible even when an internet speed test looks healthy. Before a Dubai office buys a faster connection or replaces every access point, it needs to establish whether the problem follows a person, a device, a room or the network path. That distinction changes both the remedy and the cost.
This guide provides a practical investigation sequence for business owners and the people supporting Microsoft Teams. It covers meeting audio, video and screen sharing; telephone-system faults may require additional investigation of the calling configuration or provider.
Start with one specific bad meeting
“Teams is slow” is difficult to investigate. Ask the affected person to record the meeting time, including the time zone, their location, device, headset and whether they used Wi-Fi, Ethernet or a VPN. For UAE teams working with overseas colleagues, record GST (UTC+4) explicitly so support can find the right session.
- Was audio breaking up, delayed, echoing or completely absent?
- Did the issue affect incoming sound, outgoing sound, video or shared content?
- Did everybody notice it, or only one participant?
- Did it begin after moving rooms, connecting a headset or starting another application?
Keep meeting identifiers in the support ticket rather than public messages. A screenshot of the relevant error may help, but remove confidential presentation content. The first useful outcome is a reproducible symptom, not a shopping list.
Separate equipment problems from connection problems
Run a short internal test meeting with an agreed colleague. Confirm the selected microphone and speaker, then compare a known-working headset with the original device. Close an unnecessary resource-heavy application and repeat the same activity. Change one variable at a time and record the result.
For example, if the same laptop and connection work well after changing the headset, investigate that headset, its connection and drivers before redesigning the office network. If several different laptops fail in one meeting room, investigate the shared room conditions. These are clues, not proof: a second fault may coexist.
ITZ's remote IT support service can help scope an investigation around symptoms, device checks and available logs. Request a Teams Call Quality Review with two or three dated examples and the number of people affected.
Ask the administrator to inspect the actual session
Microsoft's current Teams meeting troubleshooting guidance uses user, meeting and participant views in the Teams admin center. An administrator with an appropriate role can locate the user's Meetings & calls record, choose the meeting and inspect participant issues. Telemetry depth and retention depend on licensing, so collect evidence promptly.
Look at the affected session, not just the meeting's overall result. Packet loss means data did not arrive; jitter means arrival timing varied; round-trip time measures the journey to the remote endpoint and back. Device and compute issues can also explain a poor experience. A highlighted metric identifies a potential problem to investigate, not a complete diagnosis on its own.
Ask support to translate the evidence into a testable explanation: “The problem affected these users in this room during this interval; this is the next comparison we will run.” That is more useful to a business owner than a page of unexplained numbers.
Compare the network path without weakening security
With IT approval, compare the same laptop and meeting activity on an existing authorised wired connection. Record the room, time and network used. A good wired result and a poor wireless result make Wi-Fi a sensible next investigation, but the paths may also have different policies or routing.
Microsoft's network preparation guidance covers Wi-Fi planning, media prioritisation and VPN routing. A speed test alone does not test every real-time media condition. Ask IT to check wireless coverage, contention, busy-period demand and the path to Microsoft services. Any VPN or firewall change should follow an approved configuration review, not an employee disabling protection.
If problems are consistently room-specific, discuss a targeted business Wi-Fi assessment. Keep visitors on the intended network; the guest network isolation checklist explains why moving staff onto an unrestricted guest connection is not a satisfactory long-term fix.
Define what will count as an improvement
- Choose the affected rooms, device types and meeting tasks before making changes.
- Repeat audio, camera and screen-sharing tests at a representative busy time.
- Record participant experience alongside the available session telemetry.
- Confirm that normal security controls and required business access still work.
- Monitor subsequent real meetings and reopen the investigation if symptoms return.
A single successful call does not establish that every office condition is fixed. Keep a short change record with the original symptom, action, comparison results and unresolved limitations. Where infrastructure changes are needed, an office network review can define the implementation separately from initial diagnosis.
Request a Teams call quality review
Tell ITZ which users or rooms are affected, when the problem occurs and what comparisons you have already tried. Request a review of endpoint checks, available Teams diagnostics and network dependencies, with a documented next step. Do not send passwords or confidential meeting recordings through the enquiry form.
