Is there a fastlane for the Microsoft Store?
If you ship to the App Store and Google Play with fastlane, you've probably looked for the same thing on Windows. Here's what exists, what each option covers, and which fastlane jobs map to which Microsoft Store tool.
There isn't an official one. For an MSIX app, StoreFast does the jobs deliver and supply do for Apple and Google. If you need EXE or MSI apps, flights or add-ons, Microsoft's free tools handle those.
- fastlane has no official Microsoft Store action. The sapfire plugin uploads a package, and that's where it stops.
- Microsoft's msstore CLI and StoreBroker cover more of the Store, but you keep listing files for each language yourself.
- StoreFast uploads your MSIX, writes What's new in every listing language and edits listing text and screenshots in every language.
- It runs from your browser, a GitHub Action, a REST API you can call from a lane, or a coding agent over MCP.
What fastlane does for iOS and Android
fastlane's two store tools are deliver for App Store Connect and supply for Google Play. deliver uploads the build, metadata, screenshots, App Preview videos and What's new for each language, and can submit the version for review. supply uploads APKs or app bundles, listing text, images and screenshots, and changelogs for each language, and moves builds between tracks like internal, beta and production, with gradual rollout.
What people like about it is that the whole release lives in files in the repo and one command sends it. The Microsoft Store doesn't have a tool that does all of that, so the question is which pieces you can get and from where.
fastlane has no Microsoft Store action
fastlane's built-in actions cover the App Store and Google Play. There's nothing for Partner Center among them. Its docs also say fastlane is officially supported on macOS, with Linux and Windows only partly supported.
The sapfire plugin
fastlane-plugin-sapfire is an MIT licensed community plugin with actions for MSBuild, NuGet and the Microsoft Store. For the Store, it has:
ms_credentialsto set the Microsoft Entra (Azure AD) credentials the other actions use.upload_ms_storeto upload a package to Partner Center. Its docs say it doesn't publish the update, so you do that part by hand.upload_package_flightto upload a package as a new package flight.associate_ms_store,build_uwp_appandapp_certificationfor building, Store association and running the Windows App Certification Kit.
The Store actions run on Windows only. There are no actions for listing text, screenshots or release notes. The latest version on RubyGems is 1.3.0 from June 2025, and the repository hasn't had a commit since then. It's a fine pick if your app is built with MSBuild and you only need the upload step inside an existing fastlane setup.
Microsoft's own tools
The msstore CLI is Microsoft's open source command line tool. It publishes MSIX packages and also MSI and EXE apps, handles package flights and gradual rollout, and updates listing metadata from JSON you download, edit and send back. It's still in preview, and Microsoft's overview says app updates through it work for free products only for now.
StoreBroker is a PowerShell module built on the Store submission API. It's the closest thing to deliver. Your listing lives in XML files, one per language, with the description, features, keywords, release notes and screenshots, and it creates app, flight and add-on submissions. You write or translate each language yourself.
Both are free. The msstore and StoreBroker comparison goes into what each one is good at.
How StoreFast covers the same jobs
StoreFast publishes MSIX apps to the Microsoft Store. You connect your Partner Center account once, and then:
- Builds. You upload the .msix, and StoreFast checks the package name and version before anything goes to Microsoft.
- Release notes. You write What's new once in English, or hand it a changelog, and it's translated into every listing language in your app's writing style and kept under the 1,500 character limit.
- Listing text and screenshots. The listing editor changes the description, features and search terms in every language, adds languages, fills in what's missing, and takes one set of screenshots for every language. The listing automation guide shows a script for it.
- Submitting. It submits the update for certification and tracks it, and it can hold the update after certification until you publish it in Partner Center.
- CI. The GitHub Action legendaryspy/storefast-publish sends the package with notes from your changelog or GitHub release. The GitHub Actions guide has the workflow. Anywhere else, the REST API works with curl.
- Agents. Claude Code, Cursor, Codex and other coding agents connect to its MCP server, and you approve each submission before it goes out.
The first submission of a new app still happens in Partner Center, as Microsoft requires. That's true for every tool on this page. StoreFast doesn't publish EXE or MSI apps or do gradual rollout yet.
fastlane actions and their Microsoft Store equivalents
| Job in fastlane | Microsoft Store with sapfire | With msstore or StoreBroker | With StoreFast |
|---|---|---|---|
| Upload a build (deliver, supply) | upload_ms_store, then publish by hand | msstore publish, or a StoreBroker submission | Upload in the browser, the API, the GitHub Action or MCP |
| What's new per language (deliver release_notes, supply changelogs) | Not covered | Edited in JSON or XML for each language | Written once in English and translated into every listing language |
| Listing text per language (deliver and supply metadata) | Not covered | msstore submission updateMetadata, or StoreBroker PDP files | Listing editor, PATCH /apps/:appId/listing or MCP tools |
| Screenshots per language (deliver, supply) | Not covered | StoreBroker PDP files | One set uploaded once for every language, with captions per language |
| Submit for review (deliver submit_for_review) | Not covered | msstore publish, or StoreBroker | Submit in the browser, submit: true in the action, or the API |
| Beta tracks (supply track) | upload_package_flight | Package flights in both | Not available |
| Gradual rollout (supply rollout) | Not covered | Both | Coming, not available yet |
Calling StoreFast from a fastlane lane
If you'd like Windows releases to start from the same Fastfile as your other platforms, a lane can run a script that calls the StoreFast API. It needs an API key that can publish.
platform :windows do
lane :store do
sh("./publish-to-store.sh")
end
endAPI=https://storefast.app/api/v1
AUTH="Authorization: Bearer $STOREFAST_API_KEY"
# Start a release, upload the .msix and finish it, as the API reference shows
# Then write What's new once and translate it into every listing language
curl -X POST -H "$AUTH" -H 'Content-Type: application/json' \
-d '{"english":"- Starts faster."}' \
$API/releases/$RELEASE/notes
# Submit it for certification
curl -X POST -H "$AUTH" $API/releases/$RELEASE/submitThe API reference has the upload steps, every field and the status endpoint to poll afterwards. On GitHub, the action does all of this in one step.
Who it's for
StoreFast is a good fit if
- You ship an MSIX app and want the release notes and listing handled like fastlane handles them for Apple and Google.
- Your listing has several languages and you don't want to write each one by hand.
- You want releases to go out from CI or a coding agent with a review step you control.
Look elsewhere if
- You ship an EXE or MSI. msstore does that today.
- You rely on package flights or add-ons. StoreBroker and msstore handle those.
- You only need the upload inside an existing fastlane setup and you build with MSBuild. Try sapfire.
Questions
- Does fastlane support the Microsoft Store?
- Not out of the box. fastlane's built-in actions cover the App Store and Google Play, and its docs say it's officially supported on macOS, with partial support on Linux and Windows. The community plugin fastlane-plugin-sapfire adds an action that uploads a package to Partner Center.
- What does fastlane-plugin-sapfire do for the Microsoft Store?
- Its upload_ms_store action uploads a package to Partner Center, and upload_package_flight uploads one as a package flight. Its docs say upload_ms_store doesn't publish the update, so you finish that in Partner Center. It has no actions for listing text, screenshots or release notes.
- Can I call StoreFast from a fastlane lane?
- Yes. StoreFast's REST API works with curl, so a lane can run it with sh, the same way it would run any script. There's no StoreFast fastlane plugin.
- Can I keep using fastlane for iOS and Android?
- Yes. Nothing here replaces deliver or supply. You keep your lanes for Apple and Google and add a Microsoft Store step next to them.
- What does StoreFast cost?
- From $12 a month for one app. The API, MCP server and GitHub Action are on the Indie and Studio plans and in the 7-day trial, which needs no card.
Ship Windows releases like the others
Connect Partner Center once, then send your next MSIX with What's new in every language from the browser, CI or your agent. Try it free for 7 days, no card needed.
Sources
Facts about Microsoft's tools were checked against these pages on October 5, 2026.