Microsoft Store Submit: Publish Apps, Then Ship by Git Tag

First Microsoft Store submission: checklist (WinUI 3, free + $4.99 Pro, en-us + de-de)

These notes come from submissions in October 2026. Partner Center changes without notice, so where a screen differs from this list, follow the screen and the linked Microsoft docs. If your repo has docs/store/partner-center-notes.md, its entries win over this list. You can save this as docs/store/SUBMISSION-CHECKLIST.md.

Answers I still need from you

Send these and I'll fill in every <placeholder> below:

1. App display name (the reserved name), plus the website, privacy page and support URLs.
2. What the app does in one sentence, and which Windows APIs need desktop access. This goes into the runFullTrust justification.
3. Everything the app reads (files, folders, clipboard, input, registry, processes…). This goes into the privacy policy.
4. Pro add-on product ID in your StoreContext code (e.g. pro), what Pro unlocks, and how a tester can try Pro without buying.
5. Account type (Individual or Company), and whether Payout and tax are both Complete.
6. Category: is Utilities + tools right?

---

0. Before you open the submission

• Account settings > Payout and tax: both Complete. This is required, because Pro is paid.
• Name reserved: Apps and games > New product > MSIX or PWA app. Submit within about 3 months.
• Product identity values (Name, Publisher CN, PublisherDisplayName, Store ID) are in the manifest. Keep the raw values in a local file that you don't commit.
• Manifest <Resources> declares en-us and de-de.
• Build the .msixupload (x64 + Arm64 bundle is fine).
• Run the Windows App Certification Kit. The overall result must be

PASS. A "Blocked executables" warning is OK.

• docs/store/i18n/listing.en.json and listing.de.json are written from the listing template.
• Screenshots: 1920x1080 PNG, 1 to 10 per language, in docs/store/screenshots/en/ and de/.
• App tile: docs/store/art/app-tile-300.png, 300x300.
• Super hero art: docs/store/art/super-hero-3840x2160.png. No text, no UI, nothing important in the bottom third.
• Privacy page is live. Contents are in the "Privacy policy points" section below.
• [ ]

Pro add-on draft created under the app > Add-ons: Durable, product ID <pro>, matching your code exactly. Don't submit it yet.

• The app handles "add-on not found" with a "Pro is not on sale yet" message, not a generic error. The add-on can only be submitted after the app is live, so there will be a gap.

1. Packages (do this first)

Docs: https://learn.microsoft.com/windows/apps/publish/publish-your-app/msix/upload-app-packages

Doing Packages first matters: uploading changes the Properties privacy question, so you avoid filling Properties twice.

• Drag the .msixupload onto the page and wait for Validated.
• Device families:
  • Windows 10/11 Desktop: tick.
  • Mobile, Xbox, Team and Mixed Reality: untick.
• "Let Microsoft decide whether to make this app available to any future device families": untick.
  • After the upload this box reappears above the package table, ticked again. Untick it there too.
• Architecture shows Neutral. That's normal for a bundle; Show details lists x64 and Arm64.
• Warning "restricted capabilities require approval… runFullTrust" is expected. The justification in step 6 clears it.
• Save.

2. Pricing and availability

Docs: https://learn.microsoft.com/windows/apps/publish/publish-your-app/msix/price-and-availability

• Save draft.

3. Properties

Docs: https://learn.microsoft.com/windows/apps/publish/publish-your-app/msix/enter-app-properties

• Category: Utilities + tools.
  • Subcategory: leave "Pick a subcategory" unless the app is a backup or file manager tool.
  • Secondary category: leave empty.
• Privacy: after the package upload this is forced to

"Yes, my product uses personal information" because of runFullTrust. You can't switch it to No.

• Provide privacy policy URL: https://<your-site>/privacy.html
• Support info:
  • Website: https://<your-site>/
  • Support contact: https://<your-site>/support
  • Phone and address: leave empty. On an Individual account the address would be public.
• Display mode (Mixed Reality / HoloLens): both unticked.
• Product declarations:
  • Purchases outside Store commerce: ☐
  • Tested for accessibility guidelines: ☐ (unless you actually tested)
  • Install to alternate drives: ☑
  • Include data in OneDrive backups: ☑
  • Record and broadcast clips: ☐ (only for games)
  • Pen and ink input: ☐
  • Generative AI features: ☐
• System requirements: nothing ticked, every dropdown "Not specified". A ticked minimum blocks install on hardware without it.
• Save.

4. Age ratings (IARC)

Docs: https://learn.microsoft.com/windows/apps/publish/publish-your-app/msix/age-ratings

