Does Microsoft Teams Work in China? A 2026 Guide

Yes — Microsoft Teams works in China, with caveats worth understanding before you rely on it. On a global Microsoft 365 tenant, Teams is reachable from the Mainland but its calls and meetings degrade through China’s congested international gateways unless you add licensed cross-border connectivity. For a larger China workforce or data-residency needs, Teams also runs natively on Microsoft 365 operated by 21Vianet — China’s in-country tenant — with no VPN required but a narrower feature set. The two worlds can be bridged: staff on the China tenant can chat, call and meet with colleagues on your global tenant once cross-cloud communications are switched on at both ends.

This guide is the Teams-specific companion to our full Microsoft 365 in China decision guide. Where that pillar covers the whole tenant architecture — identity, email, compliance, the roll-out checklist — this post stays narrowly on Teams: whether it works, what actually breaks, the global-versus-21Vianet split, the Copilot gap, cross-border meetings, and how to make calls usable.

Does Microsoft Teams work in China?

Yes — on a global tenant Teams connects from Mainland China, and on the 21Vianet tenant it runs natively in-country. What changes between the two is performance and features, not whether Teams functions at all. The honest framing is “it works, but on a global tenant it is degraded over ordinary internet circuits” — a problem you fix with network design or by moving in-China users onto the local tenant. The rest of this guide unpacks both routes.

Is Microsoft Teams blocked in China?

No. Teams on a global tenant is not on China’s standing block list. Unlike Google, Meta’s apps and WhatsApp — which the Great Firewall blocks outright — Microsoft’s endpoints stay reachable from the Mainland. Microsoft itself never describes Teams as blocked; its official guidance frames the problem entirely as performance: congestion, packet loss and latency, not a wall.

The practical experience matches that. Outlook, Teams and the rest of Microsoft 365 connect from China; they are simply slow and inconsistent over ordinary internet circuits. So the honest answer to “is Teams blocked in China?” is “no, but it is degraded” — a very different problem with a very different fix.

One caveat: the Great Firewall is dynamic, not a fixed list. Reachability is the normal state, not a guarantee — connectivity reliably worsens around major political events, and short disruptions to foreign services do occur. If you want the underlying mechanics of how a permitted service still ends up slow, we cover why permitted services still run slowly from the Mainland in detail; this post states the conclusion and moves on.

What actually breaks on Teams — and why

The root cause is structural, and Microsoft is unusually candid about it. In its own words, “China ISPs have regulated offshore connections to the global public Internet that go through perimeter devices that are prone to high-levels of cross-border network congestion,” and “this congestion creates packet loss and latency for all Internet traffic going into and out of China.” It is worst, Microsoft notes, for large data exchanges and anything “requiring near real-time performance (audio and video applications).”

Teams is, of course, exactly an audio and video application. So it sits at the most sensitive end of that spectrum. On a poorly-routed connection from China, what users feel is:

• Calls and meetings first — choppy audio, frozen or black-screen video, and noticeable lag on screen-share. Real-time media has no tolerance for packet loss, so it is the first thing to suffer.
• Sign-in and authentication next — slow or failed logins and MFA prompts, because the authentication round-trips also cross the congested gateways.
• SharePoint and OneDrive sync — file sync can be severely degraded and effectively unusable cross-border without offshore routing; large uploads stall.
• Large file transfers last — attachments and bulk transfers crawl.

Treat that ordering as the typical pattern rather than a measured benchmark — Microsoft confirms real-time media and large transfers are the most fragile; the precise ranking is practitioner experience, not a published figure.

Microsoft’s own media optimisation (and its narrow scope)

There is one genuinely important 2024-onward nuance, and it is easy to mis-state. Microsoft has partnered with telecom providers to give Teams and Skype real-time media a preferential cross-border path, which it credits with a “more than ten-fold improvement in packet loss.” That is real and it matters — but its scope is narrow. It applies to calls and meetings only. In Microsoft’s words, “data from other Microsoft 365 services — and other traffic in Teams, such as chat or files — won’t directly benefit.” For Teams Live Events, only presenters and producers see the benefit, not ordinary attendees.

The takeaway: your Shanghai team’s call quality may be better than you expect even on a plain connection, while chat history loading, file access and SharePoint stay slow. The media path helps the live conversation; it does nothing for everything around it. That is why a network fix is still the right answer for a serious China operation.

