Does SharePoint Work in China? The 21Vianet Sovereign-Cloud Tenant, Document Data Residency & Cross-Border
SharePoint Online is available in mainland China — but through a separate, isolated sovereign cloud, SharePoint delivered within Microsoft 365 operated by 21Vianet (世纪互联), with its own *.sharepoint.cn endpoints and its own sign-up, not the global service on *.sharepoint.com. The real decision for a China-facing SharePoint deployment isn't speed — it's document data residency: a SharePoint site is where business documents live (contracts, HR and customer files), routinely personal and sometimes important information, so running your global tenant from the mainland keeps that content on Microsoft's commercial cloud outside China, a PIPL cross-border transfer, while the data-resident lawful path is the 21Vianet-operated China tenant. A compliance-first look at the two clouds, the cross-border-data question, CSL Article 39 (formerly Article 37) residency, and the lawful in-country path.
Does SharePoint work in China?
Yes — SharePoint Online is available in mainland China, but through a separate, isolated sovereign cloud: SharePoint delivered within "Microsoft 365 operated by 21Vianet" (世纪互联), not the global service you reach on *.sharepoint.com. Microsoft documents this China instance as specific to China, operated by 21Vianet, with data kept within the mainland and its own endpoints on *.sharepoint.cn (team sites at name.sharepoint.cn).
Because a lawful in-country option exists, the real decision is document data residency, not speed. A SharePoint site is where business documents live — contracts, HR and customer records, finance workbooks, the intranet itself — much of it personal information, sometimes important data, under Chinese law. Run that on the global tenant from the mainland and the content sits on Microsoft's commercial cloud outside China, a PIPL cross-border transfer (and, for a CII operator, a residency problem under Cybersecurity Law Article 39 (formerly Article 37)); larger or sensitive transfers can add a CAC data-export security assessment. The data-resident path is the 21Vianet-operated China tenant — subject to availability and feature parity, which you confirm with Microsoft and 21Vianet.
21YunBox maps the tenant choice, localizes your content onto the data-resident China path, and delivers the China-facing portal or intranet that surfaces your sites in-country on ICP-filed infrastructure — so it runs legally in the mainland. Treat the specifics as a risk to confirm with counsel.
What Microsoft SharePoint's own documentation says about China
| Fact | Primary source |
|---|---|
| SharePoint Online runs in China through Microsoft 365 operated by 21Vianet. Microsoft's service description states the service “is specific to China,” that “Microsoft does not operate the service itself,” and that 21Vianet operates “local Microsoft 365 data centers to provide the ability to use Microsoft 365 services while keeping data within China.” SharePoint Online is listed among the services included in each plan. | Microsoft — Microsoft 365 operated by 21Vianet, Service Descriptions (learn.microsoft.com), updated 2026-06-15, retrieved 2026-10-08 |
| The China cloud has its own SharePoint endpoints, separate from global SharePoint. Microsoft's endpoint list for Microsoft 365 operated by 21Vianet puts SharePoint Online and OneDrive for Business on the wildcard *.sharepoint.cn, with team sites addressed as name.sharepoint.cn — distinct from the global *.sharepoint.com service. | Microsoft — URLs and IP address ranges for Microsoft 365 operated by 21Vianet (learn.microsoft.com), last updated 2026-07-31, retrieved 2026-10-08 |
| Using the global tenant for China documents is a cross-border transfer. Sending a Chinese user's or business's personal information held in SharePoint to a tenant hosted outside the mainland triggers PIPL Chapter III (Articles 38–43): notice, a separate consent, and one transfer mechanism — a CAC security assessment, the CAC standard contract, or certification — with in-country storage under Article 40 (and Cybersecurity Law Article 39 (formerly Article 37)) for CII operators. | Personal Information Protection Law of the PRC, Chapter III, Articles 38–43 (cac.gov.cn), retrieved 2026-10-08 |
| Microsoft states the 21Vianet service is subject to Chinese law. The same service description carries the note “These services are subject to Chinese laws,” and flags that some features “have not yet been enabled” and reach parity over time — so availability and feature parity in the China cloud are something to confirm before you build, not assume. | Microsoft — Microsoft 365 operated by 21Vianet, Service Descriptions (learn.microsoft.com), updated 2026-06-15, retrieved 2026-10-08 |
Sources verified by the 21YunBox compliance team on 2026-10-08.
For a mainland-China audience, the first thing to settle about SharePoint is not how fast a document library loads — it is which SharePoint you mean. Microsoft runs two separate SharePoint Online services that matter here: the global commercial SharePoint most teams reach on *.sharepoint.com, and a distinct, isolated China instance — SharePoint Online delivered through Microsoft 365 operated by 21Vianet (世纪互联) — with its own endpoints on *.sharepoint.cn, its own sign-up, and data kept inside the mainland. So the honest answer to “does SharePoint work in China?” is yes — but through a specific tenant, on a specific footing.
Because a lawful in-country option already exists, the decision moves off the speed axis and onto a document-residency one. A SharePoint site is where an organization’s documents live — contracts, HR files, customer records, finance workbooks, the intranet itself — and much of that is personal information, sometimes important data, under Chinese law. Keep it on the global tenant and the content rests on Microsoft’s commercial cloud outside the mainland, which is a cross-border transfer under PIPL; keep it on the 21Vianet-operated China tenant and the documents stay in-country. Which tenant you choose, and how you deliver the portal or intranet that surfaces those sites, is the compliance question — not the render time.
Microsoft SharePoint in China at a glance
| What decides it | In Microsoft's own terms — and China's law |
|---|---|
| What it is | Microsoft SharePoint — SharePoint Online sites, document libraries, lists, and intranet/portal content (plus on-premises SharePoint Server). Two clouds matter for China: the global commercial service on *.sharepoint.com, and a distinct China instance — SharePoint Online delivered within Microsoft 365 operated by 21Vianet (世纪互联), run inside the mainland. |
| Is it available in the mainland? | Yes — through the separate, isolated China cloud. Microsoft delivers SharePoint Online as part of Microsoft 365 operated by 21Vianet, with team sites at name.sharepoint.cn and endpoints on *.sharepoint.cn, operated by 21Vianet. The global *.sharepoint.com service is a different tenant and is not connected to it. (Microsoft is retiring the standalone SharePoint Online Plan 1 and Plan 2; SharePoint Online continues within the Microsoft 365 and Office 365 suites.) |
| Where the data lives | On the 21Vianet-operated China cloud, Microsoft states data is kept within China. On the global commercial service, your sites and document libraries — files, contracts, HR and customer records, often personal information — rest on Microsoft's cloud outside the mainland, which is the cross-border question for China users and China documents. |
| Cross-border & residency | Pushing China personal information held in SharePoint to the global tenant is a cross-border transfer under PIPL (Articles 38–43: notice, a separate consent, one transfer mechanism). For a critical information infrastructure operator, in-country storage is required under PIPL Article 40 and Cybersecurity Law Article 39 (formerly Article 37); larger-volume or sensitive transfers can add a CAC data-export security assessment. |
| The lawful path | Stand up on the 21Vianet-operated China tenant (or otherwise keep the documents in-country), and deliver the China-facing portal or intranet that surfaces the sites on ICP-filed, in-country infrastructure. 21YunBox maps the tenant choice, localizes your content onto the data-resident path, and delivers it in-country — subject to the China cloud's availability and feature parity, which you confirm with Microsoft and 21Vianet. |
Availability: a distinct China cloud, operated by 21Vianet
SharePoint’s presence in the mainland is set in Microsoft’s own documentation, not by a load-time test. Microsoft’s service description states that the Microsoft 365 operated by 21Vianet version “is specific to China,” that “Microsoft does not operate the service itself,” and that 21Vianet “operates local Microsoft 365 data centers to provide the ability to use Microsoft 365 services while keeping data within China” — with SharePoint Online listed among the services in each plan. Microsoft’s endpoint list for that service puts SharePoint Online and OneDrive for Business on the wildcard *.sharepoint.cn, and the team-site address is name.sharepoint.cn. This is a sovereign cloud, operated inside the mainland by a licensed local operator, with data kept in-country.
Two things follow. First, the China cloud is a separate tenant: it has its own sign-up and is not linked to a global SharePoint tenant, so “turning on China” is a deployment decision, not a toggle. Second, availability and feature parity between the China cloud and the global service can differ and can change — Microsoft notes some features “have not yet been enabled” and reach parity over time, and it is retiring the standalone SharePoint Online Plan 1 and Plan 2 (while SharePoint Online continues within the Microsoft 365 and Office 365 suites). Which capabilities, connectors, and limits apply inside the China cloud is something you confirm directly with Microsoft and 21Vianet before you build. For that reason this page publishes no first-party China latency figure for SharePoint: a lawful in-country cloud already exists, so speed is not the axis the decision turns on.
The cross-border-data story: your SharePoint sites are full of personal information
The gate that actually decides a China SharePoint deployment is the data. A SharePoint library is rarely just a set of files — it carries the documents a business runs on: employment contracts and HR records, ID and onboarding scans, customer agreements, supplier and finance workbooks, the internal knowledge base. Served to a user in China from the global tenant, that content rests on Microsoft’s commercial cloud outside the mainland, and moving it there is a cross-border transfer of personal information under China’s Personal Information Protection Law. PIPL puts the duty on the handler — you, not Microsoft: Chapter III (Articles 38–43) requires notice, a separate consent distinct from the user’s agreement to use the portal, and one transfer mechanism — a CAC security assessment, the CAC standard contract, or certification.
Underneath that sits residency. A critical information infrastructure operator or a large-volume handler must store personal information collected in China inside the mainland (PIPL Article 40, with Cybersecurity Law Article 39 (formerly Article 37)) — a duty the global, offshore tenant structurally cannot meet. And because SharePoint can hold not only personal information but important data, where volumes or data sensitivity cross the thresholds the transfer itself needs a CAC data-export security assessment before it may proceed. How heavy each of these is scales with your documents, your volumes, and your role, which is why it belongs with counsel rather than a default assumption — a risk to confirm against what you actually store.
The data-resident path: the 21Vianet-operated China tenant
The lawful, in-country footing is the one Microsoft already documents: SharePoint Online within the 21Vianet-operated China cloud, which keeps content inside the mainland. On that path the cross-border question does not arise in the same way, because the documents do not leave. The work is to plan the deployment onto it — the China cloud is a separate tenant, so sites, document libraries, sharing, and identity are stood up there rather than flipped over from a global tenant by a switch — and to confirm, up front, that the SharePoint capabilities your teams depend on are available in the China cloud. That availability-and-parity check is not a formality; it is the step that tells you whether the data-resident path carries your use case as-is or needs adjustment.
The lawful path — map, localize, deliver
There is a lawful way to run SharePoint for Chinese users, and it has a clear shape: the documents stay in-country on the 21Vianet-operated China tenant, and the China-facing portal or intranet that surfaces those sites is itself delivered compliantly inside the mainland. That second half is easy to overlook. An intranet, extranet, or customer portal that surfaces SharePoint is a public-facing service in China, so it carries an ICP filing (备案) duty and needs compliant in-country delivery like any other China property — a site that opens quickly but hangs off an unfiled, offshore front end has solved only half the problem.
That is the footing 21YunBox owns, and it is more than advice. Our China team works in three moves. We map the tenant choice and your PIPL, residency, and ICP exposure, so you know which SharePoint you should be running and what each option obliges. We localize your content onto the data-resident path — standing up and integrating the 21Vianet-operated China tenant, or otherwise keeping the documents in-country, in place of a global tenant that cannot meet the residency duty. And we deliver the China-facing portal or intranet that surfaces your sites in-country on ICP-filed infrastructure — the 21YunBox Optimizer — sitting in front of what you already run, with no rebuild and no re-platform. The result is a SharePoint deployment that runs legally and compliantly for your users in China. What we do not do is route anyone around anyone’s terms or any network control: this is a lawful in-country deployment on the China cloud Microsoft and 21Vianet already provide, and it never uses or suggests circumvention of any kind.
Related reading:
- Cross-border data transfers under PIPL
- China’s Cybersecurity Law — Article 39 (formerly Article 37) and data localization
- China’s data-export security assessment measures
=========================