• Choose "I'm ready to complete the IARC questionnaire".
• App Type: All Other App Types.
• Ratings from a ratings board or physical media: No.
• Questionnaire answers:
  • Downloaded App: ratings-relevant content? No
  • User Content Sharing? No
  • Online Content? No
  • Promotion or Sale of Age-Restricted Products? No
  • Precise location shared? No
  • Allows users to purchase digital goods? Yes
    • Random items or loot boxes? No
  • Cash rewards, gift cards, crypto or NFTs? No
  • Web browser or search engine? No
  • Primarily news or educational? No
• Save draft. Expect about 3+ everywhere except

Brazil DJCTQ 14 for "In-App Purchases". That is normal for any app with paid add-ons; nothing to change.

• Tick the IARC Terms of Use, then Save.

5. Store listings (English and German)

Docs: https://learn.microsoft.com/windows/apps/publish/publish-your-app/msix/import-and-export-store-listings

1. Add/remove languages: English (United States) en-us and German (Germany) de-de.
2. Open the en-us page. Type Developed by and Copyright, then Save. These carry into the export.
3. Click Export listings to download listingData-*.csv.
4. Run the builder:

   python scripts/build_listing_import.py \
     --csv <listingData-*.csv> --listings docs/store/i18n \
     --screenshots docs/store/screenshots --tile docs/store/art/app-tile-300.png \
     --hero docs/store/art/super-hero-3840x2160.png \
     --languages en=en-us,de=de-de --developer "<PublisherDisplayName>" \
     --out out/store-copy/<app>-listing --markdown out/store-copy/LISTING-COPY.md
   

5. Import listings >

Upload folder > pick out/store-copy/<app>-listing. Check any problems under "View errors".

• Fallback: copy and paste from LISTING-COPY.md.

Limits for each language (the builder checks these, but they apply if you type by hand):

• Save each language.

6. Submission options

Docs: https://learn.microsoft.com/windows/apps/publish/publish-your-app/msix/manage-submission-options

• Publishing hold: "Publish this submission as soon as it passes certification".
• runFullTrust justification. Hard limit

500 characters; longer text is cut off without warning, so count it after filling in.

• The fixed text is about 310 chars, which leaves about 180 for the name, APIs and task.

<AppName> is a Win32 desktop app (WinUI 3, Windows App SDK) packaged as MSIX. It runs as a full-trust desktop process and calls Windows desktop APIs not available to AppContainer apps: <API names> to <task>. Everything stays on the user's PC; there is no telemetry. It does not need administrator rights and installs no drivers or services.

• Submission notification audience: optional.
• Save.

7. Supplemental info > Additional Testing Information

The certification notes box is here, not under Submission options. Save it with the

"Save description" link next to the page title; there's no Save button at the bottom. Leave Credentials empty.

<AppName> is a local desktop utility. No account or sign-in is needed. No special hardware is required.

How to test the main feature: <step 1>, <step 2>, <expected result>.

Pro add-on (<pro>, durable): it will be submitted after this app is published, so in this build the Pro button shows "Pro is not on sale yet". To see the Pro features without buying: <how, e.g. the free features shown, or the Pro screens visible with a lock>.

runFullTrust is used for <APIs/task>. The app does not need administrator rights and sends no telemetry; the only network use is the Microsoft Store license and purchase check.

8. Submit

Docs: https://learn.microsoft.com/windows/apps/publish/publish-your-app/msix/app-certification-process

• All six sections show Complete, and Packages shows "Validated".
• Open the en-us and de-de listings once each to check the imported text and screenshots.
• Press Submit for certification yourself.
• Timing: about 13 h last time; Microsoft allows up to 3 business days. The IARC rating email follows. Keep the Global Rating ID.

9. After the app is live

• Submit the Pro add-on:
  • Properties: lifetime Forever, privacy answer No.
  • Pricing: USD 4.99. Keep the converted prices for other markets.
  • Listing for each language: title, description up to 200 chars, 300x300 icon.
  • Submission options: publish when certified.
  • Expect about 7 h.
• Share the link: https://apps.microsoft.com/detail/<Store ID>.
• Set up the GitHub Actions release automation. Ask me when you're ready.

---

Privacy policy points

The policy must match the app exactly

• What the app reads: <list from your answers>. All of it is processed and stored only on the PC.
• No telemetry, analytics, ads or accounts.

Microsoft Store connection: the app contacts the Microsoft Store to check the Pro license and to make purchases. Microsoft handles this under its own privacy statement. Don't write "no internet connection", because that would be false with an add-on.

• Where local data or settings are stored, and how to delete them (uninstalling removes them).
• Contact: <support URL/email>.