The two worlds: global tenant vs Microsoft 365 operated by 21Vianet

There are effectively two different Teams services in play, and choosing between them is the central decision.

The first is your global tenant — the ordinary, worldwide Microsoft 365 most companies already run, reachable from China but subject to the congestion above. The second is Microsoft Teams operated by 21Vianet, a physically separate China instance that launched on 1 April 2023 under a “global-connected, local-operated” model. In Microsoft’s description, it “is a physically separated instance service located in China,” “independently operated and transacted by 21Vianet” (Shanghai Blue Cloud) under Chinese law, “powered by technology that Microsoft has licensed to 21Vianet.” Data stays resident in China, it lives in its own namespaces (*.onmschina.cn, teams.microsoftonline.cn), and — crucially — it needs no VPN, because it runs inside the Firewall rather than across it.

The 21Vianet service solves the performance problem for in-China users by definition. But it buys that with a materially reduced feature set, because it is built on China’s sovereign cloud. Here is the practical compare.

	Teams on global tenant	Teams operated by 21Vianet
Where it runs	Microsoft’s worldwide cloud, accessed across the Firewall	A separate instance hosted inside China
Performance for China users	Degraded by gateway congestion unless you add offshore routing	Native, in-country — no Firewall to cross
VPN / connectivity needed	Practically yes for reliable quality (licensed link)	No
Data residency	Outside China (your global region)	In China
Who you buy from	Microsoft directly	21Vianet or a certified partner; in practice needs a Mainland business licence
Copilot / M365 Copilot	Available (incl. Hong Kong)	Not available in mainland China
Feature parity	Full	Reduced — see below

As of the February 2026 service description, the China service runs across Business Basic / Standard / Premium, E1/E3 and F1/F3, but with a long list of features it does not support:

• Voice and PSTN calling, and Audio Conferencing / dial-in
• Live Events / Townhall and Webinars
• Shared Channels, and the richer extensions of cross-cloud meeting interop
• Meeting transcription, Whiteboard, the newer meeting notes, and post-meeting attendance reports
• Teams-certified devices such as Teams Phone and meeting-room systems
• Third-party apps and bots (first-party apps run with limited functionality)

The maximum team size is also 10,000 members rather than 25,000. Microsoft says features will “come closer to full feature parity over time” and that the table “may change without notice” — so treat any single gap as point-in-time and check the live service description before you design around it.

Standing up either service correctly — provisioning Teams, configuring policies, and any tenant-to-tenant migration — is a build job. PTS plans and runs the Microsoft 365 setup, migration and support for both global and 21Vianet tenants, including the cross-cloud configuration below.

The Copilot and AI gap

If AI in Teams is part of your plan, the China answer is blunt: Microsoft 365 Copilot is not available on the 21Vianet tenant. Microsoft’s own supported-regions guidance lists “regions like China (excluding Hong Kong) and embargoed markets where Copilot is either not available or not supported,” and the sovereign-cloud roadmap does not currently include China. Some Copilot admin experiences — the Copilot Dashboard among them — have also been absent from national clouds.

Two distinctions matter. First, Hong Kong is not the Mainland: a Hong Kong user on a global tenant can get Copilot. Second, this is an availability question, not a value question — if you are weighing whether the licence earns its keep at all, that is a separate analysis we cover in whether Copilot is worth it for your team. For China specifically, the planning rule is simple: if your Mainland staff need Copilot in Teams today, they need it on a global tenant, not on 21Vianet — and you should verify current status before committing, because national-cloud coverage is evolving.

Can China and overseas staff meet on Teams? Cross-cloud collaboration

This is the question that decides whether the 21Vianet route is even viable for most firms, and the answer is yes — with configuration. A user on the China (21Vianet) tenant and a colleague on your global tenant can chat, call and meet through Teams, because Microsoft supports cross-cloud communications between the two: cross-cloud authenticated meetings and cross-cloud guest access are both designed in.

The important word is configuration. The two tenants live in two separate Azure clouds and are never merged into one — they cooperate only if administrators on both sides opt in. That means enabling cross-tenant access (turning the Azure China connection on, and adding the partner by Tenant ID) in each tenant. It is not automatic, and it is bidirectional: switching it on in your global tenant alone does nothing. There are limits, too — B2B Member accounts are not supported across the cloud boundary, and Shared Channels (B2B direct connect) do not cross clouds, so collaboration is the guest-and-meeting model, not full shared-channel membership.

