Does Progress Sitefinity Work in China? ICP, Azure-Native Hosting & Data Residency
Progress Sitefinity Cloud is Azure-native on the global Microsoft Azure Marketplace, with no mainland-China region — so a China-facing Sitefinity site is served offshore, with no ICP-filing path the product provides and your users' personal data landing outside the mainland under PIPL. A compliance-first look at the two doors.
Does Sitefinity work in China?
Whether you can run Progress Sitefinity for mainland-China visitors is first an ICP-licensing and in-country-hosting question, not a speed one. Sitefinity isn't blocked — but reachability was never the part that decides it.
Sitefinity is software you host, and Progress's managed option, Sitefinity Cloud, is in its own words an "Azure-native" platform sold through the Microsoft Azure Marketplace and certified for GDPR and HIPAA — Western data regimes, not China's. Microsoft's mainland-China Azure is a physically separate partition operated by 21Vianet, on a different contract and marketplace, and Progress names no mainland region. So serving Sitefinity from inside China means standing up a China host the product doesn't provide — the step that pulls you into an ICP filing — and any personal data your forms, lead capture or personalization collect raises a separate cross-border-PI question under PIPL. The table below is Progress's and Microsoft's own wording and the rules it triggers.
This is a risk picture, not a verdict — your obligations turn on where you host and what personal data you collect. Our China team can scope the ICP path and your data exposure with you →
What Sitefinity's documentation says, and what we measured from inside China
| Fact | Primary source |
|---|---|
| In Progress's own words, Sitefinity Cloud is an "Azure-native architecture" with a "global CDN," which you "purchase ... via Microsoft Azure Marketplace," and it is "Certified for ISO 27001, SOC 2, GDPR, HIPAA." Its published architecture lists global Azure regions only — no mainland-China region, and none of its certifications is a Chinese data-protection regime (no PIPL, no MLPS). | Progress — Sitefinity Cloud product page, retrieved 2026-10-07 |
| "Azure-native" does not mean inside China. By Microsoft's own documentation, "Microsoft Azure operated by 21Vianet (Azure in China) is a physically separated instance of cloud services located in China" that is "independently operated and transacted by" 21Vianet, under a separate contract and a separate "Azure in China" Marketplace from the global Azure that Sitefinity Cloud is sold through. Inference (Progress publishes no 21Vianet or mainland deployment on this page — confirm current regions with Progress): a standard Sitefinity Cloud tenant therefore sits outside mainland China. | Microsoft Learn — Microsoft Azure in China (operated by 21Vianet), updated 2023-12-12; retrieved 2026-10-07 |
| Because no in-country region ships with the product, serving a public Sitefinity site to mainland visitors means standing up a host inside China yourself — and a public-facing site on mainland infrastructure must carry an ICP filing (MIIT Order No. 33; State Council Order No. 292) before a China network or CDN will route its traffic. The filing attaches to the mainland host you serve from, not to Sitefinity itself. | MIIT — Administrative Measures on Filing of Non-operational Internet Information Services (Order No. 33); State Council Order No. 292 |
| Reachability is not the gate: Progress's own Sitefinity site completed all 3 page loads from a probe inside mainland China (Alibaba Cloud cn-zhangjiakou) on 2026-08-28, with a median time to first byte of 618ms and a median largest-contentful-paint of 2,192ms. A vendor's marketing site loading, though, is not the same as a Sitefinity-built site serving your visitors. | 21YunBox — China delivery measurement, measured from inside mainland China |
| Measured again from a Beijing residential broadband line on 2026-08-30, the same page completed 0 of 3 loads within a 60-second ceiling — first byte still returned in a median 911ms, so this is border latency and offshore-asset loss, not a block: about half the page's resources hung, all of them offshore hosts (three Amazon CloudFront distributions and cdn.insight.sitefinity.com). The datacenter result does not describe what a consumer connection sees. | 21YunBox — paired measurement from a Beijing residential broadband line |
Sources verified by the 21YunBox compliance team on 2026-10-07.
For a mainland-China audience, the first question about Progress Sitefinity is not how quickly it paints — it is whether you are licensed to serve it from inside China and where your users’ data is allowed to live. Sitefinity is a CMS you host, and Progress’s managed option, Sitefinity Cloud, is in its own words an “Azure-native” platform sold on the global Microsoft Azure Marketplace — never on the separate, 21Vianet-operated Azure partition that exists inside the mainland. Progress names no mainland-China region. So a China-facing Sitefinity site is reachable but served offshore, which leaves it with no footing for the ICP filing a public mainland site requires, and turns the personal data your forms and personalization collect into a cross-border transfer China’s law governs. The reachability is real; the licensing and the data residency are the exposure.
Sitefinity in China at a glance
| What decides it | In Progress's and Microsoft's own terms |
|---|---|
| Where it runs | Sitefinity Cloud is an “Azure-native architecture” with a “global CDN,” which you “purchase ... via Microsoft Azure Marketplace” — the global one. Its published regions are global Azure only; Progress names no mainland-China region, and its “ISO 27001, SOC 2, GDPR, HIPAA” certifications are Western regimes, not Chinese ones. |
| “Azure-native” is not “Azure in China” | Microsoft's mainland cloud is a separate partition: “Microsoft Azure operated by 21Vianet (Azure in China) is a physically separated instance of cloud services located in China,” “independently operated and transacted by” 21Vianet on a separate contract and a separate “Azure in China” Marketplace. Sitefinity Cloud is not sold there. |
| Serving the public | A public site served to mainland visitors from inside China needs an ICP filing tied to a mainland hosting resource (MIIT Order No. 33; State Council Order No. 292). With no mainland region in the product, Sitefinity provides no ICP-filing path of its own. |
| Your users' data | Personal data that Sitefinity forms, lead capture or personalization collect and then process offshore is a cross-border transfer PIPL governs — with a data-localization duty for CIIOs and large-volume handlers that offshore regions cannot meet. |
| Is it reachable? | Yes — it loaded from a datacenter probe inside China, yet failed every attempt on a Beijing home line the same week (see the paired measurement below). Reachability is not the gate. |
Azure-native — which places it outside mainland China
Sitefinity is a CMS you deploy and host, so the hosting decision, not the software, is what China regulates. Progress’s managed option, Sitefinity Cloud, describes itself on its own product page as an “Azure-native architecture” with a “global CDN,” one you “purchase … via Microsoft Azure Marketplace,” and it is “Certified for ISO 27001, SOC 2, GDPR, HIPAA.” Every one of those is a Western data regime; none is a Chinese one — there is no PIPL certification and no MLPS rating in that list.
The word doing the quiet work is global. Microsoft runs a wholly separate cloud inside the mainland and documents it plainly: “Microsoft Azure operated by 21Vianet (Azure in China) is a physically separated instance of cloud services located in China,” one “independently operated and transacted by” 21Vianet, on its own contract and its own “Azure in China” Marketplace — not the global Marketplace that Sitefinity Cloud is sold through. Inference, labeled as such: Progress publishes no 21Vianet or mainland deployment on its page — confirm current regions with Progress — so a standard Sitefinity Cloud tenant sits outside mainland China.
That geography settles the licensing question before performance enters it. Serving a public-facing site to mainland visitors from inside China turns on an ICP filing (ICP 备案) under MIIT Order No. 33 and State Council Order No. 292, and that filing has to attach to a hosting resource physically inside the mainland before any China network or CDN will route the traffic. Sitefinity Cloud ships none, so there is nothing in the product to file against: standing up that mainland host is a step you take yourself, and the filing attaches to the host, not to Sitefinity.
Your China users’ data stays offshore
A CMS earns its keep by collecting things — contact forms, gated-content and lead-capture fields, the behavioral signals personalization runs on. Serve that from an offshore Sitefinity deployment and the personal information it gathers from Chinese users comes to rest in whatever global Azure region you run in, outside the mainland. Under China’s Personal Information Protection Law that is a cross-border transfer, and the handler — you, not Progress — must give notice, obtain separate consent, and clear one transfer mechanism: a CAC security assessment, the CAC standard contract, or certification. If you are a critical information infrastructure operator or a large-volume handler, personal information collected in China has to be stored in the mainland (PIPL Article 40; Cybersecurity Law Article 39 (formerly Article 37)) — a residency duty no offshore Azure region can satisfy.
Reachable, not blocked — which is exactly the point
Sitefinity is not blocked in China, and the measurements say so from two very different vantage points. Progress’s own Sitefinity site completed 3 of 3 loads from a datacenter probe (Alibaba Cloud cn-zhangjiakou) on 2026-08-28 — median TTFB 618ms, median LCP 2,192ms. Measured again from a Beijing residential broadband line on 2026-08-30, the same page completed 0 of 3 loads within a 60s ceiling — TTFB still a median 911ms, so this is border latency and offshore-asset loss, not a block: about half the page’s resources hung, all offshore hosts (three Amazon CloudFront distributions and cdn.insight.sitefinity.com). The datacenter result does not describe what a consumer connection sees — and a vendor marketing site loading is not the same as a Sitefinity-built site serving your own visitors.
Either way, reaching the page was never the gate. Reaching it gives you neither an ICP filing nor in-country data residency, and no amount of network tuning closes those two gaps. This is a risk map, not a verdict: whether you need an ICP filing, in-country storage, or both turns on what you serve, how much personal data you hold, and who your users are — worth settling with counsel before you build.
Where 21YunBox fits — a compliant overlay, not a migration
You keep building on Sitefinity, on Azure or wherever your origin already runs. We add the one piece the product leaves to you: compliant, ICP-filed delivery from inside the mainland, placed in front of your existing Sitefinity origin — no rebuild, no second codebase, and no move off your stack. Our China compliance team maps your ICP and cross-border-PI obligations against your entity and your data volumes, then stands up the in-country delivery and storage a lawful China presence needs. We streamline the filing; we do not lend or bridge a license — the ICP attaches to your own mainland footing, which is what keeps it durable.
Related reading:
