Lag and Slow File Transfers in Cross-Border Microsoft Teams Meetings: How to Identify Causes and Improve?

How network paths differ between standard meeting calls, file transfers, and large live events

Within the same Teams application, real-time meeting audio/video and file transfers use two distinct transport mechanisms. For enterprises in mainland China connecting to a global (international) Microsoft 365 tenant, Microsoft documents an important technical fact in its public documentation (cited here strictly as technical background reference, not as an indication of official Microsoft certification or equivalent product capabilities):

• Real-time audio, video, and screen sharing in standard meetings already benefit from public internet path optimisations: Microsoft works with domestic telecom carriers in China so that real-time audio, video, and screen sharing in standard Teams meetings and calls (which use the real-time-friendly UDP protocol) travel directly over optimised public internet paths, significantly reducing packet loss for real-time calls.
• Text chat and in-meeting file transfers are not covered by this optimisation: Sending text messages or screenshots in the meeting chat window, or opening shared documents in channels (which call SharePoint and OneDrive in the background over TCP/HTTPS connections), is excluded from the public internet optimisation for real-time audio and video; when traversing the congested cross-border public internet, these actions remain prone to slow sending or endless loading spinners.
• Attendee streams for large live events and Town Halls are an exception: When an enterprise hosts large live events or Town Halls (Live Events / Town Hall), the video stream received by regular attendees is not covered by the real-time call public internet optimisation above; only organisers and presenters, who join and push streams as standard meeting participants, continue to use that path on the presenting side. Additionally, if external participants cannot join a meeting, the cause may be external collaboration permission restrictions on the enterprise tenant, which an administrator should check in the account backend.

As a result, enterprises do not need to assume that using Teams requires moving all traffic onto a new dedicated line; identifying whether the bottleneck affects standard calls, in-meeting files, or large live events leads to a much more targeted fix.

Why meeting lag is sometimes caused by conference room Wi-Fi or an existing VPN

If real-time audio and video in standard meetings already have public internet optimisations, why do voice and video still lag during cross-border meetings in some offices? In real-world office environments, the most common causes usually lie inside the office network or on an existing VPN running on employee computers:

1. Employee computers are running a full-tunnel VPN to overseas headquarters: This is the most common pitfall for foreign enterprises and multinational branches. If an employee's computer has a VPN enabled by default that routes all traffic to headquarters in Europe or North America, Teams audio and video that could otherwise take a nearby optimised path within China are forced through a cross-border encrypted tunnel to overseas headquarters—and may even fall back from real-time UDP transport to lag-prone TCP transport. Simply configuring split tunneling for Teams real-time calls at the office firewall or VPN level often eliminates this detour lag without extra spending.

2. Congested conference room Wi-Fi or firewall rules blocking voice ports: When multiple people turn on video and screen sharing simultaneously in a conference room, aging wireless access points or radio interference will cause blurry or frozen video (when the network is unstable, Teams automatically lowers video resolution to preserve audio first); additionally, if the office firewall blocks the UDP ports required for Teams real-time calls, call quality drops noticeably. These local conference room network and firewall rule issues can be identified together when we assist with an evaluation.

When to connect to our cross-border channel and what benefits it brings

When your enterprise faces any of the following three needs, we can establish a stable cross-border access channel for you through our Enterprise Dedicated Internet service:

• In-meeting file transfers, chat images, and shared documents frequently stall: We route Teams text chat, channel files, and associated SharePoint, OneDrive, and Outlook traffic over our cross-border transmission channel to connect to Microsoft's global network at a nearby overseas region, resolving the frustration of having working audio while presentation materials fail to send.
• Cross-border large live events, Town Halls, or specific overseas routes are chronically unstable: For attendees of large live events or cross-border meetings frequently affected by public internet fluctuations during peak office hours, our cross-border channel provides stable transport while preserving the UDP transmission conditions required for real-time audio and video end to end.
• Corporate security policies require unified outbound egress and logging for all office traffic: If company security rules prohibit employee computers from accessing external cloud services directly over local public internet breakouts, we can route office collaboration traffic through a controlled enterprise dedicated egress, maintaining smooth performance while meeting corporate governance requirements.

Connecting requires no changes to existing conference room broadband cabling—service can be provisioned quickly over your office's existing public internet broadband, and bandwidth capacity can be scaled up on demand for company-wide live events or peak cross-border meeting periods. Once live, your team can verify the improvement directly during daily cross-border standups, screen sharing, and file transfers.