Microsoft 365 in China in 2026: Global vs 21Vianet Decision Guide

Who this is for Regional IT leaders, CIOs, Heads of Infrastructure and Compliance who support offices or staff in Mainland China.

The short version There are three viable approaches:

• Stay on your global Microsoft 365 tenant, optimise networking for China, and use Teams cross‑cloud communications to talk to colleagues and partners in China. Best when your Mainland footprint is small, or you need features that lag in China. Microsoft LearnTECHCOMMUNITY.MICROSOFT.COM
• Run a dedicated China tenant, “Microsoft 365 operated by 21Vianet,” for Mainland users, with cross‑cloud collaboration back to your global tenant via Microsoft Entra B2B. Best when you need data to stay in China or you have a sizeable China workforce. Microsoft Learn+1
• Move everything to the China tenant. Rare outside China‑only businesses. Expect feature differences, separate identity and distinct operational processes. Microsoft Learn

Why Microsoft 365 in China is different

• Different operator and legal scope. In Mainland China, Microsoft 365 is provided by 21Vianet from data centres in China. Microsoft licenses the technology; 21Vianet runs the service, billing and support. Services are subject to Chinese law. Microsoft Learn
• Separate cloud and endpoints. Identity and APIs live on China‑specific endpoints, for example login.partner.microsoftonline.cn and microsoftgraph.chinacloudapi.cn. Admin access uses portal.partner.microsoftonline.cn. Azure DocumentationMicrosoft LearnGitHub
• Different service domains. Examples include *.partner.outlook.cn for Exchange Online, *.sharepoint.cn for SharePoint and OneDrive, and teams.microsoftonline.cn for Teams. Plan your allow‑lists and proxies accordingly. Microsoft Learn
• Feature differences and lag. Microsoft documents clear differences for 21Vianet tenants. Teams in China limits third‑party apps and some developer capabilities. Several Purview features exist, but availability is narrower than global and evolves on a different cadence. Microsoft Learn+1
• Copilot note. Microsoft 365 Copilot is not offered on the 21Vianet service as of August 2026 — it remains a global-tenant capability. What that means for Mainland users, including the network caveats, is covered in its own section below. Microsoft Learn

Most of this lands on whoever runs the tenant day to day, which is why many foreign firms pair their global setup with managed IT services in China rather than stretching a headquarters team across the border.

Option 1: Stay on global, serve China users well

When to choose this

• Fewer than about 100 Mainland users, or mostly travellers.
• You depend on global‑only capabilities and partner integrations.
• You want one tenant to manage.

What to do

• Network first. Follow Microsoft’s China performance guidance. Many firms use private WAN or SD‑WAN to carry Microsoft 365 traffic to offshore breakouts, avoiding cross‑border congestion. Validate against local regulatory requirements. Microsoft Learn
• Teams interop. Enable cross‑cloud communications so Teams users in China tenants can chat, call and meet with your global users. Confirm external access settings in both tenants. TECHCOMMUNITY.MICROSOFT.COM
• SharePoint and OneDrive design. Keep heavy collaboration close to users. Avoid dependency on blocked consumer services. Plan caching and file sync carefully for China offices. Microsoft’s China URL set is essential for firewalls and QoS. Microsoft Learn
• Email hygiene. If you keep Exchange Online globally, watch outbound reputation to China domains and consider regional smart‑host routing if deliverability dips.

Pros

• One tenant to govern.
• Full global features and integrations.

Cons

• Performance and reliability depend on your network design.
• Some cross‑border scenarios remain sensitive to latency and policy.

Option 2: Dual‑tenant, with Microsoft 365 operated by 21Vianet for China

When to choose this

• Material headcount in China or strong data‑residency drivers.
• Mainland workflows benefit from local hosting and routing.

What to design

• Identity and access. Treat the China tenant as a separate Microsoft Entra directory. Use “Cross‑cloud B2B” to collaborate between your global and China tenants. Configure Microsoft cloud settings and cross‑tenant access both ways. Consider cross‑tenant sync for lifecycle management. Microsoft Learn+2Microsoft Learn+2
• Authentication endpoints. Update SSO, Conditional Access and device compliance to the China endpoints, for example login.partner.microsoftonline.cn. Azure Documentation
• Network and security. Allow‑list Microsoft 365 China URLs and IPs. Avoid tromboning China traffic out of the Mainland. Microsoft Learn
• Teams experience. Enable cross‑cloud communications with your global tenant. Plan around restrictions on third‑party apps and bots in the China Teams service. TECHCOMMUNITY.MICROSOFT.COMMicrosoft Learn
• Purview and records. Check which Purview capabilities you rely on and map the 21Vianet availability. A trimmed Microsoft Information Protection and Governance SKU is available in China with limited scope — verify current coverage against Microsoft’s availability tables. Microsoft Learn
• Intune and apps. Intune exists in the China cloud. Plan mobile app distribution without Google Play and prefer OEM or trusted local stores as per Microsoft notes. Microsoft Learn+1

Pros

• Local data hosting and routing for China users.
• Lower dependency on cross‑border links for day‑to‑day work.

Cons