For a typical foreign company this works well enough: your Shanghai colleague joins your global Teams meeting, and chat and calls flow both ways, once the cross-cloud settings are in place at both ends. The pillar guide covers the identity and B2B detail at architecture altitude; the point to hold onto here is that the capability exists, but someone has to switch it on deliberately in both tenants.

How to make Teams usable from China: the connectivity fix

For organisations staying on the global tenant, fixing Teams is a network problem with a network solution, and our China IT team designs and runs the tenant and connectivity end to end. Microsoft’s own primary recommendation is unambiguous: “the primary goal should be to avoid accessing global Microsoft 365 services from the Internet in China if possible.” Instead, route that traffic over a private WAN or leased line that egresses offshore — Microsoft names Hong Kong, Singapore, Japan and South Korea as example exit points — or over a corporate VPN without split-tunnelling for Microsoft 365.

A few practitioner points that matter for Teams specifically:

• Use the rich desktop clients, not web. Microsoft is explicit that cached clients (Teams, Outlook, OneDrive desktop) “can dramatically reduce the impact of network congestion and latency,” and advises avoiding web-based clients. On a congested link this is one of the cheapest wins available.
• Keep a PSTN dial-in fallback where Audio Conferencing is licensed, so a meeting can survive when video does not.
• ExpressRoute is not the lever people assume. Microsoft no longer recommends ExpressRoute for Microsoft 365 and authorises it “only in the rare scenarios where it is necessary.” The China lever is offshore private egress, not ExpressRoute.
• There is a split-routing pattern worth knowing: route everything offshore except Teams real-time media (Microsoft’s Optimize endpoint set, currently endpoint ID 11), which can take the public-internet preferential media path. That keeps call quality high while sending everything else over the private link. Microsoft does reorder its endpoint list periodically, so confirm the current Optimize endpoint IDs before you pin firewall rules to a number.

The connectivity itself must be a licensed cross-border circuit from an authorised Chinese carrier — MPLS, an IPLC dedicated line, or a licensed SD-WAN service — not an improvised tunnel. We compare licensed MPLS, SD-WAN and IPLC in their own guide; this post’s job is only to say that this is the category of fix, and to hand off the cost, lead-time and design detail there. Note Microsoft is deliberately neutral on products — it states it “has no recommendations on the use of SD-WAN or VPN solutions,” so the choice of carrier and circuit is an engineering and compliance decision, not a Microsoft endorsement.

”Can’t I just use a VPN to make Teams work?”

Not the way most people mean it. A consumer VPN is the obvious reflex, and it sits in a genuine grey area. The compliant path is a licensed corporate cross-border line — a MIIT-approved circuit from an authorised basic-telecom operator — which thousands of multinationals run on lawfully. Unauthorised or consumer circumvention VPNs are non-compliant for this use in the Mainland and can attract penalties, and enforcement is reported to have tightened. We set out the compliant-versus-grey distinction in why a consumer VPN isn’t the answer; the short version is that the fix is a licensed line, not an app store download.

The compliance lens: PIPL, data residency and MLPS

Performance is rarely the only driver of the tenant decision — and for many companies, compliance is the bigger one. Three regimes shape it.

Hosting Teams data inside China (the 21Vianet option) keeps personal information resident in-country, which can simplify your data-residency position. But moving data out of China — which a global tenant inherently does — engages PIPL’s cross-border transfer rules. Above defined thresholds you need one of three mechanisms: a CAC security assessment, a China standard-contract filing with a personal-information impact assessment, or CAC certification (whose measures took effect on 1 January 2026). Below 100,000 individuals of non-sensitive personal information a year, transfers are generally exempt. These thresholds move, so confirm current numbers with China counsel before relying on an exemption.

Separately, MLPS 2.0 — China’s cybersecurity grading scheme — applies to your China systems regardless of which Teams you run, and a cloud platform’s own certification does not cover your tenant. None of this is legal advice; the point is that the right Teams choice is usually decided on compliance and data sensitivity at least as much as on call quality.

Not legal advice — China’s data rules change frequently. Use this as orientation and confirm current thresholds, licensing and filings with qualified China counsel before you commit.

Which option fits which business?

As a rule of thumb — and it is guidance, not a formula, because the deciding factors are genuinely case-specific:

