API access and integration with Microsoft Partner Center for managing partner data
For apps where pricing is managed per market and the returned Pricing.PriceId is Base, there is no supported way in the documented CLI flow to send Base back as the base price. Base is only valid inside market-specific pricing and is not valid for --priceId or for submission updates that require a valid base Pricing.PriceId.
Supported paths shown in the documentation:
- Use Partner Center to publish the update when the Store returns
Base, an empty price ID, or no pricing object.- This is the documented path when prices are managed per market.
- For listing-only changes, start a new update in Partner Center, edit the Store listing, save, and submit for certification.
- Set an explicit base tier and review before committing if automation must continue.
- The documented example is:
msstore publish 'C:\path\to\app' --priceId Tier1012 --noCommit msstore submission get <productId> msstore submission publish <productId>-
submission updatealso requiresPricing.PriceIdto be a valid value such asTier<number>,Free, orNotAvailable.
Answers to the specific questions:
- Update only the listing without changing pricing when
priceId = "Base"- The documented supported approach is to do the update in Partner Center rather than through the submission update flow that requires a valid base
Pricing.PriceId. - In Partner Center, create a new submission by selecting Start update, then edit Store listings and submit.
- The documented supported approach is to do the update in Partner Center rather than through the submission update flow that requires a valid base
- Official Tier ID for a given base price such as USD 7.99
- The documentation states that the publish command page includes a table mapping expanded price tiers to US retail prices.
-
Tier<number>is the official format for a base-price tier, and it is not a literal currency amount. - No specific tier number for USD 7.99 is provided in the available context, so only the existence of that mapping table is supported here.
- Whether sending a matching Tier ID preserves current per-market prices
- The documentation explicitly warns that
--priceIdsets a single base price and doesn't guarantee preservation of per-market prices. - Intended market prices must be verified before committing.
- It also states that
--noCommitis not a dry run; it uploads the package and updates the draft.
- The documentation explicitly warns that
Practical safe path:
- In Partner Center, open the app overview.
- Select Start update.
- Go to Store listings and make the listing-only changes.
- Save and submit for certification.
If automation is still required, retrieve the current submission first, update the full JSON, and ensure Pricing.PriceId is a valid Tier<number>, Free, or NotAvailable. Before publishing, inspect Pricing.PriceId and Pricing.MarketSpecificPricings in the draft and verify all market prices, because using a base tier can alter pricing behavior.