• Two tenants to govern, license and support.
• Feature gaps, release lag and different admin surfaces.

Option 3: Move everything to the China tenant

When to consider

• You operate only in Mainland China or have a China‑first strategy.
• You accept the 21Vianet feature set and release cadence.

Key implications

• All identity, security and admin move to the China cloud.
• Contracts, SLAs and support are with 21Vianet. Microsoft Learn

Ten practical differences you must plan for

1. Operator, contracts and support provided by 21Vianet, not Microsoft. Microsoft Learn
2. Data residency within China for Microsoft 365 operated by 21Vianet. Microsoft Learn
3. Separate identity in a national cloud, with its own endpoints and app registrations. Azure Documentation
4. Admin portal is portal.partner.microsoftonline.cn for 21Vianet tenants. GitHub
5. Exchange Online domains change to *.partner.outlook.cn. Microsoft Learn
6. SharePoint and OneDrive use *.sharepoint.cn. Microsoft Learn
7. Teams features differ, with limits on third‑party apps and developer extensibility. Microsoft Learn
8. Teams cross‑cloud meetings and chats are supported between China and worldwide tenants with correct settings. TECHCOMMUNITY.MICROSOFT.COM
9. Purview and compliance features exist but with a narrower, evolving set in the China cloud. Microsoft Learn
10. Copilot availability. Microsoft 365 Copilot is not offered on the 21Vianet service as of August 2026. It needs a global-tenant licence and reliable connectivity to worldwide Microsoft 365 endpoints — plan around that, not around a China SKU that doesn’t exist. Microsoft Learn

Does Microsoft 365 Copilot work in China?

The short answer: not on the China service — but yes, with network caveats, for Mainland users on a global tenant.

As of August 2026, Microsoft 365 Copilot is not offered on Microsoft 365 operated by 21Vianet. The 21Vianet plan tables list no Copilot add-on, and Microsoft’s Copilot service description covers the Worldwide and US government clouds only — the China national cloud does not appear in its availability tables. If your Mainland users sit on a 21Vianet tenant, there is currently nothing to license. Microsoft Learn+1

On a global tenant, the licence works wherever the user happens to be; the constraint is connectivity. Copilot rides the worldwide Microsoft 365 endpoints and needs working WebSocket connections to *.cloud.microsoft and *.office.com — connections that break under TLS inspection and struggle on congested cross-border paths. Users on a well-designed offshore breakout generally get a usable experience; users on ordinary local internet often watch Copilot spin while the rest of Office limps along. Microsoft Learn

Two planning notes. Copilot prompts and responses are processed on the worldwide service, outside the Mainland, so include Copilot in your PIPL cross-border transfer mapping rather than treating it as a pure feature decision. And dual-tenant firms should expect a visible capability gap between global-tenant staff with Copilot and 21Vianet colleagues without it — better addressed in rollout communications than discovered through complaints.

Identity patterns that work

• Two directories, one company. Keep your global Entra tenant and add the China Entra tenant for 21Vianet.
• Cross‑cloud B2B. Enable Microsoft cloud settings, then set inbound and outbound access on both tenants. Use B2B direct connect for selected apps as needed. Microsoft Learn+1
• Endpoints and policies. Update Conditional Access to China endpoints and review MFA prompts accordingly. Azure Documentation

SharePoint, OneDrive and Teams design for China users

• Keep content close. For global tenants, minimise heavy co‑authoring across the border. Consider regional sites and content routing.
• DNS and proxies. Allow the full Microsoft 365 China URL and IP list, and avoid SSL inspection where Microsoft advises. Microsoft Learn
• Teams reality. Plan for the sovereign‑cloud feature set and remove reliance on third‑party apps in meetings. Microsoft Learn
• Cross‑tenant collaboration. Use cross‑cloud Teams settings to allow chat, meetings and calling with colleagues on the other tenant. TECHCOMMUNITY.MICROSOFT.COM

Email routing and hygiene options

• Global tenant retained. Keep Exchange Online globally and tune anti‑spam, transport rules and smart‑host paths for China mail flows.
• 21Vianet tenant. Use the China Exchange Online endpoints, for example *.partner.outlook.cn, and review EOP policies in that cloud. Microsoft Learn

Network patterns that actually help

• For global tenants. Many firms use private WAN or SD‑WAN to reach offshore Microsoft 365 breakouts, reducing cross‑border congestion. Validate local rules before deployment. Microsoft Learn
• For 21Vianet tenants. Break out locally in China to the documented Microsoft 365 China endpoints. Avoid sending China Microsoft 365 traffic out of the Mainland and back. Microsoft Learn

Windows Autopilot across Hong Kong and China

Windows Autopilot is a global-tenant capability. Microsoft’s own FAQ is blunt: Autopilot only supports customers on global Azure, and isn’t supported in any sovereign cloud — including Azure China operated by 21Vianet. Microsoft Learn

