StoreFast vs the msstore CLI and StoreBroker
Microsoft has two free tools for publishing to the Store without clicking through Partner Center. They're good at what they do. Here's how they compare to StoreFast and when you'd pick each one.
If you want to stop publishing by hand and don't want to own a script, pick StoreFast. It publishes from CI too, with its GitHub Action. If you ship an EXE or MSI, or you already live in PowerShell, Microsoft's tools are free and they work.
- There are no JSON files, PowerShell modules or config to keep up. You drop the package in your browser.
- What's new is translated into every listing language for you. With msstore and StoreBroker you supply each language yourself.
- The package name and version are checked before anything uploads.
- Downloads, installs, ratings and reviews are on the same dashboard. Neither tool shows those.
- Nothing to install or update on your machine or on a build runner.
The msstore CLI
The Microsoft Store Developer CLI is Microsoft's open source, MIT licensed command line tool for Windows, macOS and Linux. It publishes MSIX packages and also MSI and EXE apps, which StoreFast can't do yet. Its commands cover your apps, submissions, package flights and gradual rollout, packaging, and updating listing metadata.
For CI there's an official GitHub Action that installs it on the runner. To change listing text, Microsoft's GitHub Actions guide has you download your submission's metadata as JSON, save it in the repo, edit it and push.
A few things to know before you start, all from Microsoft's own docs.
- It's still in preview, and app updates through it work for free products only for now.
- Telemetry is on by default. You turn it off with msstore settings --enableTelemetry false.
- You sign in with Microsoft Entra ID credentials, not a personal Microsoft account.
- It can't create an app or do the first submission. Nothing can, apart from Partner Center.
Pick msstore if your app is free, you want every release to go out from CI, and you're fine keeping a JSON file for each language.
StoreBroker
StoreBroker is an MIT licensed PowerShell module built on the Store submission API. Its README says it's the main way Microsoft's own app teams submit to the Store, and that most of those apps are localized into 64 languages, so it's built for big listings. It creates, updates and removes app, flight and add-on submissions, supports gradual rollout and a target publish date, and includes a submission monitor that sends email.
Your listing lives in XML files, one per language, which you translate yourself. Its usage docs also note that the submission API allows 20 requests a minute per tenant, and StoreBroker retries for you when you hit that.
Pick StoreBroker if you already work in PowerShell, ship add-ons, or manage listings in dozens of languages with your own translators.
Your own script
Both tools sit on Microsoft's submission API, and you can call it yourself. You get a token that lasts 60 minutes, create a submission, edit its JSON, upload a ZIP with the package, commit and poll. It doesn't work with mandatory updates or Store-managed consumables, and once someone edits an API-made submission in Partner Center, the API can't commit it anymore. That's a fine project if you enjoy it. StoreFast is that project already built, with translations and stats on top.
Side by side
| Feature | StoreFast | msstore CLI | StoreBroker | Your own script |
|---|---|---|---|---|
| How you use it | In the browser | Command line | PowerShell | Your code |
| Publish an MSIX update | Yes | Yes | Yes | Yes |
| EXE and MSI apps | Nocoming | Yes | Not in its docs | Yesa separate API |
| What's new translated for you | Yes | NoJSON you edit | NoXML you translate | No |
| Downloads, installs and reviews | Yes | No | No | If you build itanalytics API |
| Gradual rollout | Nocoming | Yes | Yes | Yes |
| Package flights | No | Yes | Yes | Yes |
| Add-ons | No | Yes | Yes | Yes |
| Runs from GitHub Actions | Yes | Yes | Yes | Yes |
| Price | From $12 a month | Free, MIT | Free, MIT | Free, plus your time |
Who it's for
StoreFast is a good fit if
- You ship an MSIX app and don't want to write or maintain publishing code.
- Your listing has several languages and you want What's new in all of them.
- You want your Store stats and your releases in one place.
Look elsewhere if
- You want a free tool in CI and don't mind keeping a JSON file for each language. Use msstore and its GitHub Action.
- You ship an EXE or MSI. msstore does that today.
- You publish add-ons or rely on flights. StoreBroker and msstore both handle those.
Questions
- Can I use StoreFast alongside msstore or StoreBroker?
- Yes. They all work through the same kind of Microsoft Entra application in your Partner Center account. If another tool already has an update in progress for an app, StoreFast tells you before you upload.
- Does StoreFast have a command line tool or GitHub Action?
- Yes to the GitHub Action: legendaryspy/storefast-publish uploads your MSIX and release notes from a workflow. There's no command line tool, but there's an API you can call with curl, and an MCP server for coding agents.
- Does StoreFast publish EXE or MSI apps?
- Not yet, that support is coming. msstore handles them today.
- What does StoreFast cost compared to the free tools?
- From $12 a month for one app, with a 7-day trial that needs no card. msstore and StoreBroker are free and open source. What you pay for is not writing and keeping up the scripts, the translations and the stats.
Skip the script
Connect Partner Center once, drop your next package in the browser and send it with notes in every language. Try it free for 7 days, no card needed.
Sources
Facts about Microsoft's tools were checked against these pages on October 2, 2026.
- microsoft/msstore-cli README
- Microsoft Store Developer CLI overview
- Publish with the msstore CLI from GitHub Actions
- microsoft/microsoft-store-apppublisher
- microsoft/StoreBroker README
- StoreBroker usage
- Create and manage submissions
- Submission API for MSI or EXE apps
- Access analytics data using Store services