Single service comparison

Azure Marketplace integrates procurement directly into the Azure billing and subscription fabric: customers purchase offers through Microsoft Commercial Marketplace, receive charges on their Azure invoice alongside infrastructure consumption, and can deploy first-party data-plane resources from portal tiles. Huawei KooGallery is the analogous storefront but operates as a separate marketplace plane with its own seller center, buyer center, and order/billing workflows; deployment and metering typically flow through KooGallery orders and partner-settlement rather than being natively co-mixed with infrastructure metering on a single cloud invoice, so ISV integration points and revenue models differ at the contract boundary.

Publishing and access-control boundaries differ. Azure Marketplace uses Partner Center for offer authorisation, plans, pricing tiers, technical configuration, and transact-vs-list models, plus Azure AD (Microsoft Entra) for SaaS subscription identity brokerage. KooGallery uses the Huawei Cloud seller console and partner onboarding process, with listing lifecycle and tenant access tied to Huawei Cloud IAM and the buyer's Huawei Cloud account. Microsoft's commercial marketplace API set (SaaS Fulfillment, Marketplace Metering) has no documented one-to-one equivalent in KooGallery, so any ISV relying on Azure fulfilment APIs must redesign integration against Huawei's seller/partner tooling.

Regional reach and pricing transparency are not equivalent. Azure Marketplace is a globally unified catalog with offers available across Azure regions subject to publisher targeting, and pricing is published in multiple currencies with Azure billing in customer currency. KooGallery listings are scoped to Huawei Cloud regions and storefronts (China site and international sites), which have separate catalogs, currencies, commercial terms, and partner programs. Do not assume offer portability across storefronts, equal currency coverage, or identical discount/seat-meter constructs; evaluate catalog availability per target region before migration planning.

Assess the source offer portfolio against KooGallery product types and region catalog. Catalogue each Azure Marketplace listing, its offer type (SaaS, VM image, managed app, professional service), meter model (license-based, usage-based, seat), identity integration, and target Azure regions. Map only offers whose product type exists in KooGallery for the destination storefront and region; mark SaaS-published, API-fulfilled offers for custom rebuild because KooGallery parity of SaaS fulfilment APIs is not documented and must be validated per offer.

For data and configuration migration, recreate offerings in the KooGallery seller center: rebuild listing metadata, plans, pricing tiers, and technical configuration using Huawei's partner onboarding flow. Re-establish identity and tenant access through Huawei Cloud IAM rather than Microsoft Entra, and reconfigure any webhook or fulfilment pipeline that previously called Azure Marketplace metering/SaaS Fulfillment APIs. There is no documented automated tool to port Azure Marketplace offer metadata to KooGallery; treat listing migration as manual recreation plus contract re-enrolment.

Validate end-to-end before cutover in a non-production tenant: confirm listing approval, plan pricing, buyer provisioning flow, order and billing settlement, IAM principal scoping, and support escalation paths. Run sample procurements through the buyer center to verify metering, invoicing currency, and partner settlement match the expected commercial model. Validate region availability for the storefront chosen, as China site and international catalogs are not interchangeable.

Address pricing model and commercial gaps explicitly. Azure merges offer-meter and infrastructure-meter charges on one invoice, while KooGallery typically settles partner licensing and infrastructure usage through separate flows; recompute TCO including currency, settlement fees, partner program tier, and any inter-region traffic. Document feature-parity gaps (fulfilment API, SaaS subscription brokerage, private offers, co-sell incentives) up front, and defer production cutover until publisher contract, listing approval, and settlement validation are complete for every migrated offer.