Nota
L-aċċess għal din il-paġna jeħtieġ l-awtorizzazzjoni. Tista’ tipprova tidħol jew tibdel id-direttorji.
L-aċċess għal din il-paġna jeħtieġ l-awtorizzazzjoni. Tista’ tipprova tibdel id-direttorji.
Note
This page covers MSI/EXE app publishing using Microsoft Store Developer CLI. For information on MSIX app publishing using Microsoft Store Developer CLI, click here.
The Microsoft Store Command Line Interface is a cross-platform (Windows, macOS, Linux) CLI that helps you publish updates to your applications in the Microsoft Store. For MSI/EXE apps, the CLI calls the Partner Center APIs to submit package metadata containing the URL of your developer-hosted installer. The Store retrieves the installer from that URL; the CLI does not package or upload the installer binary. For hosting requirements, see Add and edit package info.
Important
You must complete your app's first publication to the Microsoft Store through Partner Center. After your app is published, you can use the Microsoft Store Developer CLI to publish subsequent updates.
The process to use Store Developer CLI is the same for both MSI/EXE and MSIX apps. So, to understand how to use it, check out the following video:
Prerequisites
To use the Microsoft Store Developer CLI, you'll need to:
- Register as a Windows app developer in Partner Center
- Have a tenant associated with your Partner Center account. You can achieve that by either associating an existing Microsoft Entra ID in Partner Center or by creating a new Microsoft Entra ID in Partner Center.
- Have your app already created in Partner Center. If your app doesn't exist yet, create your app by reserving its name in Partner Center. The CLI can't create an app for you.
- Complete the app's first publication through Partner Center. Create the first submission for the app, including the age ratings questionnaire, and submit it for certification in Partner Center. Wait until the app is published to the Microsoft Store before using the CLI to publish subsequent updates.
Installation
The Microsoft Store Developer CLI supports Windows 10+, Linux, and macOS:
Install the Microsoft Store Developer CLI (preview) now!
Getting Started
After installing the Microsoft Store Developer CLI, you have to configure your environment to be able to run commands. You can do this by simply running the CLI for the first time. The CLI will guide you through the configuration process:
msstore
Important
When signing in, don't use your MSA! The Microsoft Store Developer CLI requires you to use your Microsoft Entra ID credentials. You can find more information about this in our prerequisites section.
Running in CI environments is also supported, and the Microsoft Store Developer CLI (preview) can be used in your CI/CD pipelines to, for example, automatically publish updates to your applications in the Microsoft Store. More instructions on how to do this can be found here.
Note
App update operations through Microsoft Store Developer CLI is currently supported for free products only. Paid products will be supported in a future release.
Commands
These are the Microsoft Store Developer CLI available commands:
| Command | Description |
|---|---|
| info | Print existing configuration. |
| reconfigure | Re-configure the Microsoft Store Developer CLI. |
| settings | Change settings of the Microsoft Store Developer CLI. |
| submission | Submission related commands, such as 'status', 'get', 'getListingAssets', 'updateMetadata', 'update', 'poll', 'publish'. |
For more info, see: Commands.
Frequently asked questions
What is the Microsoft Store Developer CLI and how can it help me?
The Microsoft Store Developer CLI is a cross-platform command-line tool that allows developers to automate many Partner Center tasks, such as:
- Listing and retrieving app information
- Updating package metadata, including the URL of your developer-hosted installer
- Updating Store metadata
- Submitting and publishing app updates
This tool is particularly useful for CI/CD pipelines, where you can automatically submit updated installer URLs and publish app updates after the app's first publication through Partner Center. Authentication is done using Entra ID credentials linked to your Partner Center account.
It offers a flexible alternative to the web UI and supports scripting workflows across Windows, macOS, and Linux. To use it, developers must first configure API access with appropriate permissions. With this tool, teams can significantly streamline and scale their release operations.
Can I automate Store submissions with the CLI?
Yes, after you complete your app's first publication through Partner Center, you can use the CLI in build pipelines to submit updated package metadata and publish subsequent app updates. Build and host your MSI/EXE installer separately, then use the CLI to submit package metadata containing its URL. The Store retrieves the installer from that URL; the CLI does not package or upload it. You can't use the CLI to complete the first publication.
Windows developer