Global Microsoft 365 Is Slow in China: How to Improve Document Collaboration and Email?

Confirm the account edition first and identify which specific daily operations are slow

Before discussing a network solution, one basic fact needs to be confirmed: whether your enterprise subscribes to the global edition of Microsoft 365 connecting to overseas clouds, or the edition operated independently within mainland China by 21Vianet.

For the 21Vianet-operated edition, service data centres and access lines are located inside mainland China, so daily access does not pass through international public internet gateways. By contrast, for the global tenants commonly used by multinational enterprises and companies expanding overseas, servers are deployed outside mainland China, meaning domestic offices must transmit data across borders when accessing them. Microsoft’s official performance documentation for users in China also notes that cross-border optimisation solutions are specifically intended for office locations within mainland China connecting to global tenants (Microsoft’s public documentation is cited here solely as technical background reference and does not imply official Microsoft certification or equivalent product capabilities).

At the same time, when reviewing employee feedback, distinguishing issues by specific software behaviour is much clearer than broadly saying “Microsoft office tools are slow.” If an entire office experiences slow SharePoint document loading, OneDrive syncing, or Outlook email sending and receiving during weekday business hours, it is often related to cross-border link congestion or office egress routing; if only individual workstations are affected, the cause may be an employee’s computer or unstable Wi-Fi signal in the room; and if multiple domestic and overseas offices report errors on the same day, it may be Microsoft cloud maintenance or account permission changes, which an administrator should check against service health and licence settings in the Microsoft admin centre.

Why the cross-border public internet and existing office settings slow down access

Slow access to the global edition of Microsoft 365 from domestic offices is mainly influenced by two factors:

On one hand is congestion and packet loss on the cross-border public internet. When employees open web documents, sync large folders, or send email attachments, data must pass through international gateways on the public internet. Once a cross-border link experiences congestion or packet loss, connections repeatedly stall, and employees see blank pages or frozen progress bars.

On the other hand, several common settings inside the office can further increase latency:

• Relying solely on web browsers: Every click in a browser has to pull data across borders in real time, whereas installing the desktop versions of Outlook, OneDrive, and Teams caches frequently used files locally and syncs automatically in the background, resulting in much better everyday opening speeds.
• Backhauling all traffic through a headquarters VPN in Europe or North America first: Many foreign enterprise branches default to routing all internet traffic from employee computers or office routers into a cross-border VPN back to headquarters in Europe or North America before connecting from headquarters to the Microsoft cloud. This long-distance intercontinental detour greatly increases round-trip wait times, and whenever the headquarters tunnel is busy, all documents and emails bog down with it.
• DNS resolution pointing to distant regions: If DNS resolution or web proxy settings on the office network are improperly configured and point Microsoft services that could be accessed in nearby regions to distant nodes instead, round-trip wait times also increase noticeably.

Note that enterprise network solutions primarily apply to company-managed office networks; if employees connect via personal mobile hotspots while on the go, or if local domestic broadband itself has a fault, those issues still need to be addressed on the local network side.

Why network performance differs between Teams meetings and file transfers or text chat

Many business leaders wonder: why can colleagues sometimes speak normally in a Teams voice meeting, while sending files during the meeting, posting group chat messages, or opening shared spreadsheets remains very slow?

According to Microsoft’s published technical documentation, Microsoft has partnered with domestic telecom carriers in China so that real-time voice, video, and screen sharing in standard Teams meetings and calls travel directly over optimised domestic public internet paths, significantly reducing packet loss for real-time calls. However, this public internet improvement has clear scope limitations:

• Text chat and file transfers are not covered by this public internet optimisation: Text messages, group chat images, and channel file transfers in Teams—as well as the underlying SharePoint, OneDrive, and Exchange email services—travel over separate data channels and remain susceptible to congestion when crossing the standard cross-border public internet.
• Attendee streams for large live events differ from standard meetings: When an enterprise hosts a large live stream or Town Hall, the channel over which regular attendees receive video is not covered by the real-time call public internet optimisation described above; however, because event organisers and presenters join and push streams using the standard meeting mechanism, the presenting side can still benefit from that path.

Once this distinction is clear, enterprises do not need to assume that every bit of Teams traffic requires buying a new dedicated line; instead, you can work with us to plan traffic routing around the specific operations that are actually lagging.

How we improve access over existing broadband and how we can work together

For SharePoint, OneDrive, Outlook, and Teams text, file, and large event scenarios affected by cross-border public internet congestion, Microsoft’s official documentation recommends carrying traffic from office locations in China over a private enterprise network to a location outside mainland China (such as low-latency interconnect regions like Hong Kong, Singapore, Japan, or South Korea cited as examples in Microsoft’s documentation) before connecting to Microsoft’s global network. In practical deployment, we use our Enterprise Dedicated Internet service to plan a stable cross-border access channel tailored to your site footprint and the access regions we deliver.

In deployment and daily use, this approach saves enterprises significant effort:

• Connect directly over existing office broadband: Each office location can connect to our cross-border channel over its existing internet broadband, avoiding the wait for new physical dedicated line applications and construction; if office headcount grows later or intensive file syncing is needed, bandwidth can also be scaled up on demand at any time.
• Route traffic on demand to balance meetings and document collaboration: Referencing Microsoft’s published service categories, we can help steer lag-prone core office and document traffic onto the dedicated channel while keeping general web browsing on the office’s existing broadband; for Teams real-time audio and video, you can either continue using the existing optimised public path or include it in the dedicated channel when unified egress management is required.
• Plan together with multi-site office and multi-cloud networking: If your enterprise also needs to connect multiple domestic and overseas offices and public clouds—for example, we helped a Suzhou precision equipment manufacturer connect 10 domestic and overseas offices and 5 public cloud environments into a single network with centrally planned dedicated internet egress—cross-border Microsoft 365 access can be coordinated directly within the same network.

During implementation, settings involving corporate egress rules, encrypted transmission, and connection log retention are confirmed in alignment with your enterprise’s security management policies and applicable local laws and regulations; after launch, performance can be verified directly by how smoothly employees open SharePoint documents, sync OneDrive files, and send and receive emails during peak office hours.