Does SAP Cloud Platform (SAP BTP) work in China?
Yes — SAP Cloud Platform (now SAP Business Technology Platform) runs inside mainland China, but only as a separate China (Shanghai) region reached through a dedicated China entry point. Your global BTP account does not reach into it, and a global region keeps your China data offshore.
SAP documents both paths in its own help portal. Its regions “are provided either by SAP or by our Infrastructure-as-a-Service (IaaS) partners Amazon Web Services (AWS), Microsoft Azure, Google Cloud, and Alibaba Cloud,” and “each region represents a geographical location (for example, Europe, US East) where applications, data, or services are hosted” — so where you run BTP is where your data sits. BTP's mainland presence, the China (Shanghai) region (cf-cn40), runs on Alibaba Cloud, and SAP states that “Users accessing SAP BTP cockpit from China must use a dedicated regional entry point” at cockpit.cn40.platform.sapcloud.cn, activated through a separate China operator — distinct from the global cockpit and the offshore hana.ondemand.com regions. Keep serving China from a global region instead and your users' personal data stays offshore: a cross-border transfer PIPL governs, on infrastructure that can't be ICP-filed. The table below sets SAP's own wording against the rule each path triggers.
This is a risk map, not a verdict — which path fits depends on your entity, your data and who your users are. Our China team can map your exposure and the filing path with you →
Compliance snapshot
- ✓ SAP BTP does run in-country — a separate China (Shanghai) region on Alibaba Cloud, reached through a dedicated China entry point
- ! On a global BTP region (AWS, Azure or Google Cloud), your mainland-China users' data sits offshore
- ! Serving China from a global region is a cross-border transfer of personal data — PIPL applies
- ✕ A global, offshore region is outside the mainland, so it can't be ICP-filed for a public site
- ✓ Or keep your global BTP origin and add ICP-filed, in-country delivery in front of it — no rebuild
What actually decides whether SAP BTP works for you in mainland China
| Fact | Primary source |
|---|---|
SAP BTP runs on global hyperscaler regions and, inside mainland China, on a separate Alibaba Cloud region. SAP's own documentation states its regions “are provided either by SAP or by our Infrastructure-as-a-Service (IaaS) partners Amazon Web Services (AWS), Microsoft Azure, Google Cloud, and Alibaba Cloud,” and that “each region represents a geographical location (for example, Europe, US East) where applications, data, or services are hosted.” BTP's in-country presence — the China (Shanghai) region (technical key cf-cn40) on Alibaba Cloud — runs on a separate China domain, cn40.platform.sapcloud.cn, while its global regions sit offshore on the hana.ondemand.com domains outside mainland China. | SAP Help Portal — Regions, and Regions and API Endpoints Available for the Cloud Foundry Environment (SAP BTP), retrieved 2026-10-07 |
The China region is a dedicated entry point, not a switch inside your global account. SAP instructs that “Users accessing SAP BTP cockpit from China must use a dedicated regional entry point”, at https://cockpit.cn40.platform.sapcloud.cn, and that you “will receive an email from ias-notification@sapcloudplatform.cndatacom.com to activate your user before logging in” — the mainland region is run with a local China operator on a .cn domain, apart from the global cockpit at cockpit.btp.cloud.sap. Being on global SAP BTP does not, by itself, carry into the mainland. | SAP Help Portal — Access the Cockpit (SAP BTP), retrieved 2026-10-07 |
| A public site hosted from the China (Shanghai) region needs an ICP filing, and that binds to a mainland entity. Any site served to the public from infrastructure physically inside mainland China must hold an ICP filing (备案) tied to a licensed in-country host and a mainland legal entity (State Council Order No. 292, Article 4; MIIT Order No. 33). Running SAP BTP in the in-country region is what puts your data on Chinese soil — and it is also what turns on the ICP door and the China entity the filing binds to. | State Council Order No. 292 (Measures for the Administration of Internet Information Services), Article 4; MIIT Order No. 33 |
| On a global BTP region, your China users' data stays offshore. A global region (AWS, Azure or Google Cloud) sits outside mainland China, so serving a China audience from it carries their personal information across the border — a cross-border transfer under PIPL (notice, separate consent, and one transfer mechanism — a CAC security assessment, the CAC standard contract, or certification; Articles 38–43). For a CIIO or large-volume handler, personal information collected in China must be stored in the mainland (PIPL Article 40; Cybersecurity Law Article 39 (formerly Article 37)) — which an offshore region cannot do, and an offshore region cannot be ICP-filed. | PIPL Chapter III, Articles 38–43 and Article 40; Cybersecurity Law Article 39 (formerly Article 37) |
Sources verified by the 21YunBox compliance team on 2026-10-07.
SAP Cloud Platform — renamed SAP Business Technology Platform (SAP BTP) in 2021 — is SAP’s platform-as-a-service for building and extending applications, and whether it “works” in China is a data-residency and licensing question before it is a performance one. BTP does run inside mainland China, but not as a region of the global account most teams already hold: it runs there as a separate China (Shanghai) region on Alibaba Cloud, reached through a dedicated China entry point. Meanwhile a global BTP region that serves China keeps your users’ data offshore. Those are the two paths.
Below is what SAP’s own documentation says about where BTP regions run and how the China region is reached, the ICP filing a public mainland site turns on, and how China’s Personal Information Protection Law treats the data a global region holds offshore — SAP’s own words and China’s own law, so you can take the question to counsel, not to a stopwatch.
SAP BTP in China at a glance
| What decides it | In SAP's own words — and China's own law |
|---|---|
| What SAP Cloud Platform is | SAP Cloud Platform was renamed SAP Business Technology Platform (BTP) in 2021 — the same platform-as-a-service. It is region-based: you deploy each subaccount into one region, and “each region represents a geographical location (for example, Europe, US East) where applications, data, or services are hosted.” The region you pick is where your data lives. |
| Where it runs | BTP regions are “provided either by SAP or by our Infrastructure-as-a-Service (IaaS) partners Amazon Web Services (AWS), Microsoft Azure, Google Cloud, and Alibaba Cloud.” BTP's mainland presence is the China (Shanghai) region (cf-cn40) on Alibaba Cloud, on a separate .cn domain; its global regions sit offshore on hana.ondemand.com. |
| Reaching the China region | A separate entry point, not a switch inside your global account: “Users accessing SAP BTP cockpit from China must use a dedicated regional entry point”, at cockpit.cn40.platform.sapcloud.cn, run with a local China operator — apart from the global cockpit at cockpit.btp.cloud.sap. |
| Serving the public in China | A public site hosted from the China (Shanghai) region needs an ICP filing (备案) tied to a licensed in-country host and a mainland legal entity (State Council Order No. 292, Article 4; MIIT Order No. 33). |
| Your data on a global region | Served from a global BTP region, your China users' personal information sits outside the mainland — a cross-border transfer PIPL governs, on infrastructure that cannot be ICP-filed. |
| The working design | Keep your BTP origin — global region or China (Shanghai) — and add ICP-filed, in-country delivery in front of it for mainland visitors; where the law requires it, run the workload and its data inside the mainland. An overlay, not a re-platform. |
What SAP Cloud Platform (now SAP BTP) actually is
SAP Cloud Platform was rebranded SAP Business Technology Platform in 2021; the platform-as-a-service is the same product line, and the “does it work in China” question is the same. BTP is region-based: you deploy each subaccount into exactly one region, and in SAP’s own words “each region represents a geographical location (for example, Europe, US East) where applications, data, or services are hosted.” So the region you choose is where your data sits — which is why the China answer turns on which region, not on whether BTP is “blocked.” SAP’s regions are “provided either by SAP or by our Infrastructure-as-a-Service (IaaS) partners Amazon Web Services (AWS), Microsoft Azure, Google Cloud, and Alibaba Cloud,” and its in-country region — China (Shanghai) — runs on Alibaba Cloud.
Path one — SAP BTP’s China (Shanghai) region is reached separately
BTP does run inside mainland China, as the China (Shanghai) region (technical key cf-cn40) on Alibaba Cloud. But it is not a region you switch on inside the global account you already have. SAP’s own cockpit documentation is explicit: “Users accessing SAP BTP cockpit from China must use a dedicated regional entry point”, at cockpit.cn40.platform.sapcloud.cn, where “You will receive an email from ias-notification@sapcloudplatform.cndatacom.com to activate your user before logging in” — a China operator on a .cn domain, separate from the global cockpit at cockpit.btp.cloud.sap and the offshore hana.ondemand.com regions.
Hosting a public-facing site from inside the mainland then turns on a permission that has nothing to do with BTP’s code: an ICP filing (备案). Under State Council Order No. 292 (Article 4) and MIIT Order No. 33, that filing attaches to a hosting resource physically inside the mainland and to a mainland legal entity. Running BTP in the China (Shanghai) region is what puts your data on Chinese soil — and it is also what turns on the ICP door and the China entity the filing binds to. “We’re already on SAP BTP” does not, by itself, carry into China.
Path two — a global BTP region keeps your China data offshore
Keep serving China from a global BTP region instead — on AWS, Azure or Google Cloud — and two facts follow. First, that region sits outside mainland China, so there is nothing in-country to attach an ICP filing to; an offshore endpoint cannot be filed. Second, your users’ personal information lives in whichever offshore region you chose. Under China’s Personal Information Protection Law that is a cross-border transfer: the handler — you, not SAP — must give notice, obtain separate consent, and satisfy one transfer mechanism (a CAC security assessment, the CAC standard contract, or certification; Articles 38–43). The weight scales with volume and role rather than with using BTP at all: a CIIO or large-volume handler must keep personal information collected in China inside the mainland (PIPL Article 40; Cybersecurity Law Article 39 (formerly Article 37)), which an offshore region cannot do.
This is a risk map, not a verdict — which path fits depends on your entity, your data and who your users are, and the specifics belong with counsel.
Where 21YunBox fits — a compliant overlay, not a migration
You keep building on SAP BTP — a global region or the China (Shanghai) region. We add the piece BTP leaves you to arrange yourself: compliant, ICP-filed delivery from inside the mainland, placed in front of your existing BTP origin, with a fixed in-country entry so each visitor’s real IP is not carried across the border — no rebuild, no second codebase, and no forced move between regions. Our China team maps which path fits, assesses your PIPL cross-border and data-residency exposure for your entity and data volumes, and stands up the in-country delivery and storage a compliant China presence requires — and, where the law requires your users’ data to stay on Chinese soil, helps you run the workload inside the mainland.
Related reading:
Frequently Asked Questions
Does our existing global SAP BTP account work in China?
No. SAP BTP's mainland-China region, China (Shanghai) (cf-cn40), is a dedicated entry point: SAP states that “Users accessing SAP BTP cockpit from China must use a dedicated regional entry point” at cockpit.cn40.platform.sapcloud.cn, run with a local China operator on a .cn domain — not a region you can switch on inside the global account you already have. Your global subaccounts stay on the offshore hana.ondemand.com regions. Reaching the mainland means either the China region (data in China, plus an ICP filing and a China entity for a public site) or keeping your global origin and adding ICP-filed, in-country delivery in front of it.
Is it a problem to serve mainland China from a global SAP BTP region?
Treat it as a risk to assess with counsel, not a blanket yes/no. Two things follow from serving China from a global, offshore region: your users' personal information leaves the mainland, which PIPL governs as a cross-border transfer (notice, separate consent and a transfer mechanism), and a region outside mainland China cannot hold an ICP filing, which PRC law requires for a public website. Whether a data-localization duty also applies turns on your role — for example, a critical information infrastructure operator — and your data volumes.
Can 21YunBox help make our SAP BTP setup work in China?
Yes. Our China team can map which path fits — assessing your PIPL cross-border and data-residency exposure for your entity, data volumes and users — and stand up the ICP-filed, in-country delivery a compliant China presence requires, in front of the SAP BTP stack you already run, whether that is a global region or the China (Shanghai) region. Get in touch to work through your specific case.
