Deploying Microsoft Teams Telephony in China: What You Must Know Before You Start

Why China Is Different

I have deployed Microsoft Teams voice solutions across 40+ countries. China is in a category of its own. It is not just about configuring SBCs and dial plans. The regulatory, technical, and political landscape creates challenges that can derail a project if you are not prepared.

If your global IT team says "we will just extend our Teams Phone deployment to the China offices," stop them immediately. Here is why.

The 21Vianet Reality

Microsoft does not operate its own cloud services in China. Instead, 21Vianet, a local Chinese data center operator, runs a separate instance of Microsoft 365 under license from Microsoft. This is not a regional deployment of the global Microsoft cloud. It is a completely separate environment.

What This Means for Your Deployment

The critical point: you need a separate tenant for China. Your global M365 tenant and your China 21Vianet tenant are completely isolated. Users in China cannot be part of your global tenant if you need to comply with data residency requirements.

Regulatory Framework

MIIT (Ministry of Industry and Information Technology)

China's MIIT governs all telecommunications activities. Key regulations that impact Teams Phone deployment:

All VoIP services that connect to the PSTN must go through licensed Chinese telecom carriers (China Telecom, China Unicom, China Mobile)

Data must remain in China — call detail records, recordings, and user data cannot be stored outside mainland China

International calls must transit through approved international gateways operated by the licensed carriers

Foreign companies cannot directly operate telecom services in China — you must work with a local licensed operator

Cybersecurity Law and PIPL

China's Cybersecurity Law (2017) and Personal Information Protection Law (PIPL, 2021) impose strict requirements:

Personal data of Chinese citizens must be stored in China

Cross-border data transfers require security assessments

Network operators must cooperate with Chinese authorities for security monitoring

Encryption standards must comply with Chinese national standards

What This Means Practically

You cannot deploy a global SBC that sits in Singapore and route China calls through it. The SBC must be physically located in China, connected to a Chinese licensed carrier's SIP trunk, and managed in a way that keeps all call data within China.

Recommended Architecture

Option 1: Direct Routing with Local SBC (Recommended)

This is the approach I recommend for most enterprises:

Deploy an SBC in a Chinese datacenter (your own or a colocation facility)

Connect the SBC to a licensed Chinese carrier (China Telecom, China Unicom, or China Mobile) via SIP trunk

Configure the SBC to peer with Microsoft Teams via Direct Routing

Route all China PSTN calls through the local SBC

SBC Options:

AudioCodes Mediant (virtual or hardware) deployed in Chinese datacenter

Oracle SBC deployed locally

Ribbon SBC deployed locally

Key Design Decisions:

The SBC needs public IP and FQDN reachable by Microsoft's SIP proxies

TLS certificates from a publicly trusted CA (not a Chinese government CA)

DNS resolution must work from both inside and outside China

Option 2: Operator Connect

Some operators are beginning to offer Teams Phone connectivity in China, but the availability is very limited. Check with Microsoft and local operators for the latest status.

The Great Firewall Challenge

This is where many projects fail. China's Great Firewall can cause:

Packet loss and jitter on SIP signaling and media traffic crossing the border

DNS resolution failures for Microsoft service endpoints

TLS handshake timeouts due to deep packet inspection

Inconsistent call quality depending on time of day and network load

Mitigation Strategies

Azure ExpressRoute or dedicated MPLS from your China offices to the nearest Microsoft peering point (Hong Kong is common)

SD-WAN with China-aware routing that can optimize the path for Teams traffic

Local media termination — ensure media stays within China for domestic calls (the SBC handles this naturally for PSTN calls, but peer-to-peer Teams calls may still traverse the firewall)

Split DNS that resolves Microsoft endpoints to the nearest available relay

Dual-Tenant Strategy

For most multinational organizations, the recommended approach is:

Global Tenant — for all users outside China

21Vianet Tenant — for users in China

This creates administrative overhead because you manage two separate environments. User accounts, policies, phone numbers, and configurations are maintained separately. Cross-tenant calling between your global users and China users requires additional planning.

Cross-Tenant Communication

Teams users on the global tenant and the 21Vianet tenant can communicate via:

External access (federation) — allows chat and calls between tenants

PSTN — users can always call each other via phone numbers

Guest access — limited collaboration scenarios

Cost Considerations

Budget 20 to 30 percent more than you would for an equivalent deployment in other countries.

Common Mistakes I Have Seen

Assuming the global tenant works in China — it does not comply with data residency laws

Deploying the SBC outside China — this violates MIIT regulations and also creates quality issues

Ignoring the Great Firewall — "it works from our Shanghai office" during testing does not mean it will work reliably at scale

Not engaging local legal counsel — telecom regulations in China change frequently and the penalties for non-compliance are severe

Underestimating timeline — getting SIP trunks from Chinese carriers can take 4 to 8 weeks with significant paperwork

My Recommendation

Deploy Teams Phone in China only if you have:

A clear business justification (consolidating on one global platform)

Budget for a dedicated China infrastructure (SBC, network, 21Vianet licenses)

Local IT support or a managed service partner in China

Legal review of current MIIT and PIPL requirements

Realistic timeline expectations (plan for 3 to 6 months)

If your China office has fewer than 50 users, evaluate whether a local Chinese PBX solution is simpler and more cost-effective than the overhead of a Teams Phone deployment in China.

---

Need dial plans and voice routing policies for your global Teams Phone deployment? SwiftM365 covers 203 countries including China-specific configurations.