• Hong Kong. Hong Kong sits on the worldwide service, so Autopilot behaves exactly as it does in Singapore or London. No special design needed.
• Global tenant, device in the Mainland. There is no regional block — a laptop unboxed in Shanghai can enrol against your global tenant. But the whole out-of-box experience depends on reaching worldwide Entra ID, Intune and Autopilot endpoints across the border, and Microsoft warns of poor connectivity and high latency when deploying in China. In practice that means stalled enrolment status pages and app installs that time out. Microsoft Learn
• 21Vianet tenant. Classic Autopilot profiles aren’t supported with Intune operated by 21Vianet. The newer Windows Autopilot Device Preparation flow is available in the China cloud, giving 21Vianet tenants a supported — if slimmer — provisioning path. Microsoft Learn

Practical guidance: pre-provision Mainland-bound devices in Hong Kong before shipping, carry enrolment traffic over the same offshore breakout as your other Microsoft 365 traffic, and keep the enrolment-time app payload small for anything that must enrol in-country. Standing up a tenant and device estate from scratch? Our Microsoft 365 setup service covers Autopilot profile design.

Compliance and cross‑border data transfers

• Know the three legal channels. Under China’s PIPL and the cross-border rules, the main routes are:

  • CAC security assessment.
  • Certification by a recognised institution.
  • Standard Contract filing with the CAC. The 2024 Cross-Border Data Flow Provisions introduced targeted exemptions that can simplify some routine transfers. Work with counsel to pick the right mechanism. Clifford ChanceArnold & Porter

Roll‑out checklist and indicative sequence

1. Confirm approach, global only or dual‑tenant.
2. Map data flows and decide what must stay in China.
3. Design identity, including cross‑cloud B2B settings. Microsoft Learn
4. Build network plan and China allow‑lists. Microsoft Learn
5. Define Teams external access between clouds. TECHCOMMUNITY.MICROSOFT.COM
6. Validate Purview needs against China availability. Microsoft Learn
7. Pilot with one China office and one business unit.
8. Train admins on the China admin portal and endpoints. GitHubAzure Documentation
9. Finalise compliance records for cross‑border data. Clifford Chance

Budget items people miss

• Second tenant licences and support overhead in dual‑tenant designs.
• Network changes for China connectivity and monitoring.
• Third‑party tools for content migration if you move any workloads between tenants. Microsoft Learn
• Change management for different Teams and Purview capabilities. Microsoft Learn+1

FAQs

Is Microsoft 365 Copilot available in the China cloud?

No. As of August 2026, Microsoft 365 Copilot is not offered on Microsoft 365 operated by 21Vianet: the China plan tables list no Copilot add-on, and Microsoft’s Copilot service description covers the Worldwide and US government clouds only. Mainland users need a licence on a global tenant plus a network path that reliably reaches worldwide Microsoft 365 endpoints. Microsoft Learn

Can we use Windows Autopilot with a 21Vianet tenant?

Classic Autopilot profiles, no — Windows Autopilot only supports global Azure tenants and isn’t available in any sovereign cloud, including Azure China 21Vianet. The newer Windows Autopilot Device Preparation flow is supported on Intune operated by 21Vianet. Devices enrolling against a global tenant face no regional block wherever they are unboxed, but Mainland deployments contend with cross-border latency during the out-of-box experience. Microsoft Learn

Can staff in China meet with overseas colleagues on Teams?

Yes. Cross‑cloud communications support chat, calls and meetings between 21Vianet and worldwide Teams tenants when external access is configured in both. TECHCOMMUNITY.MICROSOFT.COM

Can we collaborate across the global and China tenants with one identity per user?

You will run two Entra tenants. Use cross‑cloud B2B to grant access between them and optionally use cross‑tenant sync to automate lifecycle. Microsoft Learn+1

What are the key China login and service URLs we must allow?

Examples include login.partner.microsoftonline.cn, microsoftgraph.chinacloudapi.cn, *.partner.outlook.cn, *.sharepoint.cn, teams.microsoftonline.cn. Use Microsoft’s published list for the full set and IPs. Microsoft LearnAzure Documentation

If we ever move workloads between tenants, is it supported?

Microsoft provides cross‑tenant migration patterns and many organisations use partners and tools. Plan carefully, especially across clouds. Microsoft Learn

What good looks like

• A written decision that states which users and data live in which cloud, and why.
• Firewall and proxy rules that match Microsoft’s China endpoint list. Microsoft Learn
• Cross‑cloud Teams external access tested both ways. TECHCOMMUNITY.MICROSOFT.COM
• Compliance paperwork that cites your chosen PIPL transfer mechanism for any cross‑border flows. Clifford Chance

Ready to act?

PTS designs, delivers and supports both models, and runs the ongoing tenant administration, migrations and backup as part of our cloud managed services in Hong Kong. Typical next steps:

• An architecture review to validate global‑only versus dual‑tenant.
• A China network and Teams interop test plan for one pilot office.
• A compliance work‑through on data flows and documentation.

Related guides: Does Microsoft Teams work in China? — the Teams-specific companion on performance and the global‑vs‑21Vianet choice — plus the Microsoft Teams Migration Checklist and Azure cloud migration for Hong Kong businesses. For the broader China context, see our IT services in China page and our overview of IT for foreign companies in China & Hong Kong. Standing up a new tenant? See Microsoft 365 setup for new businesses.