Msstore CLI
Microsoft Store Developer CLI (msstore) for publishing Windows applications to the Microsoft Store. Use when asked to configure Store credentials, list Store apps, check submission status, publish submissions, manage package flights, set up CI/CD for Store publishing, or integrate with Partner Center. Supports Windows App SDK/WinUI, UWP, .NET MAUI, Flutter, Electron, React Native, and PWA applications.
- Skill ID
- github/awesome-copilot/msstore-cli
- Publisher
- github
- Repository
- awesome-copilot
- Installs
- 0
- Files
- 1
- License
- MIT
- Synced
- Sep 23, 2026
Open any RiverX project, open the Skills panel in the chat, and search for this identifier. The files are fetched from the source repository at install time.
github/awesome-copilot/msstore-cliInstalls these files- SKILL.md
What this skill tells the agent
Microsoft Store Developer CLI (msstore)
The Microsoft Store Developer CLI (msstore) is a cross-platform command-line interface for publishing and managing applications in the Microsoft Store. It integrates with Partner Center APIs and supports automated publishing workflows for various application types.
When to Use This Skill
Use this skill when you need to:
- Configure Store credentials for API access
- List applications in your Store account
- Check the status of a submission
- Publish submissions to the Store
- Package applications for Store submission
- Initialize projects for Store publishing
- Manage package flights (beta testing)
- Set up CI/CD pipelines for automated Store publishing
- Manage gradual rollouts of submissions
- Update submission metadata programmatically
Prerequisites
- Windows 10+, macOS, or Linux
- .NET 9 Desktop Runtime (Windows) or .NET 9 Runtime (macOS/Linux)
- Partner Center account with appropriate permissions
- Azure AD app registration with Partner Center API access
- msstore CLI installed via one of these methods:
- Microsoft Store: Download
- WinGet:
winget install "Microsoft Store Developer CLI" - Manual: Download from GitHub Releases
Partner Center Setup
Before using msstore, you need to create an Azure AD application with Partner Center access:
- Go to Partner Center
- Navigate to Account settings > User management > Azure AD applications
- Create a new application and note the Tenant ID, Client ID, and Client Secret
- Grant the application appropriate permissions (Manager or Developer role)
Core Commands Reference
info - Print Configuration
Display the current credential configuration.
msstore infoOptions:
| Option | Description |
|---|---|
-v, --verbose | Print verbose output |
reconfigure - Configure Credentials
Configure or update Microsoft Store API credentials.
msstore reconfigure [options]Options:
| Option | Description |
|---|---|
-t, --tenantId | Azure AD Tenant ID |
-s, --sellerId | Partner Center Seller ID |
-c, --clientId | Azure AD Application Client ID |
-cs, --clientSecret | Client Secret for authentication |
-ct, --certificateThumbprint | Certificate thumbprint (alternative to client secret) |
-cfp, --certificateFilePath | Certificate file path (alternative to client secret) |
-cp, --certificatePassword | Certificate password |
--reset | Reset credentials without full reconfiguration |
Examples:
# Configure with client secret
msstore reconfigure --tenantId $TENANT_ID --sellerId $SELLER_ID --clientId $CLIENT_ID --clientSecret $CLIENT_SECRET
# Configure with certificate
msstore reconfigure --tenantId $TENANT_ID --sellerId $SELLER_ID --clientId $CLIENT_ID --certificateFilePath ./cert.pfx --certificatePassword MyPasswordsettings - CLI Settings
Change settings of the Microsoft Store Developer CLI.
msstore settings [options]Options:
| Option | Description |
|---|---|
-t, --enableTelemetry | Enable (true) or disable (false) telemetry |
Set Publisher Display Name
msstore settings setpdn <publisherDisplayName>Sets the default Publisher Display Name for the init command.
apps - Application Management
List and retrieve application information.
List Applications
msstore apps listLists all applications in your Partner Center account.
Get Application Details
msstore apps get <productId>Arguments:
| Argument | Description |
|---|---|
productId | The Store product ID (e.g., 9NBLGGH4R315) |
Example:
# Get details of a specific app
msstore apps get 9NBLGGH4R315submission - Submission Management
Manage Store submissions.
| Sub-Command | Description |
|---|---|
status | Get submission status |
get | Get submission metadata and package info |
getListingAssets | Get listing assets of a submission |
updateMetadata | Update submission metadata |
poll | Poll submission status until complete |
publish | Publish a submission |
delete | Delete a submission |
Get Submission Status
msstore submission status <productId>Get Submission Details
msstore submission get <productId>Update Metadata
msstore submission updateMetadata <productId> <metadata>Where <metadata> is a JSON string with the updated metadata. Because JSON contains characters that shells interpret (quotes, braces, etc.), you must quote and/or escape the value appropriately:
- Bash/Zsh: Wrap the JSON in single quotes so the shell passes it through literally. ``
bash msstore submission updateMetadata 9NBLGGH4R315 '{"description":"My updated app"}'`` - PowerShell: Use single quotes (or escape double quotes inside a double-quoted string). ``
powershell msstore submission updateMetadata 9NBLGGH4R315 '{"description":"My updated app"}'`` - cmd.exe: Escape each inner double quote with a backslash. ``
cmd msstore submission updateMetadata 9NBLGGH4R315 "{\"description\":\"My updated app\"}"``
Tip: For complex or multi-line metadata, save the JSON to a file and pass its contents instead to avoid quoting issues: ``bash msstore submission updateMetadata 9NBLGGH4R315 "$(cat metadata.json)" ``Options:
| Option | Description |
|---|---|
-s, --skipInitialPolling | Skip initial status polling |
Publish Submission
msstore submission publish <productId>Poll Submission
msstore submission poll <productId>Polls until the submission status is PUBLISHED or FAILED.
Delete Submission
msstore submission delete <productId>Options:
| Option | Description |
|---|---|
--no-confirm | Skip confirmation prompt |
init - Initialize Project for Store
Initialize a project for Microsoft Store publishing. Automatically detects project type and configures Store identity.
msstore init <pathOrUrl> [options]Arguments:
| Argument | Description |
|---|---|
pathOrUrl | Project directory path or PWA URL |
Options:
| Option | Description |
|---|---|
-n, --publisherDisplayName | Publisher Display Name |
--package | Also package the project |
--publish | Package and publish (implies --package) |
-f, --flightId | Publish to a specific flight |
-prp, --packageRolloutPercentage | Gradual rollout percentage (0-100) |
-a, --arch | Architecture(s): x86, x64, arm64 |
-o, --output | Output directory for packages |
-ver, --version | Version to use when building |
Supported Project Types:
- Windows App SDK / WinUI 3
- UWP
- .NET MAUI
- Flutter
- Electron
- React Native for Desktop
- PWA (Progressive Web Apps)
Examples:
# Initialize WinUI project
msstore init ./my-winui-app
# Initialize PWA
msstore init https://contoso.com --output ./pwa-package
# Initialize and publish
msstore init ./my-app --publishpackage - Package for Store
Package an application for Microsoft Store submission.
msstore package <pathOrUrl> [options]Arguments:
| Argument | Description |
|---|---|
pathOrUrl | Project directory path or PWA URL |
Options:
| Option | Description |
|---|---|
-o, --output | Output directory for the package |
-a, --arch | Architecture(s): x86, x64, arm64 |
-ver, --version | Version for the package |
Examples:
# Package for default architecture
msstore package ./my-app
# Package for multiple architecturesMore from github
Use this skill in a project
Open any RiverX project, search the Skills panel for github/awesome-copilot/msstore-cli, and install it in one click.