• A small office, light data, mostly meeting overseas colleagues usually fits the global tenant plus a licensed offshore breakout. You keep full features and Copilot, and you fix call quality with connectivity. This covers most foreign SMEs.
• A larger China workforce, China-resident data needs, or a strong data-localisation driver points toward 21Vianet (often alongside the global tenant as a dual-tenant setup), accepting the reduced feature set and configuring cross-cloud so the two sides still meet.
• In between, the answer turns on data volume and sensitivity, sector, and whether you hold a Mainland entity at all — note you cannot buy 21Vianet directly from Microsoft, and onboarding in practice requires a Mainland business licence, so a foreign HQ without a China entity goes through a local partner.

The full decision tree — the user threshold, identity design and roll-out checklist — lives in the global vs 21Vianet tenant decision guide, and if a tenant move is on the cards, our step-by-step Teams migration checklist walks the mechanics.

Microsoft Teams in China FAQs

Does Microsoft Teams work in China?

Yes. On a global Microsoft 365 tenant, Teams connects and runs from Mainland China — it is not blocked — but calls, sign-ins and file sync degrade through the congested international gateways unless you add a licensed cross-border link. For in-China users you can instead run Teams natively on Microsoft 365 operated by 21Vianet, which is hosted inside China and needs no VPN, at the cost of a narrower feature set. Most foreign firms either fix connectivity on the global tenant or run a dual-tenant setup with cross-cloud communications between the two.

Is Microsoft Teams blocked in China?

No. Teams on a global tenant is reachable from Mainland China and is not on the standing block list, unlike Google, Facebook and WhatsApp. The problem is performance, not blocking — calls, sign-ins and file sync degrade through China’s congested international gateways. Businesses fix this with a licensed cross-border circuit, or sidestep it entirely by using Microsoft Teams operated by 21Vianet, which runs inside China. Bear in mind the Great Firewall is dynamic, so reachability is the normal state rather than a guarantee.

Is Microsoft 365 blocked in China?

No — a global Microsoft 365 tenant is reachable from the Mainland, but performance is often poor: slow Outlook sync, choppy Teams calls, and SharePoint and OneDrive file sync that can be severely degraded and effectively unusable cross-border without offshore routing. The fix is to avoid egressing Microsoft 365 onto the public internet in China and instead route over a licensed private link that exits offshore (Hong Kong, Singapore, Japan or South Korea), or to adopt the separate China cloud operated by 21Vianet for in-country users.

Does Teams work in China without a VPN?

On a global tenant it will connect without a VPN, but call and meeting quality on a plain home, mobile or hotel connection is inconsistent — expect variability rather than reliable performance. Quality is far better over a corporate-controlled, licensed cross-border link. The one route that genuinely needs no VPN at all is Teams operated by 21Vianet, because it is hosted inside China and never crosses the Firewall.

Is Copilot available in Teams in China?

Not on the 21Vianet tenant. Microsoft excludes mainland China (Hong Kong aside) from Microsoft 365 Copilot, and the China service does not offer it; some Copilot admin experiences have been absent from national clouds too. A Hong Kong user on a global tenant can use Copilot. If Copilot in Teams matters for your Mainland staff today, they need to be on a global tenant — and you should verify current availability, as national-cloud coverage is evolving.

Can China staff join Teams meetings with overseas colleagues?

Yes. Teams supports cross-cloud communications between the 21Vianet China tenant and your worldwide tenant, so a Shanghai colleague can chat, call and join meetings with global users. The requirement is that administrators on both sides enable cross-tenant access — it is not automatic, and the two tenants remain separate. Once configured, collaboration works through the guest-and-meeting model; shared channels and B2B member accounts do not cross the cloud boundary.

How PTS helps

Making Teams work in China is a tenant-and-network design exercise, and it is one PTS runs as a standing service. From our Shanghai-registered entity, with Mandarin-speaking engineers, we provide managed IT for foreign businesses in Mainland China: designing the global-versus-21Vianet decision, provisioning either tenant, configuring cross-cloud communications so your offices actually meet, and delivering the licensed cross-border connectivity that lifts Teams call quality over the gateways. If you are an overseas head office supporting Mainland staff, we are IT for foreign companies operating in China and Hong Kong — your team on the ground.

If you need help or advice related to this topic please get in touch with us here.

PTS Consulting provides managed IT support, structured cabling, audiovisual design and installation, and IT consultancy services for businesses across Hong Kong, Mainland China and Singapore.